Cr00zng

WPyogi… you’re the man! Or the woman, since the name is non-discriptive ??
This has fixed my blog site:

# Use PHP52 as default
#AddHandler application/x-httpd-php52 .php

A big thanks for your help!

The new installation of WordPress had failed as well, by using the WordPress install.php via the browser, with the same internal server error. The failing point in the installation process was:

https://blogs.secure-bits.com/wp-admin/setup-config.php?step=2

In another word, after the database information had been entered and and the “Submit” button clicked.

Just for the kick of it, I’ve setup a new blog with different domain name by using the cPanel script at Inmotion Hosting, the installation had completed without any error. The problem is that the first login attempt to the new blog produced the same internal error message. The second login attempt had been successful; however, trying to administer the blog produces the internal error message at various points. In another word, it is not usable.

Yes, I’ve contacted Inmotion about this issue, but they’ve been giving me the runaround. My guess is that they’ve done some changes at the server level for countering automated WordPress hacks, that had been going on since April of this year.

Would anyone know about these changes at Inmotion?
TIA…

Yes, I can do that through my phpMyAdmin interface at my hosting company.

So, create a new database for the new installation. Then install a new instance of the WP 3.7.1, using the same renamed admin account and database prefix and same URL. Upload the child theme and the content of the “Upload” folder and then restore the database.

Correct?

The upload folder has lot of images from last and this year…

Yes, I do have a database backup for the working 3.7.1 site from earlier this week. There had been no changes since. I’ve also exported the content through the admin panel “Export”, just in case.

Yes, I do… I even have the backup for the 3.6.1…

Can I use the current wp-config.php file during installation, or do I need start from scratch?

Well, it’s probably easier to install WP 3.7.1 and restore the database, no?

The URL for the blog is https://blogs.secure-bits.com, currently the child theme is working.

One thing I’ve noticed is that running the upgrade.php does not ask for any account. It just states that the database updated. Is this a security risk?

Yes, I did re-upload the thwentythirteen theme…

It’s the same, after “Continue” the browser is redirected to the blank home page of the blog.

Trying to run the wp-admin/upgrade.php does state that the database up-to-date and clicking on continue redirects the browser to the home page of the blog site. Which, in the case of renamed parent&child themes, is a blank page.

OK, renaming the child theme folder does not break the site; however, it shows the blogs in a single column. Renaming the theme’s parent folder breaks the site. It does not seem to switch to the default theme.

Within the admin panel managing the themes results in internal server error message…

“renaming your current theme’s folder inside wp-content/themes and adding “-old”
That would be the child theme, correct?

I cannot actually manage the themes within the admin pages. I see the “twentyeleven child” theme in the admin page, but no other themes are shown. All the default themes are in the “themes” folder.

Maybe I should mention…

This is not a default installation of WP in a sense. The admin account had been changed and so was the database prefix during installation. The site has also been protected by Better WP Security (BWS), that was active during installation. In previous version updates through the admin panel had no issues with BWS. This is the first time I’ve encountered the error. I also have two other WP sites that had not been updated, due to this issues. The installation for these WPs was pretty much the same as the broken one, including changes at setup and plugins. These sites are hosted by the hosting company…

Yes, renaming the the folder “themes” to “themes_old” does the same. After clicking “Continue”, the browser is redirected to the broken blog site. Reversing the naming brings back the blog pages, just like previously…

I have followed your direction, re-uploaded all files except the the wp-content folder (renamed as wp-content_old) and the wp-config.php & root .htaccess files – from a fresh download of WordPress 3.7.1. Connecting to the blogsite.com/wp-admin/upgrade.php brings up the update windows that states:

No Update Required

Your WordPress database is already up-to-date!

Clicking on the “Continue” button, redirects the browser to the blogsite.com page, that is broken. In another word, it is a blank page now. Renaming the wp-content_old folder to wp-content via FTP does bring back the blog pages; however, trying to login gives gives the original internal server error message. It seems like a catch-22…

Do you have any other suggestion? Thanks for your help…