Moderator
t-p
(@t-p)
– Have you tried looking in your server’s error log for clues?
– Please check the error logs on your server for a more specific error message and see why it’s failing. If you need help locating them, ask your hosting provider to help you with that.
Thanks Tara, But I already tried that no errors. 🙁
Moderator
t-p
(@t-p)
– If you cannot find error logs or if you don’t find any helpful info in the error logs, try Enabling debugging and post the results.
okay I found this.
[Wed Dec 02 19:58:04 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>, referer: http://mcmapspot.com/wp-admin/post.php?post=1352&action=edit
[Wed Dec 02 19:58:04 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>, referer: http://mcmapspot.com/wp-admin/post.php?post=1352&action=edit
[Wed Dec 02 19:57:35 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>
[Wed Dec 02 19:57:35 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>
[Wed Dec 02 19:57:31 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>
[Wed Dec 02 19:57:31 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>
[Wed Dec 02 19:56:59 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>, referer: http://mcmapspot.com/wp-admin/post-new.php
[Wed Dec 02 19:56:59 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>, referer: http://mcmapspot.com/wp-admin/post-new.php
[Wed Dec 02 19:56:48 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>
[Wed Dec 02 19:56:48 2015] [alert] [client 54.153.101.160] /home/mcmapspot/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>
[Wed Dec 02 19:56:03 2015] [alert] [client 54.153.101.160] /home/mcmapspot/public_html/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>, referer: http://mcmapspot.com/wp-admin/post.php?post=1352&action=edit
[Wed Dec 02 19:56:03 2015] [alert] [client 54.153.101.160] /home/mcmapspot/public_html/.htaccess: Expected </IfModule> but saw </IfModule>\xef\xbb>, referer: http://mcmapspot.com/wp-admin/post.php?post=1352&action=edit
take backup of .htaccess file and clean it up for unwanted code .
or upload a blank .htaceess file and see if it fixes the problem (go to permalinks and update them if upload blank .htaccess)
Thanks, but that didn’t work. Here are the new errors.
[Fri Dec 04 02:10:54 2015] [error] [client 54.153.101.23] File does not exist: /home/mcmapspot/public_html/404.shtml
[Fri Dec 04 02:10:54 2015] [error] [client 54.153.101.23] File does not exist: /home/mcmapspot/public_html/robots.txt
[Fri Dec 04 02:10:48 2015] [error] [client 54.153.101.199] File does not exist: /home/mcmapspot/public_html/404.shtml
[Fri Dec 04 02:10:48 2015] [error] [client 54.153.101.199] File does not exist: /home/mcmapspot/public_html/feed
[Fri Dec 04 02:10:37 2015] [error] [client 54.153.99.223] File does not exist: /home/mcmapspot/public_html/500.shtml, referer: http://mcmapspot.com/wp-admin/post.php?post=1404&action=edit&message=6
[Fri Dec 04 02:10:35 2015] [error] [client 54.153.99.223] File does not exist: /home/mcmapspot/public_html/404.shtml
[Fri Dec 04 02:10:35 2015] [error] [client 54.153.99.223] File does not exist: /home/mcmapspot/public_html/mclogin
[Fri Dec 04 02:10:29 2015] [error] [client 54.67.99.50] File does not exist: /home/mcmapspot/public_html/404.shtml
[Fri Dec 04 02:10:29 2015] [error] [client 54.67.99.50] File does not exist: /home/mcmapspot/public_html/thrones-pvp-xbox-360-2
Moderator
t-p
(@t-p)
Have you tried:
– deactivating ALL (yes all) plugins temporarily to see if this resolves the problem (plugin functions can interfere). If this works, re-activate them individually (one-by-one) to find the problematic plugin(s).
– If you can’t get into your admin dashboard, try resetting the plugins folder by FTP. Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder (if you have created such folder). The easiest way is to rename that folder to mu-plugins-old.
– switching to the unedited default Twenty Fifteen theme for a moment using the WP dashboard to rule out any theme-specific issue (theme functions can interfere like plugins). If you don’t have access to your admin area, use FTP , or your web-host’s cPanel or whatever file management application your host provides. Navigate to /wp-content/themes/ and switch to the default theme by renaming your current theme’s folder by adding “-old” to the end of the folder name. Alternately, you can remove other themes except the default theme. That will force your site to use it.
– If all the above steps do not resolve the issue, then try MANUALLY updating. Download a fresh copy of the WordPress .zip file to your computer, unzip it, and use that to copy up all files and folders EXCEPT the wp-config.php file and the /wp-content/ directory. You may need to delete the old wp-admin and wp-includes folders and files on your server before uploading the new ones.
–Backup: If you haven’t already done, always backup everything (including your database) before doing any actions, just in case something really goes wrong.
