[v2.0.2] Ignores XSLT Utility

[jurajkapsz]

It appears that the latest version v2.0.2 does not evaluate XSLT Utility {something} expressions.

Going back to v2.0.1, everything is fine.

[nitriques]

XSLT Utility

What do you mean by this ? Calling an external xslt file ?

[jurajkapsz]

Calling an external xslt file ?

Yes, the optional xslt file in field's properties.

[nitriques]

Oh well. This is a bug. I sadly do not have the time to fix it right now tho, (sorry).
And I really wonder why this simple change would make that...

[jurajkapsz]

I sadly do not have the time to fix it right now tho, (sorry).

That's ok, previous version v2.0.1 works fine.

[nitriques]

Can you try to:

1. Update to 2.0.2
2. Change your xpath from {something} to {//something}

it should work !

[nitriques]

@jurajkapsz ping ?

[jurajkapsz]

1. Update to 2.0.2
2. Change your xpath from {something} to {//something}

Ok, I've tested it and it works flawlessly. Thanks very much @nitriques !

[jurajkapsz]

Ok, I've tested it and it works flawlessly.

One note though: the // now has to be added to the standalone xpath Expression too, like:

[nitriques]

One note though: the // now has to be added to the standalone xpath Expression too, like:

Yup. This was previously not-needed, but it is now because we allow users to enter xpath functions, which was not possible if the // is hardcoded. Thanks!

[jurajkapsz]

Ok, that makes sense, thanks!