Hi,
thanks for your post, and sorry for the trouble.
Most likely, there’s some PHP code problem here then. To find out more, can you please set the WP_DEBUG constant to true in your site’s wp-config.php file, see https://wordpress.org/support/article/editing-wp-config-php/#wp_debug ?
After that, please try the CSS changes again. Instead of an “Internal Server Error”, you should then be seeing more meaningful error messages.
Regards,
Tobias
I recently migrated my sites to another host. It would seem that something happened that moved the custom css files to be directly placed in the wp-config folder, not inside the Tablepress plugin folder.
Do I move them inside the tablepress/css folder?
Hi,
no, the wp-content folder is correct! Placing them in the tablepress/css folder will not work (and should not be done, as that would mean that they will get deleted by WordPress when the plugin is updated).
Did you get any error messages with the WP_DEBUG constant set to true?
Regards,
Tobias
Solved. There were some behind the scenes settings with my web host. So they fixed it. Thanks anyway for fast responses.
Hi,
awesome! Good to hear that everything is working again!
Best wishes,
Tobias
P.S.: In case you haven’t, please rate TablePress here in the plugin directory. Thanks!
Hi there, i’m having this same problem and came across this thread via a google search. sandalsand – could you post what your hosting provider changed? or tobias, do you happen to know?
I’ve updated a few settings around php memory allocation and similar, i haven’t had any problems with other parts of my site. Tablepress too works totally find but trying to save the custom css gives a fast “Internal Server Error.”
Sorry. Don’t recall what happened!
Hi wholemilklatte,
can you please also try the suggestion above regarding WP_DEBUG to get more error information? You might also have to check the server error log file or ask the webhost for this.
Regards,
Tobias
Hi Tobias – i just DMd you (email) the output of the apache error.log that appears to be logging the exception. The WP_DEBUG log didn’t catch anything.
Hi,
thanks for that! From what I can see, the mod_security extension for the Apache web server is installed on the server (for enhanced security) – but configured too strictly, so that it raises a false positive here. It seems to dislike certain keywords in the HTTP request and (falsely) thinks that a hacking attack is going on. Then, it blocks the request, which leads to this error.
You will need to adjust/relax the configuration of mod_security on the server, maybe together with your webhost’s support team.
Regards,
Tobias
Cool, i guess i was seeing the same thing. i didn’t know if it’s possibly an issue in the plugin or in the security plugin. I’ll look into how to adjust it with my hosting provider. thanks!
Hi,
Yes, this is something that will need to be adjusted on the server level.
Good to hear that this helped!
Best wishes,
Tobias
problem solved – they sorted it on their end (i can’t modify those rules on my own but they were fine with whatever needed to be added).
Thanks for the quick reply!
Hi,
awesome! That’s great to hear! Thanks for the confirmation!
Best wishes,
Tobias
