@Craig-Harbison said in Notepad++ v8.8.2 Release: I have both 8.8.2 and 8.8.3 versions. they both work fine on my Win10 laptop but neither will read or let me edit my json files on my new Win11 laptop. Really sucks. I can read and edit JSON just fine with both those versions. I doubt it’s a regression, but we can help you investigate what’s going wrong for you if you start a new Topic to discuss it. If it does end up finding a problem with Notepad++, we can then direct you to the right location to inform the developer. If you really want help figuring out your problem, please go to the Help Wanted category, click New Topic, and write a detailed post: list your exact steps for how you are trying to read or edit JSON (ie, how you are opening the files, where the files are located, whether on your local drive, a USB drive, a network drive, etc) and what messages or circumstances indicate to you that the JSON file is not being read or edited? Please also go to your ? menu on the right of the Notepad++ menu bar, and click Debug Info, and Copy debug info to clipboard, and paste that in your new topic.

@donho , worked without a hitch or a hiccup. No problems with the update on my Standard Install version.

@datatraveller1 Awesome. You are the best!

Just to mention, for people using Intune to deploy notepad++. if you activate the “managed installers” option, any apps not signed wil lbe signed with a valid certificate and therefore users don’t have popup for the “unknown publisher”. I think you can do the same with SCCM. Will not help regular users, but jsut in case.

Ref to Npp website spelling error

@donho said in Notepad++ v8.8 Release: @Neymar44 The bug has been fixed in v8.8.1. Here is v8.8.1 RC: https://community.notepad-plus-plus.org/topic/26833/notepad-v8-8-1-release-candidate The glitch indeed disappeared in the last 8.8.1 RC, thank you !

Another regression has been found here: https://community.notepad-plus-plus.org/topic/26815/notepad-v8-8-release/4?_=1746291034345 The regression has been fixed in the new binaries: http://download.notepad-plus-plus.org/repository/8.x/8.8.1.RC2/

@schnurlos https://notepad-plus-plus.org/news/v88-we-are-with-ukraine/ gives an Error 404 (link within “F1” Info). It’s because v8.8 is still in RC state. It will be on line in few hours.

2 off-topic posts are moved to: https://community.notepad-plus-plus.org/topic/26793/all-the-off-topic-go-here

@mkupper Thanks, those 2 links provide reasonable “guess-timates” re: what to expect in the next release. Murray

@donho , That fixed that issue, thanks.

The unrelated post has been moved to 22917 of Boycott Notepad++.

Possible v8.7.8 regression: GitHub issue #16250 .

@xomx , Understood. I wouldn’t want to rush stability, but I agree with your assessment that it’s a straight forward fix that I don’t think would affect anything else but what’s intended, but I can wait if need be. Thanks again for the help with unraveling this while I was trying to find out the actual issue at the heart of the problem.

@Mark-Olson Fixed. Thank you!

@Kaptain-Biwouak , It is up to each plugin’s author/maintainer to determine whether or not their plugin is affected. Don, as the owner of Notepad++ but not of the plugins that are written for Notepad++, doesn’t have the bandwidth to review the source code of every plugin that exists for Notepad++ to determine whether or not it would be affected, hence he made this announcement to let the plugin authors know that they each need to check their own plugins. addendum: and if users want to find out if any of the plugins they use are affected, they can just try the plugin(s) in v8.7.6, because what happened was that it was found that efficiency-improvements in v8.7.6 unintentionally broke some plugins by disabling some events; the changes that will be in v8.7.7 will allow plugins to use the API to ask Notepad++ to re-enable the mentioned events on a per-request basis. So, if you are successfully using a plugin in v8.7.6, you can continue using it in v8.7.7. If you find that a plugin worked in v8.7.5 but broke in v8.7.6, then you could check the homepage for that plugin and see whether or not they’ve mentioned a fix or released a new version in the last week or so, and if not, then ask them if they will have a fixed version ready in time for v8.7.7.