Testing nppPluginList for new/updated plugin
-
In the old days (ie, the last time I did an update to a plugin last December), I was able to follow the plugin list instructions to verify that a plugin would work with the nppPluginList before submitting to that repo. Specifically: download a recent DEBUG build, run that in a portable where plugins\Config\nppPluginList.json is the updated JSON with the hash for my new/updated plugin, run the DEBUG executable, install using plugin list.
But when I tried with a v8.9.8 DEBUG build, when I would pick either my new/updated plugin, or pick an existing plugin (one that works just find to install through the DLL version), it just exits the portable, but never initiates the download nor restarts the portable Notepad++ DEBUG executable.
I know this used to work right. I double-checked the SHA256 – both from GitHub release attachment display, and as calculated identically by Tools > SHA-256 > Generate from file – matches what I put in the JSON. I double-checked to make sure nothing in my portable directory has the Mark of the Web. So I cannot figure out anything I am doing wrong.
Did one of the security updates, where it’s checking more things under the hood, break the plugin-list JSON testing procedure?
Has anyone else tried the Plugins Admin verification procedure recently (@Coises, for example, with Columns++ 1.3.3 or @rdipardo with PreviewHTML 1.4.6)? If so, did it work for you? Or did you have to do something special to get the test to work? Or are you just so experienced that you stopped trying to test the nppPluginList.JSON before submitting?
-
Has anyone else tried the Plugins Admin verification procedure recently
Yes, but I’ve been using the same copies of Notepad++ for a long time now: portable 8.7, x86 and x64. By now I’ve forgotten how I got them, but I’m pretty sure I didn’t build them, I got them from a link someone here (possibly you) gave me.
I do check every time, because about one time in five I seem compelled to make a silly error.
-
@Coises .
I’ve forgotten how I got them, but I’m pretty sure I didn’t build them, I got them from a link someone here (possibly you) gave me.
It’s easy to get the debug builds for recent builds – the user manual link explains how – but for older versions, the GitHub artifacts expire.
I guess to find which version caused the procedure to stop working, I will have to do a search through versions from December until now, and figured out the last version that worked by following the procedure. Once I know that, I can file a bug (or ask if there’s an intended update to that procedure)… I guess I am building a lot of debug versions of N++ today. ;-)
I’ve been using the same copies of Notepad++ for a long time now: portable 8.7
I guess I know I don’t have to search back any farther than that, anyway. :-) (Actually, since I know it was working in Dec 2025, I shouldn’t need to go back before v8.8.8, hopefully.)
-
[W]hen I tried with a v8.9.8 DEBUG build, when I would pick either my new/updated plugin, or pick an existing plugin (one that works just find to install through the DLL version), it just exits the portable, but never initiates the download nor restarts the portable Notepad++ DEBUG executable.
I have also noticed what you describe, and I assumed the cause was whatever security hardening they did to WinGUP (or the cURL library it depends on) after the server takeover incident last year.
I built my own debug copy of
GUP.exeand had no issue following the user manual’s instructions.I guess to find which version caused the procedure to stop working,
Starting with the first post-incident release would be sensible.
-
I built my own debug copy of GUP.exe and had no issue following the user manual’s instructions.
With that idea, I took the released gup.exe and libcurl.dll from 8.7 portable, and put it in my debug copy of 8.9.8 portable, and the pluginsAdmin debug procedure worked. So it’s definitely on the GUP end of things. So that’s the right path to go down for finding the culprit.
Thanks.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login