An unresolved issue with functions.php update code
-
My site: http://im.mikediane.com is working. However, because there is a left-over issue with update code in the functions.php file, I can only access my admin page by using, http:im.mikediane.com/wp/wp-admin. (/wp/wp-login returns a 404 error)
This repair will take the help of someone who has done a lot of manual installs and troubleshooting.
Please read the topic: https://wordpress.org/support/topic/changing-directory-now-cannot-get-into-admin?replies=186
I am now using twentyfifteen theme.
-
It’s
http://im.mikediane.com/wp/wp-login.phpIf you leave off the file extension, the browser most likely thinks its looking for a directory that doesn’t exist (rather than the wp-login.php file).
Is it possible for @santeven to pop in for a moment to answer one question?
It looks like this is too sticky a problem for anyone to want to help. I don’t blame you!
I do have a question though, even though the functions.php and perhaps the config files and index are broken beyond repair,
Can I put a fresh wp install on a different subdirectory and use the same db? The db seems uncorrupted and I would like to use Theme Twentyfifteen.
Will this overcome the problems I have been having since I tried to redirect from a subdirectory to the root directory?
Thank you,Diane
It looks like this is too sticky a problem for anyone to want to help.
Diane, if you take another look at my response, I believe I may have answered your question regarding the 404 error you’re seeing at /wp-login.
(/wp/wp-login returns a 404 error)
Again, That’s because wp-login is a file, not a directory. use http://im.mikediane.com/wp/wp-login.php instead. It will take you right to the login page.
I can only assume by your response that you never tried it after I answered the first time.
While you may still have other issues, this particular 404 error is happening because you aren’t adding the .php extension when trying to access the wp-login.php file directly. The reason /wp-admin works is because it’s a valid directory that contains an index.php file. The reason /wp-login gives you a 404, is because it isn’t a valid directory. Again, it’s a file. You need to add the .php extension if you intend to access it directly.
When you mark it resolved (the other topic) you acknowledge no unresolved issues. So by mentioning unresolved issues here you have gotten off to a really bad start.
I can only access my admin page by using, http:im.mikediane.com/wp/wp-admin. (/wp/wp-login returns a 404 error)
This is the only well-defined issue you stated here. And the reply by @claytonjames is spot on. Vaild dashboard login url is http://im.mikediane.com/wp/wp-login.php or http://im.mikediane.com/wp/wp-admin/ and NOT the one you tried that returned a 404. He solved the problem you stated, you should mark this topic resolved.
Perhaps my suggestion for you to start this topic was in error. Everything we did is there in the other topic, and more, including the answer to your last previous question here, which indicates limited understanding of what all we did throughout almost 200 posts in that topic. Bottom line over there, we solved the problem you stated in the very first post, hence it is resolved.
If you want to attempt again whatever your objective that caused your problem there in the first place, I’m going to suggest at this time for you to spend some time and study that topic carefully all the way through yourself, instead of expecting someone else to do it.
Good Luck
For the sake of kindness and clarity I will attempt to answer your 3 questions directly. ( Nobody can eat just one ;| )
I do have a question though, even though the functions.php and perhaps the config files and index are broken beyond repair,
None of these 3 files appear the least bit broken.
The db seems uncorrupted and I would like to use Theme Twentyfifteen.
The database seems OK. And you are using theme TwentyFifteen, right?
Can I put a fresh wp install on a different subdirectory and use the same db?
Yes, you could, but I would advise not to try it again. That was exactly my suggestion in post 41. And for whatever reason resulted in what I referred to as a illegitimate “mixed installation” in post 91.
And everything we subsequently attempted was first to consolidate the mixed installation into a bonafide legit installation in the subfolder /wp/. This was accomplished first at post 148. You wrote:
Yay!!!
Will this overcome the problems I have been having since I tried to redirect from a subdirectory to the root directory?
Beyond post 148 we attempted what I call a “virtual relocation” ie remove the installation path /wp/ from the site url … So we took care of copying the /wp/.htaccess and /wp/index.php and editing /index.php … and we found that both the /index.php and /wp/index.php were all good at post 163. You wrote:
Ah, it’s magic!!!
But we still had not removed the /wp/ from the site url. All subsequent attempts to do so were confounded by what I now believe are leftover junk files in the root remaining from the mixed, double, “over”-installation way back starting at post 41. I requested, and you enumerated the root files in post 184.
https://wordpress.org/support/topic/changing-directory-now-cannot-get-into-admin/page/7?replies=186#post-6971527So there’s some answers and a recap. I’m going to stop now and give anyone else who might be interested a chance to chime in.
I owe both of you and apology.
First to Clayton. I didn’t explain my question well, so when you gave me your first explanation, I didn’t reply because I did understand that piece. What I didn’t understand was why my site could be addressed at: http://im.mikediane.com and my admin page had to be accessed by: http://im.mikediane.com/wp/wp-admin. I had used the /wp-login earlier in the process of previous work and it had worked. I was just documenting that it no longer seemed to work. I really did not mean to belittle your assistance. Please forgive me.Second to Martin. You are right, I did really get off on the wrong footing with this topic. I should have left well enough alone when we had gotten the site working in the /wp subdirectory. I love the way the site looks now with twentyfifteen and what others see is great. I don’t think I would have used it without your encouragement. I can use the admin page without any difficulties and I’m very pleased with that.
I got really frightened when you said “The caveat would be that your site likely will break if you ever switch themes or allow update theme twentyfifteen to a new version.”
I really do understand why you have wanted to quit working on this problem! I’m sorry it has gotten so long and so complicated. I will do as you say and study our previous work and see if I can get it all back and running on the /wp subdirectory and be content with that.
Thank you, both! I will mark this resolved. I will start a new topic if I cannot unravel the puzzle.
You are welcome, no apology needed, accepted nonetheless. To be as clear as possible:
I had used the /wp-login earlier in the process of previous work and it had worked.
This is highly unlikely.
my admin page had to be accessed by: http://im.mikediane.com/wp/wp-admin
Yes, because the install is in /wp/ the admin must be addressed there, either as /wp/wp-admin/ or /wp/wp-login.php
I didn’t understand was why my site could be addressed at: http://im.mikediane.com
This is possible because we put /index.php in the root and properly edited it. EDITED after I wrote to the end: I take that back it appears you have deleted the /index.php @pwdiane YOU ARE ON THE WRONG TRACK AS OF 22:09 EDT You better stop messing with it right now. Or are you just messing with me?
However, because we could not modify the site_url option without breaking everything, any further clicks into the site first addressed at the root would necessarily include the /wp/ installation path. It’s no big deal, that’s the url previously you have published, right?
Further the site is addressable at /wp/ because that is where we rebuilt it and is present /wp/index.php
I got really frightened when you said “The caveat would be that your site likely will break if you ever switch themes or allow update theme twentyfifteen to a new version.”
This is really no big deal. You like TwentyFifteen? don’t switch! Want to upgrade its version? First keep a copy of the functions.php and put lines 2 and 3 into the new functions.php after the upgrade is done. Better yet, save a local copy of functions.php right now, just in case it auto-upgrades without your knowledge or consent.
see if I can get it all back and running on the /wp subdirectory
As far as I know, your site is up and running at /wp/ just as it always was before you started the other topic.
Please, @pwdiane why don’t you post your proposed modifications prior to actually performing them? I don’t think any of us mind answering a direct, well-formed question. For me the more annoying part is trying to figure out what you did wrong when repeatedly ad nauseam you don’t remember or don’t tell us and post merely the symptoms.
Greetings @santeven,
When I reviewed what we had done, I was able to back up to the point where everything was up and working on /wp. At that point, I decided to just clear out those two update lines from the functions.php and, of course, everything continued to work well. I decided I had had enough of trying to redirect it and to just live with the /wp tail. In doing some other work, on another site, I discovered my web host had a redirect app built into the cpanel. It worked like a dream. So that is how I finally solved my problem with im.mikediane.com.
All your hard work and frustration with me was NOT wasted. You taught me so much about how to ask the questions and to document everything I did. I hope to be much better when I have another issue, though I hope it is a long time from now. 🙂 You are a great teacher and I’m sure will be able to help many more members. Hopefully they won’t be as clutzy as I was.
Thanks,
Diane
The topic ‘An unresolved issue with functions.php update code’ is closed to new replies.