Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
That’s not good. Assuming it is that plugin doing it then try this
- Using FTP or whatever filemanagement tools your host has provided you with navigate to the
wp-content/plugins directory.
- Once there locate and delete the
theme-my-login directory. Just that one directory and nothing else.
- Try and re-login to your WordPress dashboard.
If it’s that plugin that’s causing the 500 error then that should resolve it for you.
Thread Starter
igors
(@igors)
Thanks for the quick response!
Did it – does not help.
Last update cache – at 6:03 am
Update plugin – at 6:04 am
No other action is taken – just updated the plugin …
Restart the system – does not help.
A manager is far away and can not: (
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Did it – does not help.
That’s also not good. 500 Errors (usually) means that your servers PHP is having bad day and not able to process the code it’s given. It’s technical for “Web server go BOOM”.
Do you have access to your web server’s error log file? Your host provider may be able to assist you with that to find where the problem is exactly.
Looking at a cached copy of your web server (from your profile here) I don’t think it’s a WordPress problem.
These do not work.
http://your-URL-here/wp-content/themes/arthemia/style.css
http://your-URL-here/readme.html
Those are static files and aren’t supposed to get processed by WordPress. Either it’s your web server or your .htaccess file so try this:
- Using FTP or whatever filemanagement tools your host has provided you with navigate to your WordPress directory.
- Once there locate and rename the
.htaccess file. Don’t delete it this time just rename it to .htaccess-old or something.
- Try and re-login to your WordPress dashboard.
If that does work then visit your http://your-URL-here/wp-admin/options-permalink.php and re-save your permalinks. That should produce a new .htaccess file for you.
Thread Starter
igors
(@igors)
Thank you!
It works!
The problem was .htaccess. After the upgrade, it was this:
==
# BEGIN WordPress
<IfModule mod_rewrite.c>
...
</IfModule>
# END WordPress
leshooting purposes only
# BEGIN WordPress
<IfModule mod_rewrite.c>
...
</IfModule>
# END WordPress
The problem is double?
Tell me, can I return the plug in place?
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Since it wasn’t the plugin that caused your problem then I think you can…
Thread Starter
igors
(@igors)
The fact that the file .htaccess was changed exactly at 6:04, as the plugin.
Is not this plugin to change it?
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
It may be but I’m not familiar with that plugin. If the plugin modifies the .htaccess file then it may have gotten confused with what was already in the file.
Try re-installing the plugin with what you have and see if the same problem comes up again. If it does then fix it as above and perhaps the plugin author will chime in on this issue.
The plugin calls the WordPress function flush_rewrite_rules on activation.
Thread Starter
igors
(@igors)
Hello, Jeff Farthing!
Do I understand correctly that the plugin changes the file .htaccess?
No, it doesn’t. It refreshes permalink rules and WP rewrites the .htaccess file.
Thread Starter
igors
(@igors)
Clear.
Just suddenly coincided update the plugin and change the .htaccess file.
Thank you!
