It’s unlikely that this is the correct error message.
In the developer tools → “Network” tab, is there by any chance an error message in the response of the request with the 500 status code?
Click the request and instead of the tab “Headers” (as in your screenshot above) select the tab “Response”.
Well without an error message it’s hard to find out what causes the 500 error.
Is it possible to (temporarily) set display_errors to On (in the server config) to show errors on screen (or in the “Response” tab)?
Is it only Minishop2-Product-resources you can’t save, or all MODX resources?
For self-hosting, it’s in the configuration file php.ini.
If you are using a hosting provider, then maybe you can activate it somewhere in the control panel. There’s no general answer. It depends on the provider.
I have noticed that the “is being saved” display keeps running continuously, but changes in the resource are displayed/adopted after the display is ignored. However, when I try to create a new product resource, the following error is displayed in the frontend: Fatal error: Array and string offset access syntax with curly braces is no longer supported in /htdocs/modx/core/components/pdfresource/vendor/mpdf/mpdf/mpdf.php on line 2349.
So, do I have to update PDFResource because PHP 8.0 standards are not met? That would be my worst case…
These are all mere “PHP warnings”. The code still works correctly. It’s just that now in PHP 8 a warning is created.
What is the snippet with the ID = 12?
If it’s a custom snippet, then adjust the code on line 56 (or 110 for the other warning) to be correct in PHP 8.
If it’s from an extra, then the code will probably get fixed by the author of the extra in the next version.
This is also just a warning. Maybe try to fix the code yourself.
Or switch to a different extra (like “emo”). I can’t even find this extra in the extras-repository anymore, or on Github.
Do you have the latest version of the extra PDFResource installed? Version 2.0.1-pl?
There is an event OnDocFormSave that runs after a resource has been saved.
If a resource is saved correctly, but the “save”-request fails, then usually a plugin that runs on the event OnDocFormSave throws an error.
You could go to the system settings page (manager/?a=system/settings), then change to the tab “System Events” and filter by “OnDocFormSave” to see what plugins run on this event.
Then maybe temporarily deactivate them one by one to see what plugin causes the error.
For now, I will deactivate the AntiSpam extra and then look for an alternative…
I have not installed a new version of PDFResource, as strangely, all my settings were lost in two attempts to update it. For testing and finding the error, I have deactivated the extra…