This project is read-only.

After feature-activation on enterprise-wiki, the "new-page-button" is not working



first of all, i want to thank you for your work on bringing SharePoint together with SyntaxHighlighting! It's great!

... I have an issue on implementing the feature to a standard enterprise-wiki-site.
We tried to customize the code to meet certain requirements and ran into that issue, that after acivating the features, the standard "new-page-button" doesn't work anymore.
At first we thought it was in case of our customizations, but it also doesn't work with your original code(only customized to work in other ribbons than the blog-ribbon only).

After some research within the wiki-site(especially the source-code-view within the browser), i found out, that the implemantation of standard-javascript-links(by SharePoint itself) is different depending on the feature being activated or not.

Going further the implementation of the standard-javascript-links is also different wether the page (e.g. home.aspx) is in edit-mode or not(both with feature activated). Remarkable is, that when the page is in edit-mode, the "new-page-button" is working properly and i can create a new document-page.

Can you explain, where this behaviour results from?

Another Issue(from which i guess it is based on the same problem) is that the feature does not work in FireFox (v21) nor Chrome.

In Addition the different JavaScript-Startup as TextFile(in ZIP)

file attachments


pranavmmodi wrote May 18, 2015 at 5:16 PM

I am having the same problem as mention here.. After implementing syntax highlighting in wiki page, "new page" and some other ribbon options are not working.

It looks like some xpath from syntaxhighlighter.js itself conflict with existing sharepoint functionality. Anyone come across this issue?

wrote May 18, 2015 at 5:17 PM