New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v2.0.2] Ignores XSLT Utility #34

Closed
jurajkapsz opened this Issue Jun 4, 2017 · 10 comments

Comments

Projects
None yet
2 participants
@jurajkapsz
Contributor

jurajkapsz commented Jun 4, 2017

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

This comment has been minimized.

Show comment
Hide comment
@nitriques

nitriques Jun 5, 2017

Member

XSLT Utility

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

Member

nitriques commented Jun 5, 2017

XSLT Utility

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

@jurajkapsz

This comment has been minimized.

Show comment
Hide comment
@jurajkapsz

jurajkapsz Jun 5, 2017

Contributor

Calling an external xslt file ?

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

image

Contributor

jurajkapsz commented Jun 5, 2017

Calling an external xslt file ?

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

image

@nitriques nitriques added bug and removed feedback needed labels Jun 5, 2017

@nitriques

This comment has been minimized.

Show comment
Hide comment
@nitriques

nitriques Jun 5, 2017

Member

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...

Member

nitriques commented Jun 5, 2017

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

This comment has been minimized.

Show comment
Hide comment
@jurajkapsz

jurajkapsz Jun 6, 2017

Contributor

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

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

Contributor

jurajkapsz commented Jun 6, 2017

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

This comment has been minimized.

Show comment
Hide comment
@nitriques

nitriques Jun 13, 2017

Member

Can you try to:

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

it should work !

Member

nitriques commented Jun 13, 2017

Can you try to:

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

it should work !

@nitriques

This comment has been minimized.

Show comment
Hide comment
@nitriques
Member

nitriques commented Jun 30, 2017

@jurajkapsz ping ?

@jurajkapsz

This comment has been minimized.

Show comment
Hide comment
@jurajkapsz

jurajkapsz Jun 30, 2017

Contributor
  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 !

Contributor

jurajkapsz commented Jun 30, 2017

  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

This comment has been minimized.

Show comment
Hide comment
@jurajkapsz

jurajkapsz Jul 1, 2017

Contributor

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:

image

Contributor

jurajkapsz commented Jul 1, 2017

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:

image

@nitriques

This comment has been minimized.

Show comment
Hide comment
@nitriques

nitriques Jul 1, 2017

Member

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!

Member

nitriques commented Jul 1, 2017

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

This comment has been minimized.

Show comment
Hide comment
@jurajkapsz

jurajkapsz Jul 1, 2017

Contributor

Ok, that makes sense, thanks!

Contributor

jurajkapsz commented Jul 1, 2017

Ok, that makes sense, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment