Changing directory now cannot get into admin
-
I was trying to follow directions from http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory to redirect from a pre-existing subdirectory to the root directory. I made a mistake in the index.php:in copying, adding a line, and moving it. Now I cannot access the site nor the wp-admin.
My install is at: im.mikediane.com/wp
The root directory I was trying to use was: im.mikediane.com
I had changed the site address on the General panel.Can anyone please help?
Thank you,
Diane
-
Very good you already answered the next few questions I had in mind. So your primary domain and all your subdomains except im are 100% intact? Is that correct? All the websites and all the dashboards are OK except for im.mikediane.com ?
If the answer is yes, next I’ll need to know what all files and folders are present within the root folder of im.mikediane.com ?
Hi, PW Diane. Could you please confirm for me that you have an index.php file *both* in the root of im.mikediane.com *&* in im.mikediane.com/wp?
All is well on all the other site. Martin.
Yes, I have an index.php in both the root and in im.mikediane.com, Jackie.
Thank you, both.
I have to sleep now. I’ll check in in the morning.
DianeDiane, get some sleep, by all means. When you can, please go to:
http://im.mikediane.com/wp/wp-login.php
Log in w/your username & pw for that site, if you would, please. Now, when you get the 404, please go to the address bar & copy the address you’re getting & paste it into a reply so we can see it.I am 15 hours behind you, if I’m correct that you’re in Malaysia. Just goes to show, I guess, I’m nearly a day late & always a dollar short lol, but always have enough nonetheless.
The /wp-login.php aka /wp-admin (dashboard) is a much more complex url than the / (public facing website).
In other words, when logging in to dashboard there are authentication methods and sometimes various internal core redirects in place, which are not present when simply viewing the site.
For these reasons I believe it is easier if not also important first to troubleshoot and repair the / url public facing site. Further, I expect when the public facing site is repaired, the dashboard login also will have become repaired with no additional effort. Does this make sense?
Thus, my request to learn first and foremost what are the file and folder contents of the site root folder:
next I’ll need to know what all files and folders are present within the root folder of im.mikediane.com ?
Do you have any other index files in the root such as index.html? home.html?
Ok, hello to the support team volunteers working on this 1:
Might I take the liberty to summarize, & let’s see if we all agree on the series events & Perhaps the summary might provide a bit of clarity as well?
Diane had a working install on im.mikediane.com/wp. However, she didn’t like appending /wp to the url. So, at that point, she copied her index.php file to the root & changed the line to:
require( dirname( __FILE__ ) . ‘/wp/wp-blog-header.php’ );At that juncture, she seems to have had a working homepage, but was unable to login using the /wp-admin url, as it simply redirected to the homepage. She was, however able to reach a login screen by using im.mikediane.com/wp/wp-login.php . She states, however, that after entering her username & password, she was then redirected back to the homepage.
Martin made the suggestion that she put the appropriate site url in her functions.php file. The result appears to be that the homepage now no longer functions. I guess my own feeling regarding that is that it was a good idea, but, since that appears not to be working, perhaps it should be removed. Since Martin suggested including it, I’ll leave it to him to recommend its removal or not, as he sees fit.
She also stated when asked to login using im.mikediane.com/wp/wp-login.php prior to adding the siteurl to her functions.php file:
“I indeed get to a page with the log in form (it is without any css), but when I enter my user name and password, it just takes me to the home page of my site without the css. It is ugly.”That almost suggests to me a broken theme, which could, in fact, be the cause of this entire problem. I had suggested renaming the plugins & themes folder in an earlier post–we haven’t done that yet–& it might in fact prove instructive.
So here’s a plan I propose. What do the rest of you think? Any other suggestions?
1) Have Diane describe, as best she can, the folder structure of her server. Also make sure there are no files such as index.htm?, home.htm?, etc.
2) That the entries in the functions.php be removed at Martin’s discretion.
3) That she create a .htaccess file, both in the /wp subdirectory & the im.mikediane.com root directory. The file would consist of the basic WordPress .htaccess file, the only difference between the 2 files being RewriteBase / should be in the .htaccess file of the root of the subdomain, while rewriteBase /wp should be in the /wp .htaccess file.
At this juncture, an attempt to login should likely occur. If things don’t work as anticipated, then I’d suggest
4) Rename the plugins folder & try to log in again. If that works, do the usual–rename the folder back, change all but 1 of the plugin folder names in the plugins folder, etc.
5) If it doesn’t, then rename the plugins folder back & rename her current theme folder & try logging in, from which point, hopefully, she can reset her theme to a default one.
That’s obviously contingent on the site file system being in order,of course, but somehow I suspect that is in fact the case. Thoughts, yall?
Jackie, Thanks for the summary, at least for the benefit of others. I personally have followed the entire thread in detail. And I apologize for what might be considered my premature suggestions to edit anything.
1) Have Diane describe, as best she can, the folder structure of her server. Also make sure there are no files such as index.htm?, home.htm?, etc.
I think Diane has done enough to describe the subdomain and folder structure of her server. All sites except the im subdomain are OK. So we only need to concern ourselves with the folders and files within that subdomain. Which is exactly my last previous request.
next I’ll need to know what all files and folders are present within the root folder of im.mikediane.com ?
Regarding your items 2-5, these all constitute modifications to the site. And it is my opinion any and all mods to the site at this time are moot, and would serve only further to confound. There is no site, it is dead so to speak, as evidenced by the blank white screen at http://im.mikediane.com/ …
In other words both you and Diane might easily understand: Before we attempt modify a site not “alive”, shouldn’t we attempt first to “resurrect”?
Which is 1 reason, Martin, I hoped you’d consider suggesting the edits to the functions.php file be removed. At least that way, I think, we can get her back to the homepage she had originally. But I don’t feel it’s appropriate for me to do that. The last thing I want to do is step on toes here. This was actually Radices’s thread first–the only reason I intervened at all was because it appeared to me that perhaps Diane had erred in following the Codex’s instruction, which in fact she had evidently not done. So–in retrospect, I should likely not have intervened at all, & the person who should be apologizing is me. Now that I’m eyeball-deep, however…
The summary was as much or more for myself, to be honest, i.e., to see if I had missed anything & to try to clarify things in my mind. I guess I was also hoping that we could somehow come up w/a unified plan for Diane to follow so we weren’t all asking her to do 100000 different things all at the same time lol. She’s done really well at keeping up w/everything, I just want to try to minimize confusion for her if at all possible. It’s tough–she’s dealing w/a broken site, doing cross-cultural ministry, the dear Lord only knows how many different timezones, & 3 of us giving instructions–I was just hoping to try to simplify things for her, you know? It was just a thought.
Thanks again Diane, I appreciate your gracious consideration for the other forum volunteers. Myself, I guess I tend to get abruptly to the point when I sense the least little deviation.
Yes the “resurrection” will have to involve resetting the two database options, but they depend on file and folder structure so that has to be repaired first. And begining with the core, then the /wp-content/ , then the /wp-content/* uploads, plugins and themes.
I think it’s going to be really easy at this point:
- Delete everything except /wp-content from the root. if /wp-content is present, rename it to /wp-content.old
- install to the root a brand new wordpress core as per the manual installation procedure.
- move the /wp/wp-config.php and /wp/.htaccess to the root
- move all the contents files and folders of /wp/wp-content/* into the new core /wp-content/. If there is no /wp/wp-content/* contents , likely find them in /wp-content.old/* … maybe check this first before deleting anything at all, ie where are the uploads, themes, and plugins?
- remove the options settings from functions.php
- put proper options directly into database instead, these both will be http://im.mikediane.com as we have rebuilt the site in the root which was Diane’s intention that started this thread in the first place.
I think that is it.
Why don’t you and @radices tell us if you think this makes sense and if there’s anything missing?
Good morning to both of you. I greatly appreciate your interest and expertise in this complicated situation. I appreciate all of you who have been helping and I haven’t minded in the least trying to answer all the questions to the best of my ability. I’m not primarily a techie, I came to web work in my mid fifties, so my technical know-how is limited. Yes, Jackie, I am in Malaysia. That was a good guess. I’d love to correspond with you more after this mess is cleaned up.
_______________________________________________________
I will start answering from where I left off last night.
When I log into: http://im.mikediane.com/wp/wp-login.php
this is the url that shows up after login: http://im.mikediane.com/wp-login.phpThe files in the root directory are: cgi-bin, wp, error_log, index.html, index.php. I deleted the index.html. Interestingly, when I tried going to the site with both addresses, I now get a error 500 and when I try the wp-login, I get a error 404. I don’t know if that is significant or not.
Ok, Martin, I’m looking at the process you have outlined. That is what I have wanted to do all along, but couldn’t figure out how to do.
There is no wp install in the root directory. So, I assume my next step is to put a fresh wp install manually there. I’ll do that and get back to you before I go further.Thanks so much!
DianeOK, I have another question. I made a new database as requested. I downloaded a new wordpress as a zip file: wordpress-4.2.2. I extracted it and uploaded it to the root directory. Since the url: im.mikediane.com/wp-admin/install.php didn’t work, I used: im.mikediane.com/wordpress-4.2.2/wordpress/wp-admin/install.php
That worked. It opened the set up instructions. But I think I should have just uploaded the files and folders inside the folder called: wordpress. Should I delete what I installed or try to move it or rename it? I don’t want to make any more mistakes!
Thanks for your hand-holding! I really, really appreciate it!Diane
Diane, might I ask a question here? Does your CPanel have any autoinstallation scripts like Fantastico, Softaculous, or something like that? Maybe this would be the better way to go? It’ll create your database & install WordPress for you. Sometimes, these autoinstallers want to install to a separate folder, i.e., wp, but just keep vigilant, & erase it from the edit box to install to the root. If you extract the files to wordpress, you’re going to have a similar problem to the 1 you had w/installing to wp.
Actually, I looked at your sites, which is why I felt you were in Malaysia. So–guess, yes–but hopefully a rather educated 1 lol.
Well, I took the chance and just ftp moved the inside files and folders to the root and all is well. I’ll follow through with the set up as directed by the program.
DianeWhen I go there, I get:
WordPress › InstallationWordPress
Select a default language
English (United States)Continue
Is that how it should appear?
The topic ‘Changing directory now cannot get into admin’ is closed to new replies.