The system administrator mentioned that the absolute path /usr/home/... does not exist on the production server, and I should use paths relative to the website’s root directory (e.g., ./content/2_projets/_drafts/test).
I can create pages at the root level without any issues, suggesting that the permissions and basic configuration are correct.
Is it possible that Kirby is using absolute paths that are not compatible with my production server configuration?
How can I configure Kirby to use relative paths for creating subpages?
Are there any specific Kirby configurations I should check to avoid this issue?
I have tried (as a user) to set all files and folders to “write permission”, but it still happens.
Is there any way to “debug” Kirby, i.e. to find out where the error occurs, stop there, and then try to see why the problem is happening? I have already spent a lot of time trying to figure out what’s up, but have gotten nowhere so far. In the worst case, I have to re-create everything from start.
Whose permissions have you set? In this case, this is a PHP process that needs the permission. The question is, as which user does the PHP process run? Who has permissions to write in this directory. You also need to make sure to grant permissions recursively, not only to the current folder, but also the folders above.
