Custom plugin support broken in v7.6?



  • I have just updated to v7.6, but I have run into one minor issue, and one big problem:

    1. During installtion I did select the Plugins Admin, but I couldn’t find it in the Plugins menu. I guess this is because I previously never installed the Auto Updater, and apparently Plugins Admin requires it. However, if it was previously not installed, and the Plugins Admin is selected, then the Auto Updater is greyed out but not selected. Anyway, I fixed this by running the installer again, unselecting Plugins Admin, selecting Auto Updater, and then selecting Plugins Admin again. A minor issue, but I thought I’d report it anyway.

    2. I discovered that my custom auto-indent plug-in was missing from the Plugins menu, although the standard plug-ins are there. Inspecting the Notepad++ program files directory I found my custom plugin DLL still there, but apparently the standard plug-ins have been moved to user space. Of course I moved my DLL there as well, but this didn’t seem to help. This is a big problem (well, not global warming big, but you know what I mean).

    I guess I could (should?) try to get my plug-in added to the new plug-in list on GitHub, and I might look into that. Do note that this is a plug-in that I posted here way back when I wrote it, but there was zero interest in it. This is fine of course, but it does means that I’m not exactly motivated to invest too much time in sharing it now.

    So, is the Plugins Admin a breaking change? I hope not, but if so, then IMHO v7.9 should come with big red warning signs. Meanwhile I have rolled back to v7.5.9, and I have informed my colleagues to not update until further notice.

    BTW, is it really necessary to store DLLs in user space? IMHO this is bad practice, and should be avoided at (almost) all costs. I would urge you to reconsider this, especially if the Plugins Admin feature is not installed (because then there is no reaon to do this, right?).



  • Hi,

    Your plugin should be working, just make sure to put the DLL in the new destination (user space as you call it) BUT under its own folder, IOW:
    %USER_SPACE_PLUGINS_FOLDER%\%YOUR_PLUGIN_NAME%\%YOUR_PLUGIN_NAME%.dll.

    I would urge you to reconsider this, especially if the Plugins Admin feature is not installed (because then there is no reaon to do this, right?).

    Just a note here - To avoid further confusion the same folder for plugins should be used regardless of Plugin Admin feature presence.

    BR



  • @Theo-Niessink Are you missing https://sourceforge.net/projects/npp-plugins/files/NppAutoIndent/NppAutoIndent Plugin v1.2/NppAutoIndent_1_2_dll.zip/ in the list? Currently just the plugins are added to the x86 plugin list which are also available as 64bit plugin. Transformation of the plugin list from plugin manager to pluginAdmin is still outstanding for the plugins which are just available for the 32bit version of N++.
    Additionally the plugin zips need to be in the correct format, which seems to be the case for NppAutoIndent.



  • @pnedev said:

    Your plugin should be working, just make sure to put the DLL in the new destination (user space as you call it) BUT under its own folder, IOW:
    %USER_SPACE_PLUGINS_FOLDER%\%YOUR_PLUGIN_NAME%\%YOUR_PLUGIN_NAME%.dll.

    Cheers thanks a lot, that worked!

    Just a note here - To avoid further confusion the same folder for plugins should be used regardless of Plugin Admin feature presence.

    So old plug-in support is indeed not broken, except you might need to move some files around manually, but only if you use oldskool plug-ins of course. Fair enough I guess.

    @chcg said:

    @Theo-Niessink Are you missing https://sourceforge.net/projects/npp-plugins/files/NppAutoIndent/NppAutoIndent Plugin v1.2/NppAutoIndent_1_2_dll.zip/ in the list?

    No, like I said, it is a custom coded plug-in (MartinicAutoIndent), which I never bothered to share because there was zero interest in it (back in 2013). But thanks anyway.


Log in to reply