Is the first time we have this issue. We have no content in the Editor yab of October CMS backend.
I atach a print Screen… We had never seen this issue. Can you haelp us debug this or have a solution?
In the console we have some strange error:
Uncaught (in promise) SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at EditorPage.initVue (editor.page.js?vca7bdbf8:18:41)
at EditorPage.init (editor.page.js?vca7bdbf8:12:14)
at new EditorPage (editor.page.js?vca7bdbf8:8:14)
at editor.page.js?vca7bdbf8:69:22
Thanks. I got the same issue with 4.3.0 on the Editor-tab and after clearing the browser cache with the latest Firefox I was able to see it. Something like a cache-buster could help here.
Hi. We have tryied with CTRL+F5 multiple times on the browser tab but with no luck.
Finaly we made a fresh reinstall and it seems it works now but with some “bugs”. From time to time the layout it’s not saved the x icon apears next to layout name in editor tab not the circle (after saved) and the layout is empty. We work this out by editing in paralele directly on the server via Visual Studio and after we close the unsaved file it will open correctly next time.
This is very unusual. I can’t reproduce that outcome over here, and would be interested to know what is causing that.
The caching issue is a funny one, since the cache is busted already (the entrypoint) but the imports don’t get busted by the entrypoint, so it causes a mismatch.
A solution for this will be coming soon, but for now a hard refresh is the way to go, and making sure your assets have a reasonable max-age, e.g. for JS + CSS:
Yes, this issue is affecting all users, and we will need to include the cache-clearing instruction in the release announcement.
The root cause is a partial cache invalidation: only the entrypoint is being busted, while the ESM imports remain cached. This results in a mismatched application state where old and new modules are loaded together.
It’s worth noting that web standards bodies treat this as a cache control responsibility (as referenced above). While there are workarounds available, traditional web development delegates cache management to the web server - or to the user via the browser.
We have a patch in development that will address the partial cache busting issue. Following that, we’ll be evaluating a service worker approach to intercept asset requests and append version strings, providing a more robust long-term solution.
I don’t think it is only cache related. I have tried
ctrl+f5
clearing browser data and cache
php artisan cache:clear
composer update
new browser
This way I managed to overcome almost all issues. Currently (I think) I only have a problem with the Builder plugin (showing only two columns of a table). I have several web servers on different physical installations and I faced those issues on all of them.
We are facing the same problem now in the Builder. We can’t save the table, and the editor saving problem persists from time to time we need to edit the content via external Code Editor on FTP.
Something is terrible wrong here and we can’t work like this.
This is the screenshot with some js errors on the builder page where the table is not saved. Also the table with colums is not fully vissible.
On Chrome the page appears correctly, but on Firefox not
You can’t edit an existing table, you can’t create a new one. Tested on two websites.
(sorry for hijacking the thread)
I can confirm that this is working now in firefox.
But it looks like there is another issue when we try to create a form
This might be broken for a while (Firefox and Chrome).
