Tech Support

WordFence Never Again

This entry is part 3 of 3 in the series Plugins I Must Avoid

WordFence is not a plugin for novices or amateurs.   It isn’t a bad plugin, it is well-developed, supported, and maintained.  It is powerful and will take your site down if not used with proper knowledge.  If you simply remove WordFence your site will go down – there is a process to follow with that too. I …
Read more

Cron disabled, but where?

I have been dealing with so many issues after my sites were migrated that I lost track.  I need cron, the issue is that cron status is disabled.  But in the Config file, it is not so.  I used WP Config File Editor to take a look:   I used Cron Status Checker plugin. ( ):   Cron …
Read more images mess up

This entry is part 2 of 3 in the series Site Transfer Giganet 2016

My images are goofed up on  A letter to Tech Support at Giganet.  Because I am totally confused!  This is just for keeping track. Hi, I have a lot going on, a lot of messed up things on multiple sites I can’t keep track of, and I am still confused.  This is a huge …
Read more

How images work on host Giganet

This entry is part 3 of 3 in the series Site Transfer Giganet 2016

I do not understand this yet.  But I need to!   From tech support at my new host, Giganet: Hello The image source is set to It’s like you when you have included this photo in your article, you used this external url as source and didn’t upload it on your server. You can include …
Read more

Cannot post or Google Search Verify

New problem on but possibly the entire WordPress MultiSite network on I cannot post or verify with Google site ownership “cannot connect to server”.    Today I got  500 server timed out error.  Sigh.  Been de-activating and deleting plugins to no avail. 5 Feb.  No response Host Hoot support. Moving to another …
Read more

Disable bots

Host Hoot Support || Staff 01/31/2015 20:00 Reference: View Ticket #371897 wp-includes error (I think this is   I have added add the following code inside your .htaccess file to disable bots to be executed under your domain. === RewriteEngine On RewriteCond %{HTTP_USER_AGENT} (googlebot|bingbot|AhrefsBot) [NC] RewriteRule .* – [R=403,L] ===