Brad

If you have a lot of traffic and WP Super Cache correctly configured and Cloudflare and it is still going over the limit, you need to upgrade your hosting plan. I would recommend at least a VPS for this site.

Try disabling all plugins and try editing. If that works re-enable them one by one and see which one is incompatible. And do ensure all your plugins are up to date.

You’re welcome. Where you change the inital page that is displayed when users come to your WordPress site is located in the following area of the wp-admin dashboard.

1. Go to “Settings” located on the left hand side then select “Reading”.

2. See where is says, ” A static page (select below)” … Just select the proper page you wish to have displayed.

3. Click Save and clear your browser and any caching plugins you might have running.

The Go Live plugin may not be under Plugin Settings it may be under the WordPress Settings mouse over or somewhere else. You’ll have to look around for it by hovering your mouse over all the sections of wp-admin on the left hand side. I am sorry I do not know off hand where exactly it’s located. It appears your site has been fixed and it now working properly.

I am not sure this is possible, does anybody else have any ideas?

Please try disabling all of your plugins. One may be incompatible due to a recent WordPress update where the plugin developer has neglected to keep their plugin up to date.

If you’ve canceled your hosting with Yahoo they more then likely have automatically deleted all your files off their servers upon cancellation. Your blog most likely has been deleted.

There is defiantly a control panel located at:

https://dadsofcomedy.com/cpanel

Please consult with HostGator regarding access to your cPanel account. Try your FTP credentials. I do not know Dream Weaver well enough to support it here, if all else fails look in your public_html directory for .htaccess using an FTP program called Filezilla. If it says there is no default editor for .htaccess use notepad.exe on windows or TextEdit on Mac. You can download it for free.

I see your currently on HostGator and HostGator has cPanel which you can in fact edit that file under “File Manager” BUT when you select “File Manager” and the popup window appears you must click the check box to show hidden “dot” files.

Check the .htaccess file ensure it has the proper URL/patch. Edit it as needed.

If the bad URL’s are in the database, you’ll need to install and properly run this plugin to replace all the old URL’s with the new URL’s.

https://www.ads-software.com/plugins/go-live-update-urls/screenshots/

1. Open your wp-config.php file on your hosts server via their control panel.

2. Directly under the line “<?php” put the following lines:

define(‘WP_SITEURL’, ‘https://example.com/wordpress&#8217;);
define(‘WP_HOME’, ‘https://example.com/wordpress&#8217;);

3. Replace “https://example.com/wordpress&#8221; with the correct URL of your WordPress site. Then try to login again.

Hope this helps!

Try creating a notepad file called php.ini (not pp.ini.txt) with the following line:

memory_limit = 128M

Save it and upload it to your main directory where WordPress is installed. If you are unable to save as a .ini file save it as a .txt and rename it once it’s been uploaded to your hosting account.

If that does not resolve the issue try adding the following line in your wp-config.php file, anywhere after the line “<?php”

define(‘WP_MEMORY_LIMIT’, ‘128M’);

If that does not work, you may have to contact your host.

I work in the support department for a web hosting company and most of the time I find the user did not actually configure WP Super Cache correctly, they just activated it and expected it to work but did not go into the plugin settings and properly configure and activate caching.

What is your domain? It could be that your WordPress site is the target of a automated brute force (password guessing) attack.

Install and activate the plugin “Limit Login Attempts” as well just for good measure.

Yes, this is a server side issue most likely related to the shared server configuration at your host. It sounds like they are using an Apache to Nginx or Varnish reserve proxy to serve pages faster and it’s either overloaded or mis-configured.