Roger Lipera

Hello ejcabquina,

Thank you for your reply. It is very much appreciated. I have checked the home page and there is no evidence of a WPSP shortcode. I do not have the ability to look for PHP snippets as I have not worked with PHP on the nitty-gritty level for a very long time and, to be honest, it is “not my thing”, as they say.

You description of how the plugin works makes sense, and I think it may help with tracking down the problem. I have conferred with the site’s owners and they are satisfied to keep it as it is now, and if I can solve the issue we will re-activate the plugin.

Thanks for your help. I like the plugin and am hoping I can use it on other projects.

Again, thank you.

Michael,

That did it! Perfect!!

The “trick” is in the Customize > Additional CSS

Very, very nice. The “cats” will be very happy.

Thank you.

Thank you, Michael,

I tried it, but, alas, no luck. I even experimented with variations and there was no change.

I will keep trying.

Thank you, again.

Roger

@logankipp,

Done! You are totally 100% correct. All is now good with SiteLock and I am very pleased. I hope that it is clear now days with the host company that there is no problem.
I am very pleased.

Wendy,
There is one other thing that I totally forgot about! The CDN feature does not work with the free SSL and will give you a similar, if not identical, error. You probably know that you will find the CDN switch when you log into your Bluehost account and click the WordPress Tool link at the top of the page. At the Performance option (on the left) you will find the CDN switch. Apparently it has to be Off.

I ran into this several months ago and totally forgot about it. It was one of the phone techs that told me about it.

The last few days I have had major issues on my site stemming from a bum SSL certificate. The techs removed the old certificate, put in a new one, and the propagation process started. But, when I checked my site much later there was a new, but similar, error message. I spoke on the phone again late last night, but the tech was convinced it was still slow propagation, and my own checking seemed to indicate that was right. But, because I am sort of a nosey kind of person, I was checking my account when I remembered the CDN issues. Somehow my CDN switch was on, which it should not have been. The moment it was turned to Off the problem with the site cleared up.

By best guess, and that is all it is, is that during the SSL fix process that switch magically got turned on. When I not-so-magically turned it off again, the site was repaired.

So, now with the SSL fix that the phone techs instituted and the CDN switch to off, my site is happier than garlic on bread … with butter!

Yes, this is absolutely true, the Bluehost free SSL and SiteLock are not compatible. If you run into this trouble, call them on the toll-free number. Do not use the chat. The chat people have much trouble with this, the folks on the phone will simply turn off SiteLock and all will be fine.

I have run into this on all of the Bluehost WordPress sites I manage(d) and the conflict is a problem. Remember, do not use the chat! Call them on the phone.

The problem turns out to be even more confusing that described above. Yoast is, apparently, not the problem, but merely the signifier of the problem. Yoast was not working because something else was going on.

As it turn out, in another forum moderated by Mr. Huff, I believe his name is, he suggested adding –

define(‘CONCATENATE_SCRIPTS’, false);

just under the –

define(‘DB_HOST’, ‘localhost’);

line in the wp-config.php file. Once I did this everything worked fine again.

For those of you who might run into this problem, be advised that I removed all caching plugins and did a thorough “house cleaning”, too. None of that solved the problem, but it didn’t make it worse, either. However, once that line was added to the file, everything worked immediately.

Problem solved!

The All-In-One Migration plugin was causing a problem. In short, it created an error that overwrote the .htaccess file when Permalinks were saved after changing.

The solution was to re-clone using another tool. In this case I used WP Clone from Clone Academy.

I have already removed all the other plugins and excess goodies before the final “test”, which failed. A re-cloning with WP Clone worked fine. No problems.

Yep, did that. Doesn’t work. Still fails spectacularly.

I’ve been on with Bluehost and no luck. I think I know the problem. I am going to try an experiment.

Perfect! That is excellent. Thank you for the help. I believe that will do the job exactly.

Again, thanks!

Perfect!! Fabulous!!!

That did the trick. Thank you for your extremely quick fix on this.

Again, thank you.

Roger

Yes, I also have the very latest version.

Thank you.

Roger

Hi!

I have PHP 5.4.43.

I am checking the error log and will report back.

Thanks.