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

[question] Why do I get "No CSR-enabled webparts found on the page"? #21

Closed
egidiocs opened this issue Jul 13, 2016 · 8 comments
Closed

Comments

@egidiocs
Copy link

awesome tool! I'm getting this error in default forms. MDS is off.
thank you in advance.
-egidio @egidiocs
image

@joweiser
Copy link

Hey @egidiocs did you install from the Chrome Web Store or from the github repository?
I'm asking because this issue may already be solved. See over here: #20

@andrei-markeev
Copy link
Owner

Yep, this is already solved but not on Chrome Web Store. I'll be updating Chrome Web Store version shortly.

@andrei-markeev
Copy link
Owner

I pushed the latest changes to Chrome Web Store, including fix for this problem. Version should be 2.0.0 now. If it doesn't update, go to chrome://extensions, tick [x] Developer mode, and press [Update extensions now...] button.

@nyn3x
Copy link

nyn3x commented Jul 15, 2016

I have a similar problem. I'm on a list-view (http://portal/sites/foo/_layouts/15/start.aspx#/Lists/samplelist/AllItems.aspx) and I get the "No CSR-enabled webparts found on the page" message - even though the version of CSR is 2.0

@andrei-markeev
Copy link
Owner

Hi, indeed something with list views. Thanks for reporting, I'm investigating it right now.

@andrei-markeev
Copy link
Owner

Ok I fixed this in commit 465953d and I pushed the changes to Chrome Web Store, version 2.0.1.

Automatic update usually takes some while, so go to chrome://extensions, tick [x] Developer mode, and press [Update extensions now...] button.

Please tell me if it works for you now? It should, based on my testing.

For those interested what is happening: so basically the story is that in O365 they changed things so that webpart ids on a page now begin with WPQ1 instead of WPQ2. I was starting from WPQ2 when collecting webparts information from the page, so after this change, things stopped working.
I fixed this in Cisar 2.0, BUT this broke things for old O365 tenants and on-prem SP2013, and also for Wiki pages where this WPQ1-change seemingly was not applied.

@nyn3x
Copy link

nyn3x commented Jul 15, 2016

Just checked with SP2013-OnPrem: seems to work :) Thx for the quick fix!!!! awesome!

@andrei-markeev
Copy link
Owner

Glad to hear that! :)

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

4 participants