Content file ignored, new content file being generated

The CMS Questions
1

I’m having a recurring issue where Kirby ignores the content file for a particular page (in this case blog.txt) and generates a new default.txt content file for the page that is blank except for a new UUID. This is obviously a real nuisance because it disrupts the page’s intended template and content. The issue seems to arise when a user is working in this page inside the Panel. Any ideas how I can even start to troubleshoot?

2

which version of Kirby 5 specifically?

3

The staging site was running 5.0.3. Sorry—I thought I was up to date but I should have checked. I just upgraded to 5.1.2 now… I am hoping this solves the problem but it should be obvious soon, since the new default.txt content file has been getting added multiple times daily. Thanks!

4

If the issue persists:

  • Is the default.txt file added in addition to the blog.txt file?
  • Have you made sure the page folder does not contain any leftover content file (e.g. file meta data text files that do not belong to a file)
  • Can this be reproduced in a Starterkit?
5

any plugins or custom hooks?

6

Thanks for helping me troubleshoot. For the record, upgrading to Kirby 5.1.2 did not fix the problem. To clarify, yes, the default.txt file was being added alongside blog.txt. The site in question had several plugins, but I don’t think those were causing the problem.

The staging site is hosted at NearlyFreeSpeech, a host that I like but haven’t ever used for Kirby. Their servers are extremely stringent with file ownership and permissions, and I think my issue resulted from the Kirby php scripts lacking adequate permission to modify the existing blog.txt file. I’m not sure how to prove this, but since recursively changing permissions on the entire content folder, I haven’t experienced the problem.

What’s odd is that, in other cases, I received clear panel errors telling me Kirby lacked permission to delete a folder, modify a page’s content file, etc. But in the case above, there were no panel errors—just silent creation of a new default.txt file.

Either way, I think I’ve solved the problem, so I’ll mark this post as the solution. Thanks again for the help.