Andrew Arthur Dawson

@jayceezay are you using Godaddy and how do you access SFTP? I am really not a knowledgeable user and simply know how to login into my wp-admin and point and click stuff. Would you be able to provide really simple steps for me on how to do this?

@jeherve and I agree that maybe this wasn’t entirely attributable to resources if multiple users are dealing with this? That’s wjy I’m trying to figure out what hosting platforms people are using. If not everyone is GoDaddy in their Managed WordPress environment then maybe Jetpack is creating an issue now with its size and own server?

@bobbydurrettdba just curious Bobby, did you say you are on GoDaddy or some other hosting environment? When you deleted all of Jetpack, and reinstalled, did you do that behind the scenes or through the dashboard? And didn’t that delete all your settings and email subscribers and such?

I should also mention that when I did get GoDafdy to delete Jetpack entirely in last nights three hour process to get my site back up and running, I was unable to download even from the plugin page. So, I don’t know whether this is because of Jetpack being too big now of a plugin for GoDaddy or whether resources last night were a problem between the two servers of mine with them and yours. Regardless, there are many people who use Managed WordPress and Jetpack who aren’t going to be able to go behind the scenes and muck with it to get it to work. Did you guys even test this in the Managed WordPress platform that you have? Can something be done to fix this on your end with them to make this a smooth transition so that less educated WordPress users like me can just point and click like I do with all my other plugin updates? Honestly @jeherve I have never had any issue with an update having a time out EVER except for Jetpack and that started back I think at Jetpack 5.0 or 6.0. Nevertheless, unless you guys can wrk with GoDaddy, I and other Managed WordPress users wont be able to use Hetpacl anymore as it grows in size and creates even more limitations.

I only use Jetpack for metadata and email subscribers and that’s it. It would be great to have a smaller plugin availability to do the limited stuff I need. But I’m sure that is not possible. So, basically, I don’t know what to do and I can’t afford to move my blog to another server nor have the understanding to do it only own.

I pray that Jetpack and GoDaddy can figure out this resource issue and help me and others to love beyond this problem.

So here is my issue @jeherve.

A. GoDaddy won’t help me with this because they only guarantee my site is up and running and I’m on my own to fix any plugin issues.
B. Jetpack is the only plugin I get issues with ever with resource issues where it timed out.
C. I have no idea how to do a FTP or Cpanel or access those behind the scenes issues.

Last night I spent 3 hours getting my site back up and running because of trying to update this plugin. It literally killed my site. I don’t understand why Jetpack is the only plugin I ever get this issue with. And I’m curious as to if the people that had this issue also use GoDaddy or is it quite possible that it’s your server that really is the timing out issue here. Regardless, I fear I’m dead in the water with ever updating Jetpack again now because I’m not able to just point and click the update button without it timing out. And given Godaddy does not fix stuff like this nor shows me how to do anything I really don’t know what to do except stay on Jetpack 6.8.1 permanently, which at someone y I assume will no longer work when software changes.

At this point I could use some really guidance here for a user who doesn’t really know how to do any WordPress stuff other than point and click. ?? (Oh and the theme issue was corrected with no issues once I was on PHP 7.2.) also, doesn’t deleting Jetpack as you suggest above delete all your settings in Jetpack, your email subscribers, etc? Meaning I’d have to start over with Jetpack?

• This reply was modified 6 years, 1 month ago by Andrew Arthur Dawson.
• This reply was modified 6 years, 1 month ago by Andrew Arthur Dawson.

Mine also failed. I’m on GoDaddy Shared. I am running PHP 7.2 and I’ve tried it both on WordPress 5.0.2 and 5.0.3. Now I cannot get to my dashboard (wp-admin) and am having to work with GoDaddy to restore my account to get back in and work on my site without updating to 6.9. Are any of you on GoDaddy Shared? Or are you all on some other server setup? And by the way, when I tried to update it, it basically just left my account in a “maintenance mode”. Eventually, it removed the plugin altogether because of some fatal error. And when I attempted to download Jetpack from the plugins again and install it, it just hosed my site up all over again.

• This reply was modified 6 years, 2 months ago by Andrew Arthur Dawson.

Update #2 – I tried posting a comment on anothe thread and for a response from a volunteer who said GoDaddy must have changed something else. But I verified the only thing changed was 7.1 to 7.2. And once changed, the update all WordPress themes latest versions including my active one, Twenty Sixteen, worked. At 7.1, they all failed with permission issues. The only thing I can think of is that it’s a combination of the shared server configuration and the PHP combination?

Update: I updated to PHP 7.2 from 7.1 and the theme update worked! Does the new updates require PHP 7.2? IF so, why didn’t WordPress tell its users to make sure to always run the latest PHP? I just find it strange that updating to PHP 7.2 made the update work successfully but on 7.1 it gave me all sorts of conflict errors with permissions? Hopefully someone will respond to this from the WordPress gurus…

• This reply was modified 6 years, 2 months ago by Andrew Arthur Dawson.

Being a free user of Jetpack I always wonder what could be thrown in at any given time. Advertising is a deal breaker and something o could never tolerate or accept with the seriousness of my blog subject material. I hope for Jetpack’s sake, they learned a lesson today from all this with their loyal users…

I have indeed verified this has now been fixed. I just created a quick blog to apologize to my subscribers and reassure them. The email did NOT have the advertisements in them. And yes I agree with @androweb as I’m always fearful what Jetpack could throw in without letting us know that could totally change things for me. Running a 12 Step addiction blog, I have a very sensitive readership and my only hope is that it hasn’t been jeopardized by this ad thing that happened with last night’s posting. Thankfully, they have fixed it and I pray it remains that way…

There wasn’t any announcement and yes that was my first reaction too. There are a lot of people who are upset about this and my subscribers are threatening to drop! None of us signed up for a this plugin to show ads we don’t benefit from nor need, that also jeopardize our subscriber base…

I responded over on Github too. Jeremy from Jetpack stated they added this 10 hours ago to all non paying users!!!!!! Are you freaking kidding me. I barely have enough money to even pay for my hosting at GoDaddy and now I have to upgrade to a paid version at Jetpack to see a feature to turn this off? No notifications, no warning, no nothing, just implemented for all of us!!! Now my readers are complaining too and are going to unsubscribe. In light of all the Facebook privacy issues going on, people are skiddish and don’t want to see garbage ads in anything, especially something as simple as an email subscription. I sincerely hope Jetpack will immediately turn this back off and rethink a decision that is going to seriously impact negatively their reputation in the WordPress world.

Come on Jetpack, have some mercy on a poor and currently disabled guy who can’t afford to pay money to turn an unwanted feature off that is scaring what few readers I have away!!!

At least I know it is not something I’m doing. I’m guessing it’s either a mistake on their end, or a new feature they were trying out to see if it bothered subscribers or not. I absolutely so not want this feature as it will drive my subscribers away. My email looks like an advertisement now. And I pray to God they don’t come back and force free subscribers to Jetpack to have to upgrade to turn this advertisement off! I’ve been a loyal Jetpack supporter for five years now and really hope they know this isn’t a good thing at all to put in their subscription emails for anyone, free or paid.

Rogier, thank you for responding so quickly. I am inclined to agree with you. Unfortunately, my site is with GoDaddy and I use a Managed WordPress environment and they occasionally make changes that affect my operation and then don’t own up to it. So, I’m guessing they just recently made a server configuration error that is affecting me, as this just started happening on Saturday. I’ve been using ReallySimpleSSL and have the certificate on my website since about April with no issues. Then suddenly they appear and so, that’s why I’m inclined to believe it’s on GoDaddy’s side. The downside, is that the people I get to talk to usually have no idea what I’m talking about and so, I’m just hoping that someone higher up in their testing will come across this and figure it out and resolve it, because the last time I tried to explain to them an issue that was in their server, I wasted 3 hours of time on the phone and got nowhere and that is generally the ongoing issue I have with them. Regrettably, I can’t afford to put my blog on my own server, because of financial limitations. Nor do I have the wherewithal to move to a new hosting provider, as I’m not very tech savvy. So, I’m stuck with this error it looks like until someone finds a way to communicate to the server developers at GoDaddy…

@jeherve Jeremy, it’s been over a month now with no contact on this error. I have sent an email or two in the past two weeks to the team inquiring on this, because the GitHub error you opened has not even had a person assigned to it. Usually I get a relatively quick response from the Jetpack support email and in this case, I haven’t received any contact or foot traffic on this bug that has been proven. I’m a little frustrated because I have no work around for this. Is there anything you know about when this is going to be assigned or whether it ever will be? Anything on this bug at all?

@jeherve Jeremy, just curious. Is the function that’s part of Jetpack that forms the email that goes out to subscribers actually formulated in the Jetpack software on my end or is it done on your end when I post a blog? I was just curious. And also, is anyone going to take the bug assignment for this because I haven’t seen anyone sign up yet… ??