The reason I re-copied files into a working dir, is because we don't even know when the other dir started making errors. Several months ago, I did this same process, but back then we kept both folders (working and non-working). I can't be sure which folder is which. Right now, you have a working folder, and a non-working folder, and you need to make sure you don't start trying to use the non-working folder ... What did you do with the one from last time? Did you eventually delete it? It's important to avoid confusion between dirs.
sound_and_light wrote:What I don't get is that error message is part of your app, yes?
It is, and I have looked at this earlier. Basically the script checks what action to take based on posted parameters. This would normally trigger:
// Save page settings
} else if(isset($_POST['page_settings']) && isset($_POST['path'])) { //...
In your case, it is not reading the $_POST options above, and instead ends up on last option where no action is defined.
} else {
echo '{ "error": "No request parameters?" }';
}
I have even checked the "payload" that is forwarded to server, and the page_settings and path are there. This is some low-level corruption in a folder or folder caused by something you did. This is not something anyone has ever reported, which is unfortunate as it makes it hard to diagnose. This is something with server and/or file changes made on server causing some corruption ... That's why there is no "bug" or no "fix", because from X3, there is nothing that can be fixed. The $_POST is therefore CORRUPTED at some atomic level.
To diagnose even further, I would probably want to do this: Start deleting files in error server. Does it still fail when there are 0 files? Start removing items in page.json .. still fails? At the end, you are left with a naked folder name, and if the flaw is there, it's some files-based server/client read/write corruption which is beyond what X3 can handle. To be honest, it already looks like this is the case.
PS! You might want to disable Settings > Advanced > Store image settings in image as IPTC, as this is normally my first suspect because it edits IPTC in images when you save. The reason I can't see this is currently related, is because the folder works fine when copying all the images into different dir (new-york-city-copy). It would remove variables if you could disable this option though ... It's only useful if you are editing titles and descriptions and later on need to move files into other dirs while retaining the edited titles.