<![CDATA[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?

]]>https://community.notepad-plus-plus.org/topic/27646/testing-npppluginlist-for-new-updated-pluginRSS for NodeTue, 01 Sep 2026 00:06:08 GMTMon, 31 Aug 2026 20:50:55 GMT60