wp-admin/options.php 404 Error Help!

[aloud]

Hi,

I moved my site from localhost to hosting account, all fine so far and the site is displaying fine

When I got to the theme options to change the logo/styles etc and click save, it brings me to an error 404 page

Topic

[Jason Bobich]

Hello,

When you transferred your site, did you a full URL change of your site? Meaning everywhere you had localhost.whatever you changed to mysite.com in your MySQL database?

[John]

I’m having this issue. I have rechecked the db with interconnect/it serialized db tool and I see no instances of the old domain. I noticed another thread with this issue, but never saw any ideas on a resolution.

[Jason Bobich]

I would try doing your transfer again. There has to be a mistake made somewhere with how you’re transferring the site and swapping the data. This is the only instance I’ve ever heard of this, I think? What other thread had this issue?

[John]

the other thread is:
http://support.themeblvd.com/forums/topic/cant-update-options-after-moving-to-a-new-server/

[John]

When I update on the development server I go to:
http://crossinology.broomfieldwebette.com/wp-admin/themes.php?page=jmachildtheme&settings-updated=true

On the live server I just go to:
http://crossinology.com/wp-admin/options.php

which is a 404 error the file does exist with permissions at 644.

[Jason Bobich]

Hmm, yeah I see. Unfortunately, I honestly have no idea.

options.php is where all options are passed through in WordPress when you sanitize and save a set of options through the standard WP options API. Then, after WP does its thing, you get sent back to the original page.

So, if you’re stopping there at options.php, it means most likely some sort of PHP error is happening that is breaking the process. Do you have WP_DEBUG on? Are you checking your server’s error log? Could be tricky to diagnose.

[John]

Just an update for anyone who runs across this issue:
I am hosting the live site on GreenGeeks. I contacted support with the issue and they fixed it, giving me this explanation:

The problem was related to mod-security. So I have whitelisted the mode_security rule which caused this issue.

So, I guess check with your host, since I don’t know a way to overcome this on your own.

[Jason Bobich]

Yeah, that makes sense. If you check your server’s error log, that mod_security flag should be showing up, and would lead you to that conclusion (which is probably what your host did, I assume). I don’t know all that much about these things though, either.

[Author]

Replies