Skip to content
Discussion options

You must be logged in to vote

Hey @stefankuijt thanks for the report.

We were already aware of the issue here and we postponed it almost one year ago and never got back to it. 😞

The reason we didn't prioritized is because we can't guarantee that all kind of selectors will work, even if escaped, so you will also probably need to overwrite some backpack save/update process if deviating from the "standard process".

We'd agree to escape the selectors back then, so I've done it already in PRO and tagged a new version 2.0.17.

It should be available later today with a composer update backpack/pro

Closing this, let me know if you still experiencing issues after the update.

Cheers

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@stefankuijt
Comment options

Answer selected by stefankuijt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants