Dashboard Edit option does not work after upgrade to 5.6
Permalink
Hi,
We recently upgraded our concrete5 CMS from Version 5.4.1.1 to version 5.6.3.5. When we trying to edit the Pages of our website. For most pages everything is smooth and work as expected. But for some pages, we are unable to edit the page after clicking on the edit option. When we try to edit the blocks on the pages the hyperlink is unavailable. Hence the blocks cannot be edited,copied to clipboard,delete,design change and etc is not possible. We check the console of the browser the following js error comes up.
Uncaught TypeError: Cannot read property 'bridge' of undefined at ccm.app.js:3.
Uncaught ReferenceError: ccm_menuInit is not defined at HTMLDocument.<anonymous> (index.php?cID=439&ctask=check-out&ccm_token=1505708545:dc54374a93458787d76dfee876e1d7b9:147)
at o (jquery.js:2)
at Object.fireWith (jquery.js:2)
at Function.ready (jquery.js:2)
at HTMLDocument.B (jquery.js:2)
Attached the image of the error
Can please anyone suggest the way forward in resolving the issues.
We recently upgraded our concrete5 CMS from Version 5.4.1.1 to version 5.6.3.5. When we trying to edit the Pages of our website. For most pages everything is smooth and work as expected. But for some pages, we are unable to edit the page after clicking on the edit option. When we try to edit the blocks on the pages the hyperlink is unavailable. Hence the blocks cannot be edited,copied to clipboard,delete,design change and etc is not possible. We check the console of the browser the following js error comes up.
Uncaught TypeError: Cannot read property 'bridge' of undefined at ccm.app.js:3.
Uncaught ReferenceError: ccm_menuInit is not defined at HTMLDocument.<anonymous> (index.php?cID=439&ctask=check-out&ccm_token=1505708545:dc54374a93458787d76dfee876e1d7b9:147)
at o (jquery.js:2)
at Object.fireWith (jquery.js:2)
at Function.ready (jquery.js:2)
at HTMLDocument.B (jquery.js:2)
Attached the image of the error
Can please anyone suggest the way forward in resolving the issues.
hi we use Blank HTML5 Boilerplate. Yes the problem persist even if switched to greek yogurt theme.
Unfortunately that rules out the simplest reason, that the way themes loaded core assets changed slightly between 5.4 and 5.6, so minor adjustments to theme headers would be required.
Can you please explain bit elaborately.so that i could implement the minor changes.
As the problem persists with Greek Yogurt, it will not be theme related.
If so, do you still get the problem if you (temporarily) switch the theme back to a core theme such as Greek Yogurt?