Dubsy

Hi,

Thanks for your response. I followed your instructions. I gave it two attempts and in two different chrome accounts still received:

*** Forbidden. Browser seems to be spambot. Anti-Spam by CleanTalk. ***

*** Forbidden. You submitted too quickly. You may try again in a few seconds. Browser seems to be spambot. Anti-Spam by CleanTalk. ***

Cheers,
Tina

I now have a sucessful result.

I had been playing in the backend and optimising my site with PageSpeed Insights. When I optimised some JS files to load on user interaction (rather than preload at the start or delay when they were seen as render blocking resources) this resulted in the lazy load feature not working. PageSpeed had flagged siteground optimizer assets as being a render blocking resource and I had added it the Flying Scripts plugin to see if it would delay (not defer) this script (without knowing what I was doing and even though it was the CSS that was flagged and not the JS) and this had broken the lazy-load functionality.

So technically, no plugin conflict. I just had to remove the keyword “siteground-optimizer” from the Flying Scripts field. Flying Scripts works well with Site Ground Optimizer by delaying external scripts like google-site-kit and cdn-cookieyes.com until user interaction or 5 seconds, which ever is sooner. I could keep tweeking but my mobile score is now 95 and PC 98, so I’ll rest there for now.

To add for anyone seeking a solution to the same issue, I was advised I could turn lazy load feature off as it was conflicting with something else I use (there was no attempt to discover what this was although I’m doing that now). We also discovered that it wasn’t just doing this on Safari, it was also in Chrome but occured when I wasn’t logged in to the site. (When logged in, I could see the images.) Turning off the Speed Optimizer feature for Lazy load allowed the images to reappear but now they aren’t lazy loading. Since then, I have a tried a different lazy load plugin and the same thing occured when activitating where most of the images (when logged out) would not load. In my efforts to resolve this problem so that I can have images lazy loading, I deactived Speed Optimizer completely and the alternative Lazy Load plugin worked. I’m still experimenting and testing. I have 6 websites and this issue issue occurs on all 6.

• This reply was modified 5 months, 3 weeks ago by Dubsy.

Okay. Took a few steps but I worked out how to navigate around the AI to chat with someone.

• This reply was modified 6 months, 1 week ago by Dubsy. Reason: solved the direct support dilema

I am unsure what resolved this issue. I noticed that there was a Cross-Origin Read Blocking error and began to go through steps to report this to chromium.org but at the same time lodged a report with my personal firewall provider of a possible partially blocked website. About 5 minutes after lodging that, WordPress became fully functional again.

Hello, Yes I deactivated all my plugins including Jetpack and then tried to install the update and it worked. I had no problem reactivating my other plugins after I installed the update. Sorry, meant to come back and post the steps I took. I’ll open the support ticket soon.

Thanks for looking into it.

7.1 – that’s the ‘safest version’ recommended by Siteground (or so my backend states).

Just wanted to add some further information as I have not discovered a solution to this on my own.

1. This is a fresh install of WordPress
2. I deactivated all plugins and themes except for the latest WordPress theme, cleared my cache but the error continued.
3. I have five other websites using this plugin (free version) on the same shared server (same version of PHP) which don’t give the error.
4. I tried uninstalling the app and reinstalling it again and still, it gave the error.

I’ve since deactivated it and tried a different SEO Plugin which doesn’t give the error.

I worked this out. I had the cover image on the once-classic post set to center on the page.

Uncentering the image removed unwanted CSS. With center selected for the image, my theme was adding the following CSS code:

.aligncenter {
    clear: both;
    display: block;
    margin: 0 auto;
}

The “display: block” parameter changed the appearance of the text over the cover image, uncentering it (vertically) and changing the font from white to grey.

My theme is Generate Press.

Closing this since I know what the problem is now.

I had resolved this thread – not sure if I need to start a new one – so let me know if that’s the case. I have reopened it though as I’m now told Sections is compatible and I’m also responding to the above by Marius.

Unfortunately, I’m still having problems activating Guttenberg.

I disabled the classic editor.
I then deactivated then reactivated Gutenberg, but when editing or starting a new post, the classic version appears.

I have now tried troubleshooting.
Reactiving Gutenberg.
But I get the message: “sorry your not allowed to access this page”.
After exiting the troubleshooter and when I try to edit or start a new past, it still defaults to the classic editor.
Now looking to see if it’s a BPS Pro plugin firewall issue.

Ah, thanks for your input Karen and Marius.

I think I will wait for Sections to be made compatible (they’re working on it) as most of my main pages use Sections and disabling will destroy the layout.

Marius, I’ll keep in mind to deactivate and reactivate the plugin when Sections is ready to be used with Gutenberg.

Thanks again.

(I’ll resolve this thread since I now know the issue.)

I’m also getting this warning across multiple WordPress sites so I would also like to add my voice to the request for a solution with the next update so I don’t have to keep editing the plugin. Cheers and thanks for a great plugin.

Looks good and I’ve reactivated my plugins including BPS without seeing any issues so far.

Thanks for all your help Jeremy (and AITPro too!).

Hi Jeremy,

They came back to me after the sending your suggestion telling me it should all work now, but I’m still getting a FAIL (2 out of 3 attempts failed) on the last test. (I notice a few others have posted a similar issue in September but not what resolved it for them.) I’ve sent them a copy of the FAIL portion of the debug script hoping this might point them toward something else that’s blocking the connecting.

Cheers
-Tina

I’m not sure what to make of this but I’m sure you have an idea. I’m still getting intermittent connection problems, between 50-70% of the time it connects and the other time it tells me there’s a problem. For my host when they tested they had a 100% success rate, I was only having 50% success.

When I look at the debug info when it fails, I see this:

TEST RESULTS:

HTTP: PASS
HTTPS: PASS
IDENTITY_CRISIS: PASS
SELF: FAIL

The fail means something isn’t working – maybe at my end – but I’m not sure what. I use Kaspersky for my own personal computer firewall so I don’t know if that would have an impact. Otherwise, I use Chrome 64 bit. I kind of grew a little impatient today (all my own fault – unfortunately, it’s a live site and I don’t like to leave it down for too long) and began reinstalling my plugins. I also took the opportunity to install a new Woocommerce theme with Woocommerce. I’ve still not activated BPS Pro. The 50% failure rate started before I began re-adding my plugins. I’ve had more failures with the debug since activating the plugin, Flamingo (but also a success too ) so not sure if there is also a plugin conflict since it’s not consistent.

• This reply was modified 7 years, 5 months ago by Dubsy. Reason: grammar