SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After upgrading from MOSS 2007, when we try the new interface (preview mode), some context menus are not working - if a user clicks e. g. view properties, edit properties, approve/reject... etc, nothing happens. When the user clicks the "Edit item" icon, it works fine.

It happens only sometimes and to some users. There are some customizations, but nothing serious - for example an inserted CEWP above the list - but only sometimes.

Any ideas?

share|improve this question

It looks like a JavaScript problem that might caused by the CEWP (assuming they contains JavaScript) You could try deleting the CEWP, if it works after that then you will need to review the code in the webpart. if its not then you might have a custom theme or other customization that is causing problems

share|improve this answer
Hello Renzo, yes, it seemed to me that the JS in a CEWP might be the cause. However, it doesnt work also in pages that do NOT have a CEWP, and, whats more, only to some users (e. g. one user with ReadWriteEdit permissions has a non-working context menu). We do not have any custom themes and I dont know about any customizations that may cause this behavior - if any, they are, in general, applied throughout the whole portal. Are there any ways to a sort of debug the context menu? – user1667 Nov 1 '10 at 10:53
hi, you can try to debug the JavaScript on the page using the developer tools from IE (go to tools > Developer tools) then got to the script tab and click the start debugging button, reload the page and watch the console for errors – Renzo Nov 1 '10 at 12:17
Well, tried this. The result is: trying to go to dispform/editform - nothing at all - just nothing happens, trying "Alert me" - works, trying Manage permissions - works, but with an error (see More confusing than in the beginning :). Thanks a lot. – user1667 Nov 1 '10 at 14:08

Yeah, it was a custom JavaScript in the site.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.