A 500 error could be anything. Without a proper error message (or a stack trace) it’s almost impossible to determine what causes the error.
Unfortunately this doesn’t make much sense. This chunk doesn’t get loaded or executed in the manager. You could try manually deleting the chunk again from the database table modx_site_htmlsnippets, but I doubt this changes anything.
I just spoke with my web host and they don’t see any signs of an attack. Now, I’m wondering how to fix the issue with the manager The HTTP ERROR 500 message with the header ‘Unable to process this request at the moment’ is still being displayed.
I have checked some things again now, and I cannot find a direct answer to the error in the logs. Has it not happened before that the manager was not accessible? I find it very strange that it suddenly stopped working.
Sure that happens. But there can be a lot of reasons why an error occurs. Usually an extra was installed that is not compatible, or a custom plugin was created that contains a syntax error. Maybe the PHP version of the server was changed and the installed MODX version doesn’t support it.
But the creation of a chunk with some text and some placeholders won’t crash the manager.
You could try different things: For example deleting the whole cache directory (core/cache) or deactivating the plugins (database table modx_site_plugins → column disabled) and see if that helps. But without a proper error message (from the server error log) it’s just guesswork.
Hey Harry, thank you so much for all your help, but I’m not making any progress at all.
I have now disabled all plugins, but it doesn’t seem to have any effect as all the plugins are still being loaded on the website.
The website itself is working perfectly fine.
I have taken a closer look at the logs, but I’m not sure what to look for. The specific errors that were mentioned are not being displayed.
None of the things you’re describing sound like they have anything to do with the FormIt changes you made. I believe, and I assume @halftrainedharry feels the same, that the 500 is coincidental but independant to the FormIt changes.
Some questions to clarify:
Are you able to access the login screen of the manager or does that 500?
What version of MODX are you running?
What version of PHP is the server running? This should be visible in your cPanel or by creating a php_info() call in a php file and visiting the URL.
If it were me debugging this kind of issue, I’d personally check to make sure that the file locations have not changed. It’s very easy to accidentally drag and drop directories in the Files tree inside MODX into the wrong place. This can definitely cause 500s (though you’d also get an error that the config file can’t be located). Other things to review include permsissions on files and folders, though normally, those don’t just throw 500 errors.
If you did disable all the plugins, they will not be disabled until you empty the site’s cache directory in core/cache/*.
It may be worthwhile paying someone to look at this depending on how much time you want to burn here vs someone just going in and looking and potentially seeing what you’re not.
Hello @Rykoutech, as the others have mentioned, we do need more information on the cause to find a solution. Also I wanted to mention that, even though you “only” created a new chunk: by saving you cleared the cache, and that’s why it could be from something else which wasn’t cached yet.
I’m personally guessing it is a php-error, so to find out why that 500 blank page error is happening, I would go on like this:
Set MODX to debug-mode (as you can’t access the manager, go into PHPMyAdmin, open the modx_system_settings-table and look for the setting debug: then set it to 1)
Via FTP or SSH delete the folder /core/cache/ recursively
Find out the real path to your modx-setup - and copy it somewhere temporarily:
if you have access via SSH, cd into your directory and type in pwd
if you only have access via FTP, go into your web-root and create a new file info.php with this content: <?php phpinfo();, then in your browser, navigate to this new file and look for document_root
Via FTP or SSH go into the folder /manager/ and edit the index.php, at the very top (after <?php) paste in this:
Now, you should start seeing some real error(s).
First try opening any manager-page in the browser.
If you don’t see errors in the browser, check the error-log you just set up.
We are mostly interested in the fatal errors, not warnings.
Please report back and let us know what you find out