Hmm, that's strange. Is there any chance that you have changed the user permissions, and/or are using an account that is not an administrator? It's possible, for example, that your current user / user group has edit permissions, but not view draft permissions. So when you edit a description, it reverts to draft - but then your user / group is not allowed to see it!
To check the permissions, make sure you are logged in with an Administrator account. Go to Admin > Groups, and under the archival description permissions, check that the permissions are set to Grant for Update and View draft. If you've modified individual user permissions, check the same for the specific user account. It's also possible to add per-description permissions in AtoM, so check if any of those exist for the description in question as well! See:
If it still doesn't work, and/or you are already using an administrator and have not changed the permissions, then I would recommend that you make sure that the filesystem permissions are properly configured. AtoM expects all files and directories under the root AtoM installation directory to be owned by the www-data user. If you have followed our recommended installation documentation, you can try resetting your filesystem permissions with:
- sudo chown -R www-data:www-data /usr/share/nginx/atom
I'd also recommend that you try running the following maintenance task as well - run them from the root installation directory (i.e. /usr/share/nginx/atom if following our recommended installation instructions):
The first 2 commands will generate slugs for any descriptions that are missing them for some reason, as well as rebuild the nested set, which is used for maintaining hierarchical order (such as in the treeview) when data is stored in a relational database.
Now let's clear the application cache and restart PHP-FPM
Clear the application cache:
The command for restarting PHP-FPM depends on the version of PHP you have installed.
- PHP 7.0: sudo systemctl restart php7.0-fpm
- PHP 7.2: sudo systemctl restart php7.2-fpm
Finally try reindexing your site :
Let us know if this helps!