-
Notifications
You must be signed in to change notification settings - Fork 91
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
Issues with wildcard usage in paths containing names starting with digits #688
Comments
@Vocinglero Can you share a yaml which allows us to reproduce the error? |
@kwin Here are the 2 yaml files we use |
@Vocinglero Thanks, I could reproduce. The full stack trace from the exception is as follows:
|
The problem here is not the wildcard at the end, but the name |
@kwin thanks. I thought it was caused by the wildcard because this works fine: |
@Vocinglero Without wildcard there is no query involved, therefore you need the wildcard to trigger it. |
Keep wildcards unencoded, though (https://issues.apache.org/jira/browse/JCR-5051) This closes #688
Keep wildcards unencoded, though (https://issues.apache.org/jira/browse/JCR-5051) This closes #688
Hello,
In our project, we have encountered an issue with folder names in our DAM that include numbers. When we specify ACL rules targeting a specific path directly, everything functions as expected. However, an error arises if we attempt to use a wildcard in the path specification.
For instance, consider the following rule:
This setup results in an error stating:
"Could not process yaml files / e=javax.jcr.query.InvalidQueryException: java.text.ParseException: Query: /jcr:root/content/dam/brands/"21c"()/global-marketing/; expected: jcr:root, /, *, @, (, ."
It's important to note that if we use the path /content/dam/brands/21c/global-marketing without the wildcard, it operates correctly.
The text was updated successfully, but these errors were encountered: