You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using your library inside a Microsoft SharePoint project, it rendered some SharePoint functionality on a page invalid, because SharePoint seems to have some own JavaScript "URI" identifier.
Including your library resulted in JavaScript errors generated by SharePoint.
Solution for me was to download your library from the Build page and then use a text editor to replace all text occurances of "URI" with "MyOwnURI".
Later, I used "MyOwnURI" when accessing your library.
Suggestion
Maybe an option on that Build page to specify a prefix or alternative name for "URI" would be helpful.
The text was updated successfully, but these errors were encountered:
UweKeim
changed the title
Possibilty to change the name of "URI"
Possibility to change the name of "URI"
Jun 28, 2019
Using your library inside a Microsoft SharePoint project, it rendered some SharePoint functionality on a page invalid, because SharePoint seems to have some own JavaScript "
URI
" identifier.Including your library resulted in JavaScript errors generated by SharePoint.
Solution for me was to download your library from the Build page and then use a text editor to replace all text occurances of "URI" with "MyOwnURI".
Later, I used "MyOwnURI" when accessing your library.
Suggestion
Maybe an option on that Build page to specify a prefix or alternative name for "URI" would be helpful.
The text was updated successfully, but these errors were encountered: