Skip to content
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

Customizer match url statement ignores URL parameters after first # #38

Open
vtobias opened this issue Feb 15, 2019 · 0 comments
Open

Comments

@vtobias
Copy link

vtobias commented Feb 15, 2019

when using customizer in connections cloud we encounter an error with the url matching:

We use e. g. a url like this one:

https://apps.ce.collabserv.com/communities/service/html/communityoverview?communityUuid=0b6afdad-6be2-46ab-9305-d0756388dbb8#fullpageWidgetId=W3467c5081b6d_463d_9c79_3ed06e754f29

And want to have a specific script running when exactly this widgetID is part of the URL.

{
"name": "Custom community widget helper",
"type": "com.ibm.customizer.ui",
"payload": {
"match": {
"url": "W3467c5081b6d_463d_9c79_3ed06e754f29"
},
"include-files": [
"communities/customWidgets/main.js"
],
"include-repo": {
"name": "CNXcustomizer"
}
},
"path": "global",
"state": "enabled"
},

Unfortunately, the match url statement in the customizer extension in the app registry is not able to ask for anything behind the first # in the URL.

Please care for customizer having the full window.location.href available when evaluating matches on the url.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant