Wordpress Login, Rendering, And Erorrs

  • Answered
Back in February I migrated my site from BlueHost to InMotion. The process went smoothly, except that I noticed my theme had a rendering problem in Chrome (it refused to show the necessary Divi fonts). I also couldn't login via Chrome. At all. It would redirect me to a page not found. I decided not to worry about, thinking maybe it was an issue that would catch up upon a new update of Divi.

This week, I noticed the rendering issues were still prevalent, the login issues in Chrome still happening, and all of a sudden my donate form wasn't directing people to PayPal after submission, but instead going back to the donate page. All of this only occurs in Chrome. It works in Mozilla and IE.

After two days of talking to countless support reps--who either couldn't find a solution, or gave up and just said it it's a caching problem (it's not, it's been cleared a million times), or a ISP DNS caching problem (again, not likely because it occurs on multiple computers throughout the city and on cell phones, too)--I finally decided maybe it was my site. I'd been hacked a couple of times at BlueHost, maybe it was just compromised beyond repair. So I had my account reset to the default settings and my site wiped.

Nothing's changed. After installing a new WordPress instance through the built-in cPanel scripts, I'm still having login issues in Chrome. I put in my user name and password and it refreshes back to the login page (better than a page not found, but still very annoying). Even if I put in a bad username or password, I don't get an error. Just a refresh.

After using Mozilla to login, I attempted to see if my rendering issues were still there. I downloaded a fresh version of Divi from ET and uploaded it. And promptly got three errors, which first popped up when I migrated, but went away.

Warning: Error while sending QUERY packet. PID=207580 in /public_html/wp-includes/wp-db.php on line 1811

Warning: Cannot modify header information - headers already sent by (output started at /public_html/wp-content/themes/Divi/functions.php:96) in /home/echofo5/public_html/wp-includes/option.php on line 823

Warning: Cannot modify header information - headers already sent by (output started at public_html/wp-content/themes/Divi/functions.php:96) in /home/echofo5/public_html/wp-includes/option.php on line 824.

My rendering issues are also still there. The Divi module fonts get a 404 in the Inspector Console in Chrome. But they're there in cPanel.

At this point, I don't want to bother with building a donate page, because I have a feeling the same issues are there.

I don't know what else to do. I've deleted my cache and cookies a million times, I've flushed my DNS in Command Prompt on multiple computers, I've uninstalled and reinstalled Chrome, I've deleted my .htaccess, I've added stuff to my .htaccess, I've set my site home and url home and my cookie domain in wp-config. I've manually moved fresh files over for wp-admin and wp-login.php through FTP. I've upgraded my PHP. I've uninstalled and reinstalled WordPress. I've Googled and Googled and Googled for the past three days. Nothing works. Nothing fixes the issues.

I have this theme working on all of my website--some of them hosted with InMotion on other accounts--and I've never had any of these issues before. Not even with BlueHost. The guys in support swear up and down the account and server are configured correctly. I don't really want to swap hosts again, but now I have no site and no answers and no fixes.

Hello, Thank you for your question regarding Login and rendering issues. I was able to replicate the login problems with a test WordPress installation on your server. I was then able to login successfully by Disabling Mod Security. This only disables basic mod security rules, but the major security features still run. Essentially, all rules are enabled by default, but the tool in cPanel lets you disable the rules when it necessary for running programs (such as WordPress). I left Mod Sec disabled so you can test, it can be re-enabled at any time if necessary. You may want to also contact Live Support to review the specific mod security rules your WordPress site is breaking. I recommend following our WordPress Troubleshooting guide for the other issues, specifically the sections on "Turn on WordPress Debugging" and "Disabling your Current Theme and reverting to the Default". This will help you narrow down the cause of the problems. Thank you, John-Paul