Keirwatson

OK. Got it. Thanks again.

On reflection, I am still left with some questions…

You say “All functionalities(combination, minification, async load) are not included in the wp-admin.”

But when I am in the admin>customiser, I can see using the inspector css coming from files such as “https://rosemarycottageclinic.co.uk/blog/wp-content/uploads/siteground-optimizer-assets/siteground-optimizer-combined-styles-49bac55ab2f1611dca7e6435fa991ce0.min.css”

So that suggests that the plugin IS still operating in the admin, or at least in customiser/live preview?

I can’t count. That’s three. THREE FEATURE REQUESTS!

I have the latest version (5.1.2)… Oh. You have literally just released an update! OK. so right now I have 5.1.3 ??

—

I think it was a browser issue. I use Safari and it can produce odd results when I have several tabs open displaying the backend/editor pages. Can’t get to the root of it yet. But a few days ago it seemed I could only view the edit page button in admin bar if I disabled sg-optimiser. Yesterday the problem returned, but was nothing to do with SG-O, and only resolved when I switched to chrome browser.

Thanks for the prompt reply.

Well dang it! It’s working today!!!

Yesterday I spend half an hour tracking down the issue, but today it’s working again. (I’m using a different computer, so perhaps it was a local cache setting? – although I did try clearing the browser caches)

Any comments? Is there a known issue here?

When in my site admin, looking at the loading circle in Jetpack notifications, I can see the following error in the console (Safari): ![Error] WebSocket connection to ‘wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data’ failed: Unexpected response code: 403 (x32)

I have found that the same problem occurs with all of my WordPress installations on Siteground. So I now believe it is a server configuration issue. I have contacted SiteGround (my host) and was shocked at their ignorance (especially as they recommend Jetpack! Support said:

“I’m not entirely sure if you are supposed to connect the site to wordpress.com if it is not hosted there, and I believe that this is why you’re seeing this error. And the site’s not hosted there (wordpress.com) – It’s hosted here (SiteGround).

I would recommend double-checking this with either the development or support team of Jetpack in order to confirm this, and if they do have any specific recommendations for any application or server changes, please let us know what they are. We’d be more than happy to test them out.”

I just found another clue.

I had not turned on the wp toolbar turned on, so activated it (little bell in corner of admin bar)

When I click on it there is a permanent loading circle and nothing loads.

Previous site: herbidacious.wordpress.com

I am using the same email address as before (the same one associated with my login to www.remarpro.com, WordPress.com and in my site dashboard. All use the same email. It’s a gmail account.

SiteGround does not permit php Mail function on WordPress, so requires WP Mail SMTP plug-in. That is supposed to send all site mail via [email protected]. As far as I can tell it is configured correctly and sends test mail properly. I do receive notifications when someone leaves a comment, but not when they subscribe, and when I post a new post, I do not receive a confirmation email myself. Not sure if subscribers are receiving them either.

Also, in GTMetrix (https://gtmetrix.com/reports/herbidacious.calamus.graphics/WyrtF5dV) you can see that there is a long delay waiting for

…/?relatedposts=1

Taking more than half of the page load time! (300ms)

I’ve just tried “Diagnose a connection problem” from the wordpress.com>settings>Manage Connections. It says:

“Unknown error
An unknown error has occurred.
If you continue to get this error, please check out our troubleshooting guide or contact support.”

I guess this could be the root of the problem?

OK. I’m trying this. And it’s weird.

All plugins removed (including custom css), using 2019 theme; all caches cleared (browser and Cloudflare)… turn on a fresh install of Jetpack and the related posts are still broken in exactly the same way as before!

[NOTE: I’ve switched back to GeneratePress and restored the plugins as the ‘clean slate’ did not reveal the problem]

—-

Here is a thought: I have recently moved my blog from wordpress.com to self-hosted at Siteground. The export / import procedure is rather fraught. The XML file had to be uploaded again and again as it kept timing out and freezing. some images did not port over properly, appearing as broken in the media library (this appeared to be related to the timeout happened during an image upload). It is possible that the timeout interrupted some posts too (I have noticed one is missing, but there might be others). Is it possible that a post-fragment has been included in the database and that this is causing the related posts to not show if they are trying to lookup a non-existent post?

—

Another issue (which may be related?) is that I am not receiving notifications when I get new followers to blog or when comments are left.

• This reply was modified 5 years, 7 months ago by Keirwatson.

I thought you had nailed it there!

SO when I changed to 2019 Theme, the related posts on https://herbidacious.calamus.graphics/2018/10/05/lily-turf-liriope-muscari-big-blue/ was showing properly.

Switched back to GeneratePress (my normal theme) and hey presto! It was fixed!

However, when I checked several other posts that had the same problem, they were still broken (e.g. https://herbidacious.calamus.graphics/2018/09/02/white-willow-gentian/ and https://herbidacious.calamus.graphics/2018/08/28/the-abyssinian-gladiolus/)

So I again switched to 2019, and could see that these two were still failing to display related posts.

In other words, it looks like the lily-turf-liriope-muscari-big-blue was an edge case that somehow fixed itself, but the deeper issue remains.

What can I try next?

I’ve checked (flushed caches etc) and they are still not showing on the posts in question. (please look at the “page I need help with” as an example)

Any other ideas?

• This reply was modified 5 years, 7 months ago by Keirwatson.

Thanks, I have found a solution but it doesn’t shed any light on what went wrong. I created a fresh page and copy/pasted the content over. The copy of the page is now set as my home page and is working flawlessly – no server spikes – so I don’t know why the old one was causing problems. (I still have the dodgy page if you want an export of it).

In case it is helpful to you:

I was using Gutenberg 1.4.0;

I also had Atomic blocks active, and in an earlier draft of the page in question had both Atomic and Kadence blocks content active on the same page and working happily. However there are two reasons that I don’t think it was Atomic blocks because:

(1) When the problem started I think I had deleted the atomic blocks content so there should have been no scripts activated by the page – although Atomic blocks was still active within Gutenberg.

(2) To try and troubleshoot I deactivated both Atomic blocks and Kadence (along with several other plugins), at which point the stopped causing problems. Reactivating just the Kadence row block (which was the main one I was using) started up the problems again (Atomic blocks remained inactive). I intend to try reactivating Atomic blocks and inserting some content on the page to see if the same problem occurs – if it does I will let you know.

In case it is relevant: the problem initially showed up when trying to view an autosave of the page (because Gutenberg saves so often I had 42 autosaves!). To begin with, the error only showed up when trying to view the autosave, but after a couple of times of getting my server permissions reset just attempting to edit the page did it. I thought there might be a problem in the autosave file becoming corrupted, so I deleted all of my autosaves but the problem still persisted.

– – –

Custom CSS in use:

.image-shadow img {
box-shadow: 0 3px 10px rgba(0, 0, 0, 0.4);
}
.fetched {
box-shadow: 0 3px 10px rgba(0, 0, 0, 0.4);
border-radius: 1%;
border: 1px solid #333333;;
}
.feedzy-rss .rss_item {
border-bottom: none;
}
body a {
text-decoration: none !important;
}