I just launched my first Kirby 3-based website, and everything’s been working really great up till now. Only thing is, soon as I migrated the site to our live host, which is running PHP 7.3 with all the required extensions, saving any edits made in the panel don’t persist. The UI feedback suggests that the save was successful, but upon viewing the site on the front-end or reloading the same edit screen in Kirby panel, none of the edits have been saved.
It worked fine on my local development environment and on another host where we have a staging environment.
If I edit the files under
/content directly via FTP, that works fine – the files save fine and I can see the changes both on the frontend and in Kirby panel.
Here are the things I’ve tried to do to solve it:
- I recursively gave all files under
/contentthe permissions rwxrwxrwx (I know that’s not a secure set of permissions, but I just wanted to make sure it wasn’t a permissions issue).
- I opened Chrome’s dev inspector to see if the PATCH request failed. There were no failed requests at all, and the POST and PATCH requests all returned successful 200 responses.
- I checked for any PHP errors and haven’t found any.
- I studied the output of
phpinfo()to ensure all the required PHP extensions were enabled, and as far as I can tell that looks to be the case.
Here is a link to the
phpinfo() output, if that’s of any help.
Any thoughts on what’s going on?
In a pinch we can still edit content via FTP, but it’s far from ideal. A lot of time was put into building the Kirby panel UI for this website with the hopes that the client would be able to make changes on their own.