MediBid

I found this thread for the same issue of “Older Entries” getting a bad URL (.com/blog/blog/?paged=#) and after reading through all of this I think I may have found a good solution for anyone else out there:

Esmi is right:

Did you check your theme template files to see how the navigation links were being generated? Have you checked your Blog and Site urls in Settings/General?

I know it is the theme as I have had the problem ever since adding the theme. But because the wordpress address and site address were different, I was getting the extra blog/ in the theme. I didn’t want to pay the $68 for the theme support if I didn’t have to, so this is an alternate solution. I noticed in the theme it was creating .info/blog for the older entries and I know the .info forwards to .com/blog thus giving me .com/blog/blog I’m sure this can also be edited in the theme, but I couldn’t find it in the code and this solution fixed another issue I was having with the sitemap, so I’m happy.

Solution: make the wordpress address and the site address the same in the Settings/General of wordpress. Forward a URL to your wordpress page a different way (like in GoDaddy).

please run 1 job than the folde will create automaticly

I think that piece of information needs to be in the installation information. I had same issue, but as soon as I let it run without creating the missing folders myself, I got results.

OH MY GOSH! The blog is back!

Thank you for your help, esmi.

Spoke to a new GoDaddy guy, who knew something about wordpress. He verified that as long as I can access the reame file, it was not a server error. He said to rename all of the plugins and then open the website. Now I can systematically check the plugins until I find the one that did this to my page. 7 hours of my work day gone for this issue, whatever it is.

So – for anyone else who finds this post because they have an error: go into your files, via GoDaddy or your own FTP client and rename all of the plugin directory folders in the wp-content/plugins/ directory. No .htaccess file needed, and possibly no need to re-install all files. See if renaming each plugin file (I just renamed the directories by adding a number to the front so that I would still know which was which as I re-enable them later) fixes your issue first.

Oops. I thought that was a standard file. Gone now.

Ok, new database – so install the same fresh files all over again, including new content files, but in a new subfolder, or is there another step that will involve registering a new wordpress with new admin and new passwords and recreating that whole wp-config.php file?

You know, I think I misunderstood the support guy. I thought he was saying that I needed to check the PHP on WordPress and on the server. You already said WP is compatible with the PHP5 on the server and that is what he was asking me to check. I’ve finished the files, and the blog is still down. I can’t even get into my admin panel. So I’m once again out of ideas and will call GoDaddy.

From the GoDaddy Dedicated Server Support guy:

Server Concierge: The following files work without issue in the /blog folder:
https://medibid.com/blog/readme.html
https://medibid.com/blog/license.txt
As such this is an issue with the coding or WordPress requires a higher php version that what is installed on the server.

Server Concierge: I would recommend researching the issue or referring to WordPress for assistance with this issue. I have confirmed that this directory is accessible and not experiencing any issues as you can browse to the 3 files provided above via a internet browser. I would also recommend checking to ensure that the wordpress version that you have installed is compatible with the PHP version that is installed on your server which is PHP 5.2.6.

Ok, I’ve replaced nearly every file with a fresh download of 3.0.3 and still nothing. I think the image folders are all that I have left outside of the content file. I took out the .htaccess file as part of the deletion of all old files and I didn’t add it back in since there wasn’t a file for it in the fresh download.

How do I check to see if the PHP version matches what is on the server (5.2.6)? I know if I call GoDaddy again, they will ask if I checked.

Ok, so here’s the big question if I re-install all the files – do I need to get new information for the wp-config.php file, or will the old data work?

I’ve checked the database and our webmaster has as well and nothing jumps out at us as a problem. I’m currently trying to find if possibly GoDaddy upgraded the PHP to 5.2.6 and if that is possibly not compatible with wordpress at all?

Would I lose all of my posts and scheduled posts by re-uploading all files? I’m assuming that those all live in the content folder? I am not the original installer of our WordPress, but I’m sure I can find instruction forums for a re-install. Do you think it would work? I’m trying to lose as little as possible.