skygazer

Update… it seems to be working again :confused: perhaps it there was a delay in the email notifications and I incorrectly assumed it was not not working… so for now it looks like there actually isn’t any issue but I will update if needed after observing for another day or so.

I also have one instance of this error, would also like to know why and how to fix it.

Hi msytsma, just to let you know, we found out the likely cause of the issue but I didn’t get around to actually fixing it yet because in my situation it involves a fair bit of work because I cannot update my theme (due to discontinued support from the theme creator, it is a custom theme). And so unfortunately I am stuck having to do it manually for now. The issue is that I cannot update my WP to the latest because it creates issues with my page layout, as a result since I am not able to upgrade to the latest WP I therefore cannot update to the latest Jetpack either. Mine was working until one of the Jetpack updates and then after I did the update it stopped publicizing. So there seems to be compatibility with my version of WP and Jetpack. Some features still work, but the publicize stopped unfortunately for me.

Hi hernanct,

I have not actually fixed the issue. The issue is likely a version compatibility issue but I am unable to fix the issue at the moment as I would have to update several things and I just haven’t had the time.

That may also be the problem you are having.

Hi beuchertengineer, you know I was looking at the error and was thinking of doing the same thing. I’m glad to see someone else had that idea. I don’t know for sure if it will work for me too but I will give it a try and I’ll update when here when I can.

EDIT: Did you simply uncheck the compression option and that’s it or do you have to resubmit the sitemap after you unchecked compression?

EDIT2: I went ahead and resubmitted the sitemap and the sitemap errors are no longer present..not sure if that means they are actually gone or if they may reappear again later but for now it looks to be good, we will see in a few days I guess. There is just one separate compressed one still showing for sitemap_attachement.xml.gz but after a few days pass I will delete that one (in case it is still using it and since I just resubmitted the main sitemap).

• This reply was modified 6 years, 7 months ago by skygazer.
• This reply was modified 6 years, 7 months ago by skygazer.

Contact has been received. thanks.

Thanks for replying. Just wanted to update.. Indeed it is NOT related to this plugin. It is a version compatibility issue. I’m presently dealing with JetPack support. Thanks kindly for replying and for offering suggestions though. I appreciate that.

Hi Tracy, I noticed this is marked resolved but I still have not gotten any reply since I did as you suggested and emailed the issue directly for support a few days ago.

I have likely found the problem but need to talk to someone about a possible solution via email. Can you please have someone contact me.

Thanks.

Hi, thanks very much for the reply. Sorry wasn’t able to reply sooner but was trying to investigate the issue further. I think you are right, it likely has nothing to do with your plugin. I even took your suggestion and activated the social meta (which shouldn’t have had anything to do with anything because I didn’t ave it active before and the JetPack publicize was still working).

And to clarify when I said it stopped working I meant it stopped sharing my published post to facebook and twitter (had to resort to manually sharing them) even with the social meta activated it still refused to work and there were no errors.

So finally after days of trying and testing etc I noticed that the last Jetpack update was likely the issue because it is slightly ahead of my version of WP in terms of compatibility and at present I cannot update WP to a newer version b/c my theme won’t allow it so basically I’m screwed till I find another suitable theme as my theme developer/creator is a deadbeat and no longer someone I deal with.

For now I am thinking of going back to the version of Jetpack just before the last update (but I’m not sure this is possible or if it will cause more problems)

And of course my other solution is finding a standalone social sharing plugin and disable the JetaPack publicize feature.

Anyway I just wanted to explain the details as to why I had to ask here because there were several plugin updates around the same time so I was uncertain if this plugin might have been one of them that created the issue but it was not the offender.

Thanks again for replying and for your suggestions in trying to help, I appreciate it.

OK will do.

Edit: I’ve sent an email with a link to this thread.

Thanks.

• This reply was modified 6 years, 8 months ago by skygazer.

Hello.

Yes, as well as disconnecting and reconnecting the FB and Twitter shares on my admin area, I also did the remove app association step (and re associated it) on FB and still no change. I even tried deactivating and reactivating the Jetpack plugin none of these actions made any change.

I also checked using example.com/xmlrpc AND exmaple.com/xmlrpc.php/?for=jetpack
*(example.com URL being my actual URL of course)

.. both returned “XML-RPC server accepts POST requests only.”
which from what I understand is what it should return, so those check out OK thus eliminating any plugin conflict as the issue I would think. And I think this also eliminates server security settings as the cause (again, I think). Besides I hadn’t changed anything just before the shares stopped working.

The only thing were done were plugin updates and one unusual scenario where I had to turn off my server to reset my root PW. This is not a normal action but I had changed my pw and forgot to write it down so had to reset it. I’m not even sure if this has anything to do with this issue but just mentioning it because aside from the plugin updates there weren’t any other changes made that I can think of.

I’m running Apache 2.4 on the server end with cURL installed and working (always has been and still is). I don’t know if that is helpful in any way but thought I would mention it in case it is.

If you don’t mind, please look at my profile for the info. you requested.

Thanks for your help so far.

EDIT: I was just looking at the sharing settings again for the two shares I use and I saw the

“Connection available to all administrators, editors, and authors”

box… it is unchecked. I don’t recall ever changing this and I’m the only admin and user account on the WP admin so not sure if this has anything to do with the issue or not. If I’m the only admin do I still need to check these boxes?

EDIT2: Sorry for the edits, but I was wondering if the Data synchronization function would probably help here, was just thinking maybe if it did have anything to do with the fact I had to turn off my server and restart it. But then my stats are working fine so I dunno.. Do you think I should the Jetpack Data synchronization?

• This reply was modified 6 years, 8 months ago by skygazer.
• This reply was modified 6 years, 8 months ago by skygazer.
• This reply was modified 6 years, 8 months ago by skygazer.

DONE ??

Thanks again.

Hi. I executed the 2.4.6.1 update and checked my last few visitors on the WordFence live log and it looks like all is good again, I’m seeing no weird URL append and no “not found” error either so that part looks good AND Google analytics is also good to go and is showing visitors again.

Thanks so much for you dedication and effort. I’m sure you can imagine how much it means to have these things resolved quickly and properly. YOu are awesome for taking care of it in such a timely manner.

Many thanks, I’m happy again ??

Ok thanks for the update and looking forward to a resolution. Appreciate very much you updating me..thanks.

see profile