stylesheet is broken as of 2.2

[robot-ranger]

the stylesheet appears to be broken for me since 2.2. anyone else have this problem?

When i change the agent.cfg and devices.xml back to 2.0, it works as expected. 2.2 and it appears like above.

no issues with client-end apps; the xml appears to be in good shape, so i think its just the stylesheet

[wsobel]

This usually has to do with the namespace in the stylesheet. I'll check.

[robot-ranger]

This usually has to do with the namespace in the stylesheet. I'll check.

I was trying my best to act like i know stylesheets and dove straight into the transform logic, right past the header things haha. looks like youre right!

is it possible to make it read the schema version from the probe?

[robot-ranger]

or maybe it could be an env var? i dont know much about stylesheets, so i dont know how dynamic it could be or how it would work. but it would be nice to be able to roll up and down schema versions without editing the file

[robot-ranger]

oops - accidentally close it

[wsobel]

They are static documents, so we would need the agent to preprocess the file. Currently it is just serving it as a text file with caching for files under a certain size.  I can flag certain files for preprocessing. That wouldn’t be too difficult if it is a simple replace of tokens in the config file. On Dec 12, 2023, at 19:22, robot-ranger ***@***.***> wrote: oops - accidentally close it —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[robot-ranger]

fixed in #403

[robot-ranger]

fyi - if anyone needs to fix this on an existing container, the following command works:

docker exec -it agent sed -i 's/2.0/2.2/g' /mtconnect/data/styles/styles.xsl

(replace agent with your contianer name if not agent)