Take responsibility of the bug

Harsh words. Perhaps you could phrase this a little less demanding and aggressive?
Let’s not forget, this is free software without any warranty and provided as is.

Just downgrade/rollback using WP CLI https://www.ads-software.com/support/topic/version-3-6-5-json-headers-issue-broke-site/#post-17785813

note: I’m not the plugin author … just trying to help you. I’ll be adding to the thread I referenced with other possible ways to fix…

@pixolin I have spent enough time first today debugging and the fixing customers sites which costs money even the plugin is free hence the strong wording. Do note that this bug has affected so many sites with auto updates and at the time of posting this the author of the plugin has not responded to a single thread here for users with issues. It has nothing to whether the plugin is free or not. Standard practice is to acknowledge the issue and provide revised version with version bump so that people can update the plugin from their own admin or managed services. Currently you have to manually overwrite every instance where plugin is installed.

@jrevillini I am just asking for other users since I got my customers sites back already. Thanks for the tip since it could help others too.

• This reply was modified 4 months, 3 weeks ago by sirrahikkala.

@jrevillini Thank you for a constructive proposal to deal with this issue.
However, I think you don’t even need to downgrade. Following seems to work out of the box:

wp plugin update code-snippets --version=3.6.5

wp-cli update helps the people with one or couple sites but imagine doing that to dozens of different sites one by one instead of pushing new version from repository.

• This reply was modified 4 months, 3 weeks ago by sirrahikkala.

@sirrahikkala Every bug is frustrating for any user who has to deal with them. Let’s assume good faith and not unethical bevahiour that Shea Bunge altered the file without creating a new plugin version (and all SVN hussle needed to update). Also, the lack of response may simply be due to the fact that the developer is asleep. He lives in Australia. Time zones can be tricky.

What we know now:

• The plugin was fixed and version was not bumped
• The first post of the issue was 13 hours ago from this moment which was before afternoon Australia
• There was not a single forum post to even do in-place update

So lets leave it to that because everything else is just speculation. Have a nice day.

Hi @sirrahikkala,

My apologies for the issues this has caused you. The issue you mentioned was not a bug in the plugins code, but instead an issue that accidentally occurred during deployment. I had thought that the impact was minimal, and that by re-deploying a correct version of this file the majority of users would be unaffected, but clearly the original file was pushed out far further than I had realised.

Not asleep yet, just had a busy day and wasn’t able to make it to my computer to see this and provide a proper update. I’ve pushed out a proper version bump that should make it easier for everyone to update. Once again, I can only apologise, and promise to handle this sort of thing better if it should occur in the future.

Thank you for your response and explanation.

Things happen, it’s unfortunate, but sometimes they do.

Thanks for all you do @bungeshea !