New Plugins Home (Round 2)



  • How to Install plugins as non administrator user?

    1. Option:
      Install NPP into “%ProgramFilesx86%”. But during install or upgrade of a plugin, there will be displayed an UAC dialog which prompts for an admin accout. Therefore this is not a possible option.

    2. Option:
      Install NPP into “C:\Notepad++” and add “doLocalConf.xml” into this folder. Additionally give write access for the users group for this folder. The users (non administrators) are now able to install or upgrade plugins without an UAC prompt.
      So far so good, but the main problem is, that now the configuration files are also located in “C:\Notepad++” and not in the userprofile anymore.
      This leads to problems on shared computers which are used by different users. They don’t have their own configuration of NPP anymore.

    Is there a different solution which I don’t know for solving this problem?
    The main requirement is: Our users (which are not admins) should be able to install plugins by themselves.



  • @Shamu35-NPP said:

    The main requirement is: Our users (which are not admins) should be able to install plugins by themselves.

    This is critical for us as well.



  • @Shamu35-NPP & @Artem-Sh :

    If it is critical for users to be able to install plugins by themselves, either give them local-administrator privileges, or install in an alternate location: if you use the installer, but put it in (say) c:\usr\apps\Notepad++ instead of c:\program files\notepad++, then they should have the write privileges necessary to install plugins themselves.

    The reason I suggest this workaround, rather than agree that it should be changed: you aren’t the only one with a critical requirement. Others have a security-critical requirement of users not being able to install plugins, which is the exact opposite of your requirement. So, if you have admin privileges locked down, the options are to install into program files to protect notepad++ and prevent user-installed plugins, or install somewhere else with write-privileges to allow user-installed plugins, or to use a portable edition with doLocalConfig.xml to keep everything bundled in one writeable directory (or protected directory, if that’s what you prefer).

    My workplace uses Avecto Defendpoint (and I’m sure there are other similar), which allows locking down certain Admin tasks, but allowing others; so, when I try a UAC action, Avecto Defendpoint checks my privileges, and if I’m allowed to do that local-admin task, it lets me, otherwise it prevents me. Maybe something like that would work to grant partial Admin privileges to your users. I am not an expert on the IT/Admin side of things, so that’s about as much about Avecto Defendpoint as I know.



  • @PeterJones said:

    or install in an alternate location: if you use the installer, but put it in (say) c:\usr\apps\Notepad++ instead of c:\program files\notepad++, then they should have the write privileges necessary to install plugins themselves.

    This doesn’t work! There is still an UAC prompt during installation of a plugin although I give write permissions for this folder. Additionally it needs doLocalConf.xml but this leads to problems on shared computers, because all plugins are installed in the installdir of NPP and not in the userprofile. I explained this already as “2. Option:” in my posting above.

    you aren’t the only one with a critical requirement. >

    Yes of course. But it had worked for years and now it’s broken for my needs and I have not found a solution for this new situation. Currently I’m not able to upgrade NPP to Version =>7.6



  • @Shamu35-NPP ,

    This doesn’t work!

    No need to yell at me. I’m a volunteer, spending my own time to try to help fellow users of Notepad++. I’m trying my best, but since I’m not on your computer, I cannot tell what problems you may or may not have.

    Ignoring the UAC issue right now (that seems like a bug in the installer, to me; it shouldn’t need UAC to install in a non-program-files location, but we can come back to that). When you say "additionally, it needs doLocalConf.xml" when you installed into a non-protected area, what did you mean by that? What didn’t work if you don’t doLocalConf.xml?

    Currently I’m not able to upgrade NPP to Version =>7.6

    So is there a reason you can’t just stick with v7.5.9? With some apps, like internet-facing browsers, it’s good to always stay on top of updates for security reasons. But for an app like a fancy text editor, it’s not so dangerous to just stay on a version that already works for you. Turn off auto-updates, and stick with the version that’s “good enough”, that does what you want, even if it’s not the latest-and-greatest. There haven’t been a lot of killer-features added, mostly just incremental changes recently. Personally, if i weren’t trying to help people on the forum, I would still be on 7.5.8 right now.



  • I have a tricky question. What if one wants to create a plugin named “Doc” or “Config”? This plugin should reside in a folder with the corresponding name, right? ;)



  • @Vitaliy-Dovgan

    you’ve just made my day 👍

    😂😂😂



  • @Vitaliy-Dovgan said:

    :-)



  • @donho: When are you fixing the plugins per user feature you have broken? Are you able to answer?

    • If auto-update files are not installed the PluginAdmin does not load. So nobody can install “per User” plugins.
      NPP auto-update cannot disabled per machine.
    • Per user plugins cannot enabled in setup any longer. Why the hell?

    I need:

    • Notepad++ auto-update disabled (per Machine). A config.xml in notepad.exe folder seems not working (tested).
    • PluginAdmin is required
    • PluginAdmin with Automatic Update
    • Plugins need to be installed “per User” to %APPDATA% (and not to %ProgramData% where users have no access what causes an UAC)
    • Need to be able to disable automatic-updates for specific plugins. e.g. AutoUpdate=0 in global config .ini files.
    • Plugins do not install per architecture. That means you cannot run x86 and x64 on same machine. Per user plugins currently colides. The folder structure need to be adjusted to have “%APPDATA%\Notepad++\x86” and “%APPDATA%\Notepad++\x64” folders.

    Please repair Notepad++ ASAP so it can be used in Enterprise environments.



  • I’m admin in an enterprise environment and we’ve been using Notepad++ for a while. But with the latest changes I can no longer update the application because it would break basically every installation/“usage pattern” our users have adapted to.

    We’ve been deploying Notepad++ updates with Microsoft SCCM and then placing the “allowAppDataPlugins.xml” file in the program directory under “%ProgramFiles%\Notepad++”, allowing our users to install whatever plugin they want in their own profile under “%AppData%\Notepad++\plugins”. We do that because obviously we don’t want to give users admin privileges to install plugins in the program directory. We also don’t want to install plugins for the users ourselves. The support overhead would “kill” us.

    Is there any way to get this functionality back?

    • Load global plugins from “%ProgramFiles%\Notepad++\plugins”
    • Additionally load user installed plugins from “%AppData%\Notepad++\plugins” when “allowAppDataPlugins.xml” exists in “%ProgramFiles%\Notepad++”


  • @narutards

    this recent thread >>> install notepad++ plugin without admin rights <<< covers how to deploy/install 7.6.3 and above, so that users are able to install plugins without admin rights.

    it also includes a working deployment batch script as example.
    also feel free to open a separate new topic on your case, if you need different information or examples.

    if your questions don’t differ much from the original poster’s, you can comment on the same thread from above as well.



  • With the new structure of the plugins folder, I’m wondering whether an archive with a new version of a plugin should reflect this new structure?
    Let’s take NppExec plugin as an example. The old structure of its archive (NppExec_*_dll.zip) is:

    doc\NppExec…
    NppExec*.h
    NppExec.dll

    Should it now be changed to the following? -

    doc\NppExec\…
    NppExec\NppExec\*.h
    NppExec\NppExec.dll

    Such structure will reflect the current Notepad++'s expectations regarding its plugins and will need the new Plugin Manager’s script that deploys NppExec to be modified accordingly.
    Is it what is expected? Just want to clarify this in advance.



  • @Vitaliy-Dovgan

    this is a very good question.

    my first (unconfirmed and untested) thought is, that if the plugin’s release .zip structures are altered, they will be extracted as is, resulting in a doubled subfolder for each plugin (e.g. NppExec\NppExec\NppExec.dll).

    also as there is probably no possibility, that all plugin developers change the structure at the same time, plugins admin would need to have an intelligence, to be able to know where the plugin’s .dll is located within the plugin release zip’s folder structure.
    (alternatively, plugins admin would need some kind of extra bool flag, which tells it something like: newFolderStructure=true)

    very tricky everything is, intriguing and interesting and very tricky.



  • @Meta-Chuh said:

    very tricky everything is, intriguing and interesting and very tricky

    …and totally worth it…one little ad…



  • I know what to do. Two versions of the *dll.zip will be created: one with the old and another one with the new folder structure inside. So the Plugins Manager will be able to use either one. And finally, as time passes, just one version of the *dll.zip will survive.



  • @Vitaliy-Dovgan said:

    I know what to do. Two versions of the *dll.zip will be created: one with the old and another one with the new folder structure inside. So the Plugins Manager will be able to use either one. And finally, as time passes, just one version of the *dll.zip will survive.

    I think Plugin Manager will still cater to old plugin arrangement.

    It is plugin Admin that is managing pluings as per new arrangement.



  • @donho said:

    The applied plugin folder structure <PLUGINS_HOME>\myNicePlugin\myNicePlugin.dll remaines the same.

    To be clear you are saying plugins no longer load from <PLUGINS_HOME>? For example <PLUGINS_HOME>\myNicePlugin.dll is not supposed to work? I have several plugins in <PLUGINS_HOME> and none will load. I can of course make a directory for each of them, I am just wondering whether this is expected behavior and why the change.



  • Ok I found the answer in the Help Wanted post Plugins gone?! which says the folder structure is now needed. I did that and it’s working fine.

    (Unfortunately I couldn’t edit my previous post since edits are only allowed for 180 seconds. I suggest making that a much longer amount of time like 24 hours.)



  • WTF happened to the plugins?

    I need to urgently apply a Python script to our loca files, deadline is in like half an hour, and fucking Notepad++ can’t fucking see the goddamn pythin script plugin any more? WTF.



  • welcome to the notepad++ community, @Dave-Bongfishtester

    if you have a 30 minute deadline right now, just install notepad++ 7.5.9 (or whatever your previous version was) on top of your current notepad++ installation.
    your plugins will then be visible again.

    you can deal with the plugin setup of newer notepad++ versions later.

    best regards.


Log in to reply