Home › Forums › WordPress Plugins › Hide My WP › I really can't get control of my admin after wp-admin name change
- This topic has 24 replies, 2 voices, and was last updated 9 years ago by
Suman M..
-
AuthorPosts
-
July 14, 2016 at 5:51 am #10629
Suman I’m going to do a backup restore and start over, deleting the HMWP entries in the database as before.
When in the admin I can search the security plugins for potential conflicts, and if nothing works I will try to find an alternative to this feature or just have to leave it out. 🙁
July 15, 2016 at 4:40 am #10642Okay, let us know!
July 16, 2016 at 12:34 pm #10669Hi Suman,
For the record and for anyone else that may encounter a similar issue, I couldn’t get this resolved. In the end I’ve opted not to change the admin name via HMWP, but only change the login path, which works fine.
No other option unfortunately, I can’t figure it out!
July 16, 2016 at 1:52 pm #10677This reply has been marked as private.July 17, 2016 at 2:20 pm #10704I haven’t tried switching to the WP default theme, but I’m not sure it would help me if it suddenly worked as I need to use the theme I’m on now.
I have an alternate method for testing that I’m trying now. If I discover anything I will update here.
Appreciate your help!
EDIT: Ok! Just did a little test. I set up a subdomain under the primary site URL using WP and the same WP theme, but only a handful of plugins (but the same security plugins). I tried changing both the wp-login and wp-admin names and they both worked first time without a hitch.
This tells me that it’s not some external setting affecting the entire server, or else it would affect both the main domain and subdomain WP installs the same way. It must be something within the primary domain installation that’s causing the 404 login loop.
I’ll do my best to figure it out, but I’m unsure how to start, since I already attempted disabling all plugins and bringing them back one by one, and that didn’t help.
-
This reply was modified 9 years ago by
Hyperknight.
-
This reply was modified 9 years ago by
Hyperknight.
July 17, 2016 at 2:33 pm #10707This reply has been marked as private.July 17, 2016 at 3:33 pm #10708Well Suman, mind blown!
I started going through htaccess and then wpconfig details of the primary domain and subdomain, making comparisons of what was different. Since the subdomain is newer, and only has some security plugins, it was emptier.
I looked for elements that were in the primary files and not in the subdomain files, and sequentially tried deleting them or changing the code.
After going through the htaccess, I was right at the end of the wpcongig comparisons when I found this code:
set_time_limit(90);
define(‘COOKIE_DOMAIN’, ”);
define(‘COOKIEPATH’, ”);
define(‘SITECOOKIEPATH’, ”);It was another element not present in the subdomain wpconfig, so I deleted it, and bam – the new admin name works, 404 eliminated!
I’ll leave this here for future reference for anyone with a similar problem, but I was hoping you could tell me what this code is, because I’m not sure if I added it, why I added it, or if a plugin added it, or what its function is!
Either way, with it gone the admin now works as it should. Very happy!
July 17, 2016 at 4:52 pm #10711This reply has been marked as private.July 18, 2016 at 9:35 am #10723After googling that code I think I took it and implemented it from this page:
Previously I had a redirect loop problem happening and I was trying to resolve it. I possibly tried the code and then forgot it was there.
Should I keep the “set_time_limit(90);” code then? I’m not sure what it does exactly.
July 18, 2016 at 10:52 am #10732This reply has been marked as private. -
This reply was modified 9 years ago by
-
AuthorPosts
You must be logged in to reply to this topic.