naithin
Forum Replies Created
-
Your comment landed fine, Bob, that isn’t the issue though — it’s with our own comments as site admins.
DBMcNicol: JetPack w/ Chrome on Windows here.
Edge works fine. Firefox is also OK now.I had left it marked as resolved as it seemed that getting it logged into other tickets was the best outcome I could expect, but just to clarify — the issue still exists to this day, and as others have since commented — it’s occurring for others, too.
Hoping there might’ve been some updates even if just in the understanding of why this is happening and an estimated ETA to resolve.
Hi Tracy,
I don’t have access to a Mac, apologies, and it seems that Safari for Windows support ended 2018 when I look it up.
I think I noted it already, but it seemed to work in Edge which is somewhat strange as that does use the Chromium renderer too. But entirely possible Edge and Chrome are still handling cookies quite differently over the top of that I suppose.
Hi Karen,
Thanks for the link and follow-up. Just to note though; that it seems from the commentary and response to other examples this is an issue specific to use of HTTP. Time to Loot runs a current valid SSL cert and forces redirect to HTTPS, so there won’t be any usage of HTTP here unless Jetpack itself is doing something strange here.
As an additional piece of info to the below — this issue with Chrome exists across multiple PCs, too.
Hi Stef (And Mominny!),
Apologies for the delay in response — I did some further checking and found my current account works just fine if I use a different browser. (Odd thing is, I could’ve sworn I did precisely that test when this started and still had the issue! Anywho…)
So it would appear that it isn’t the JetPack <–> WordPress connection or even the account necessarily, but I’m still a bit puzzled how it’s happening.
I’m using Chrome for what it’s worth but was able to successfully comment if I logged in via Edge or Firefox.
Forum: Fixing WordPress
In reply to: Inbound Pingbacks Not WorkingThanks for your response bcworks!
I don’t know whether the Siteground crew fixed something silently in the background after all, or whether somehow my theme *was* blocking them, but I successfully received a pingback yesterday after changing my theme. (Was Genesis Framework + Magazine Pro, now OceanWP)
I still struggle to see how it might’ve been the theme, as the pingback ‘comment’ itself was not being generated fullstop, it wasn’t just a display issue.
Even so, out of curiosity about whether I might be able to use this script to ‘repair’ some of the missed pingbacks in the past, I took it for a spin.
No error codes were generated, but neither was the pingback. Should I expect it to? The target post still has comments open, the source post is definitely doing a direct link to the post rather than via reader, short link or anything else.
Although possibly I’m making an assumption I shouldn’t — FaultCode is returning 0 as an integer. I assume that means no error, but that might be wrong. FaultString is returning an empty string.
Forum: Fixing WordPress
In reply to: WordPress Admin Menu ProblemHi Alex,
At the very bottom of your menu/icons, will be an arrow in a circle icon. Click that to expand it out again.