By “changed the config folder name” I assume you mean you changed “wp-config-sample.php” to “wp-config.php”?
Also, unless you were just in a hurry above, the actual link would be
site/wp-admin/install.php
Only thing other than that I can think of is that perhaps the domain you’re using isn’t resolving properly?
There should be 3 directories and 20 files in the directory for WordPress, so you said 23 above, which I guess could be the same breakdown.
Do you have a temporary address / alternate url to try for teoubleshooting purposes? Like ip_address/~username/ or something, just to see if it finds /wp-admin/install.php?
Yes and yes to your first two questions 🙂
My domain not resolving properly, would that be a host issue? I’ve got an email in to them, to see if there’s something on their end that needs to be changed.
And sadly, I’m not quite sure what you mean by an alternate url.
Thanks for your reply!
Usually, with most hosts, there is a temporary url to access yours site until your domain resolves properly, or if for some reason your domain is not working.
For example, if your domain name is MyNewDomain.tld, but the DNS hasn’t resolved yet and it’s not working, you can use the address the host gives you so you can still access your site via http and get to work while the DNS sorts out.
Example would be the ip_address/~YourUsername/
When your domain name resolves, ip_address/~YourUsername/ is the same as going to MyNewDomain.tld. Domains are a funny thing at times. I’ve seen a domain resolve through DNS in 5 minutes (yes, literally), but it can take up to 72-96 hours to fully resolve throughout the internet DNS structure. Usually, it’s less than 24 hours, but I have seen it take close to 72 hours before.
Can you go to just your domain name?
Granted WP will produce errors, but can you get anything from just going to the domain without the /wp-admin/install.php behind it?
Oh, I see what you’re saying. Yes, I can go to the domain, though it just shows a “this domain has just been registered page” since I didn’t create a parked page for it.
I decided to try it differently and do the “subdirectory” thing, renaming the directory blog. Now, when I try to go to mywebsite/blog/wp-admin/install.php
I get the fatal error message
Fatal error: Call to undefined function: wp() in /homepages/23/d161111088/htdocs/blog/wp-config.php on line 5
Ok. That at least is a positive note so far. That says your domain is ok at least.
For the record, you can remove the hosts default page in your htdocs directory.
Now, for the problem.
By that error, it says line 5 of wp-config.php is calling the function wp, and it doesn’t recognize that function. Funny thing, is that line 5 of wp-config justs defines the pw for your db connection.
Is this a fresh install? It sounds like it.
Could you try removing all the files, and completely starting over with fresh files, including creating a new config file. I say this, just so that you get everything cleaned up from your testing.
You could go back to using the htdocs directory (site root) as well. Just remember to take out the hosts default page (usually index.html, or similar).
Also, triple check you have the right username, pw, db name, and db host as well to be on the safe side.
Okay, I did that and now I got this message:
There doesn’t seem to be a wp-config.php file. I need this before we can get started. Need more help? We got it. You can create a wp-config.php file through a web interface, but this doesn’t work for all server setups. The safest way is to manually create the file.
Never mind. All the files didn’t copy. Duh. Now I have this. I swear, I don’t know what the heck is wrong.
Fatal error: Cannot instantiate non-existent class: wp_query in /homepages/23/d161111088/htdocs/blog/wp-settings.php on line 201
I did it! I had to manually type in the information to the config file (not copy and paste) and reinstall everything.
Thanks so much for your time and patience. I appreciate your help. I guess perserverance pays off 🙂
Cool your working now.
Sorry about missing your last couple of posts.
Been fighting an infinite redirect loop issue with apache. 🙁
