Andrew Arthur Dawson

@macmanx I went to that link and it tells me to login. I login and select my picture to continue and it brings me right back to the page that says to login. I tried it on safari and chrome to no success. I’m not exactly sure why I’m supposed to be doing over at that link but it’s not working to log in and process?

James Huff (@macmanx) James, I absolutely do not have anything set for auto update. Is there a switch in Jetpack that I’m supposed to make sure of this? As for GoDaddy, they have auto update on for WordPress updates I believe but the six plugins I have I most hit the update button myself, so any help tracking down the source of what is triggering this message would be great! ??

@fresatomica I spoke with my host provider at length. They said that they do not allow the wp_update_plugins to be touched because they control the updates for all WP cure files. GoDaddy Managed WordPress handles all WordPress updates, changes to core files, database, etc. the only thing I’m responsible for is updating plugins I download. They told me the wp_update _plugins is not the one I control. So, going back to my original question then, is that true. Is wp_uodat_plugin where core files are updated? If that’s the case then I guess this scheduled event can’t be fixed? I also really would like to know from the Jetpack team why this is even being checked in their site health check and what’s the specific purpose of this specific scheduled event in regards to that file itself?

Ok, I spent hours of testing on this tonight and got to the root of where specifically the error is with the WordPress 2016 theme. It comes down to this:

1. The blog posting in text must be some around around at least 493 characters (with spaces) long.
2. The blog posting cannot use italicized to count for those characters.

When either of those conditions were false, the reader will default to the text I have on the right of my main page that is my intro to my blog text block.

On my Thought For The Day category, they were mostly long enough, but were 100 percent in italicized. And as soon as I removed the italicized the reader worked fine.

On my Question TO Ponder For The Day category, I needed to pad characters to each of them to get over a certain character length, so I added “The Twelfth Step -” a number of times until I reached the threshold where it would appear in the reader correctly.

These are errors in the Theme itself and this is the only workaround I could find. It would be great if the WordPress team could fix this so I don’t have to pad my short blog entries with text and avoid using italicized…

Ultimately, there are many circumstances where the reader view just doesn’t work right and does not display the articles on the main page that I’m displaying. I look forward to any help I get on this.

Ok thank you. I’ll keep an eye on it. I wish I understood those debug warning messages better but you are probably right that if it happens rarely it’s not worth being concerned about. I have been trying to chase down another issue of my site having resource timeouts and that’s why I’ve had this debug log on. And any message that has appeared I’ve wondered if it could be related. At least in this case I know it’s not. I only wish I knew what triggered it because it’s the first message that’s appeared that I haven’t been able to figure out that.

I have tried a number of searches, but none have caused the error again thus far. Any suggestions of search strings to try that might trigger this? I was just putting in random stuff from symbols to letters to numbers to various combinations. Always got back either no results or a result or two. I have a pretty basic site and very limited plugins and have no other ideas of what else could cause this to suddenly show up once. If you have any suggestions of specific combinations of things to try to search for that could cause this please let me know or any other ideas either? As I mentioned, I’m a pretty basic user with very little WordPress understanding other than now to point and click really.

@kokkieh ok thank you. I will open another thread again after this last comment here. I’m glad to know that information. I didn’t open a thread for each failed update because I didn’t want to keep getting the response it was my server company’s fault and to them go through the same dance where they blame you guys and vice versa. Regardless, I’m glad to know you are keeping track of this because it is an issue and hopefully Jetpack will fix the plugin’s update so that it isn’t causing timeouts on any server.

@kokkieh I will definitely do that as soon as I encounter it again. I have not updated since going up 7.0 because every update was failing with a time out issue and it took me hours getting it back to normal.

I thought it was Jetpack related, I had an opened thread, but then I was told it was server related. I spent hours with my hosting company with this. They spent hours checking server logs and I spent hours checking debug logs. My account was cross checked to others. My server was cross checked to others. And nothing was found. I was told by my hosting company it is definitely related to the size of Jetpack’s plugin.

I have been following the support forum for this issue and have noticed the same error happening on updates being reported by multiple users now and Jetpack keeps saying the same thing that it’s a shared server timeout issue as a response.

Then I just saw two days ago a person who is running on a fast server, not shared, and got the same issue. And I am hoping you guys might look into maybe compacting the size of each update in the future? Handling it differently maybe? And in the meantime have an opened thread like this, one thread, that people can comment on if they are getting this issue? Does that make sense?

So, is there any way you could leave this thread opened please? And not delete my comments so we can see if others have similar issues and maybe we can see if there are any commonalities because I’m still trying to debug my own and I can’t do that if I can’t connect with other Jetpack users to see what is different with my setup, if anything?

Please respond here to this and advise when you can. I hope you can agree. Thanks!

@dpiguyana I’m just curious when your issue started. I have been reading the forums myself lately and have seen a number of others have this issue and I personally have been dealing with it since version 6.8.1. I’m just trying to see if there are commonalities in the setup of who’s reporting this update. What kind of server are you on, is it shared, Cpanel, etc? Do you have a huge site with lots of plugins or a small site? There’s been at least a dozen people who have begun experiencing failed Jetpack updates and Jetpack has been saying it’s due to resource issues on shared hosting servers. Yet, I’ve seen a report now of someone who’s on a fast server that hasn’t has this issue. But regardless, even if it is all related to a shared server, I’m thinking that at some point, if a lot more and more people on shared servers begin having issues, that it might be something they find a way to fix to make the update a lot easier and quicker? Anyway, I do love Jetpack and swear by it, but still would like to see if there are any connections on all of us having this issue, so any details would be greatly appreciated.

@jeherve hey, Jeremy, sent you a few emails with some errors in my WordPress debug log and wanted to know what your thoughts were on whether they could be related to my timeout issues. Are you still around and getting my emails? Usually you respond within a day? I also reported a separate bug that isn’t related to my site and is a Jetpack issue but have not seen a response from it either. Hopefully I’ll hear back from you on both soon?

@pradeep89 hey there, honestly, I did one thing. I removed a link on my site that for the life of me I can’t remember now what it was but after I did that and went into google testing tools and recrawled my site and it was working again. So sadly I don’t have an answer other than that.

@jeherve Thank you so much! I will wait to do anything but I was thinking it might be best now to communicate the rest of this by my email I’ve used to contact Jetpack support before, since it’s now out of the scope of this support forum. You agree?

@jeherve Thank you so Much in advance for that call. I absolutely agree it’s my server and a Godaddy issue. As you already see, I have a very simplistic set up and shouldn’t be running into these issues but unfortunately I am on one of their original Managed WordPress servers and keep telling them the problems of memory on it and they keep saying it’s fine and blaming Jetpack. They should move me over to a newer server for free to see if that fixes my resource issue but they keep telling me there is no issue and to contact Jetpack. I would love to remain with them only because I do like their customer service and because I have another personal website with them. Hopefully you make some serious progress with them. I was going to call today to talk to them bit I will hold off until I hear back from you. Maybe you can work with them to figure out why this server keeps timing out on me anytime I do anything with Jetpack… if you need me to give them any sort of permission to have you talk to them Just let me know. thanks again in advance Jeremy and I look forward to hearing back from you.

Thank you for responding @jeherve . While I will try calling GoDaddy and tell them this, I don’t have much faith in getting anywhere as the last time I spoke about this they ran some server tests supposedly on their end and said things were fine. Then they told me my only option was to upgrade to cpanel if I wanted more dedicated resources.

Honestly, for as much as I love Jetpack’s abilities it’s so frustrating with its size as in the last three years of continuing to do this blog that was simply meant to be a cheap digital life diary for myself, EVERY single issue but one with needing to upgrade my PHP to the latest has been 100 percent related to Jetpack’s size and resources needed by it to function. No other plugin has given me any other issues…ever. And using a WordPress theme and removing any potential plugins that weren’t necessary has proven it’s really just Jetpack and being on a shared server with Godaddy.

So trying to convince godaddy to move me to another server will most likely lead to what they said the last time and the time before that and the one before that as well, that it’s Jetpack and that Jetpack needs to fix their resource demands.

Thus I’m probably left with the options of (a) quitting blogging altogether, (b) paying $300 for them to move my blog to a cpanel starter setup and an additional $150 a year for it on top of what I’m already paying, (c) pay a WordPress knowledgeable person to find me a server to move me too on another company that would be far better of which I would have no idea where to even start with, or (d) delete and reinstall Jetpack every time a new release comes out.

I guess you can see why now I am so frustrated about this…