I just updated the october cms and the page is running on october 2.0 now. The migration as it went flawlessly and i can access the backend as well as every page on the frontend. Now I just have the problem that the reditor gives me a 'blank' file for every file I try to open. (Screenshot https://imgur.com/a/hDY4kaZ)

Every tab has a skull as icon and I also can't create new pages as it doesn't save anything. Unfortunately there is absolutely no error message so I am not 100% sure what the problem is. I guess it has something to do with my file/folder permissions but I don't know where the problem is. I gave all the files inside the project the 755 permission but it didn't fix the problem.

Great news! Humm, it does indeed sound like a permissions problem

Navigate to Settings > Event Log and see if there are any errors showing there

There is only a error telling that the metadata can't be accessed. This error appears only if I try to access the metadata of the page and not when just opening a page in the editor:

October\Rain\Exception\SystemException: Invalid documentMetadata in /home/web/octoberv2/modules/cms/traits/EditorExtensionCrud.php:386

I have tried testing using the metadata and it seems to work fine on my end. So it means I can't replicate it. Does it happen with the demo theme? Do you have any plugins installed, if so, which ones?

I have the same issue with both themes (mine and demo). What permissions should the theme files/folders have? Furthermore I find it strange that the pages display correctly, wouldn't that mean that at least the editor should be able to read the file?

I have the Goodnows (and the dependency Toolbox plugin) as well as a custom plugin. I tried if disabling my plugin would help but it did not help

Last updated 3 years ago

I just setup a new project following this guide and ran into exactly the same issue https://octobercms.com/docs/setup/installation, that's what I used

Even a sudo chmod -R 777 october didn't fix that problem

Okay, it seems not to be related to the permissions. I just switched to Google Chrome and now it is working. I was using Firefox before. The output in the Firefox Console might be interesting for you, I will upload it to pastebin

https://pastebin.com/A8xfrfL6 https://pastebin.com/WsjtYgcn https://pastebin.com/1Dfx6QUn Those are the three appearing errors in the Firefox (v87.0) console. I just tried the editor in Google Chrome and Firefox Developer Edition and both worked so the issue has something to do with Firefox (I guess).

Hi felix, I can't reproduce the error in Firefox 87. The error messages suggest that the page could try to use promises before October CMS enables the cancellation feature. I'm not sure why this is happening but one possible reason is browser extensions. Please try to disable all extensions and see if it helps. It would be great to find out which extension causes the problem and if we can fix it in the platform.

If it doesn't help please post a message here and also send me an email: alexey@octobercms.com.

Thanks for the information. Indeed it seems that my MetaMask Addon was the bad guy, it's working now. Thank you very much for your patience :)

I am also in a similar situation. I upgraded to 2.0 but I can't edit any pages in the CMS with exactly the same errors as above. I've tried Chrome, Safari and Firefox with plugins disabled and it fails every time.

https://prnt.sc/131phs3 and https://prnt.sc/131piu2

Does anyone have any suggestions?

Hello ollie65718,

I see two errors on your screenshots. One if them suggests that a browser extension is trying to use promises before the Editor client-side framework is initialized. I know that you mentioned you've disabled plugins, but I think there is one in Chrome.

For the second exception - could you find the relevant error message on the System / Event Log page and send the execution stack here? Or email us at hello@octobercms.com.

Thanks

This plugin of Google Chrome is caused this error.

MeddleMonkey 1.0.7

disabled it and it works

felix said:

Okay, it seems not to be related to the permissions. I just switched to Google Chrome and now it is working. I was using Firefox before. The output in the Firefox Console might be interesting for you, I will upload it to pastebin

felix said:

Thanks for the information. Indeed it seems that my MetaMask Addon was the bad guy, it's working now. Thank you very much for your patience :)

Thanks Felix, I also disable MetaMask just fine.