Closed privatemaker closed 1 year ago
Thanks for checking Sveltia CMS! Well, your Decap CMS config file should be able to be reused without any modification. Can you please open Chrome DevTolls and take a screenshot of the Console tab? There would be some errors displayed there.
I just deployed version 0.3.3 to make sure errors are always logged in the console. Can you take a screenshot and post it here? Thanks! 🙏🏻
Thanks for enabling logging. Previously my console showed no error message. Now I see this:
Thanks for the screenshot! I think now I understand the cause. Will test and deploy the fix.
Just deployed the fix! The issue happened only when the Netlify CMS proxy server was previously used. Please reload the page and try again. I think the documentation is okay because there are no extra steps. 😄
Tested. This seems it was exactly the bug and makes sense given fresh state of my dev environment where I had successfully used the local feature. Thank you for the quick investigation + bug fix. Works great again 👌🏻 🥳
Given that the main use cases are migrations from Netlify CMS, Sveltia CMS is supposed to be working even in a non-fresh environment 😄 Only the proxy thing is an exception, and I should have noticed it earlier.
Thanks again for reporting this! 💯
Hello 👋🏻 I'm very excited about sveltia-cms 😄 I tested it a couple months ago with the
local Git repository
option and it is all looking wonderfully well done.However, my deployment still required
decap-cms
and I reconfigured my dev environment. Since then I cannot get serving locally working again. I get this error:My
config.yml
file works just fine with the decapnpx netlify-cms-proxy-server
so I am sure i'm just misunderstanding something.Perhaps putting an example config or documenting where
sveltia-cms
differs fromdecap-cms
would be helpful to me and others.Anyway, thanks for your hard and really polished work here! Looking forward to future releases 😀