Notepad++ 7.6 & new Plugins Admin
-
@bveldkamp said:
How do I open this new plugin manager?
In the english locale there is in the main menu bar an entry
Plugins. I don’t know how it is called in your locale, to find it you could switch to english via(menu) Settings -> (register card) General -> (combobox) Localization. In the drop down menu ofPluginsyou will find an entryPlugin Admin. -
I confirm as well. Notepad++ needs to use folder names based on architecture e.g. %USERPROFILE%\AppData\Local\Notepad++\x64\ and %USERPROFILE%\AppData\Local\Notepad++\x86 etc or some other structure that has unique folders for the 2 x64 and x86 architectures.
-
Forget my last posting, here is a much better advice.
-
I see now that the menu is there when I run NP++ ‘As Administrator’, but not for my normal user account. I’d expect it to be available for all users especially now that plugins go into %LOCALAPPDATA%.
A complete reinstall didn’t change anything.
FWIW, I have installed 7.6 x64
-
@bveldkamp
%LOCALAPPDATA% is personalized for each user, so if installed as Administrator, all other users won’t see any pluginsthe only workaround i found so far for using all plugins for all users is:
install notepad++ to C:\Notepad++ with the option “Do not use %APPDATA%” selected
(don’t install inside C:\Program Files\ when selecting “Dont use %APPDATA%” or you will not see plugins nor the plugins admin)hope it helps
-
wow guys, this is a big step back.
now its not possible anymore for sysadmins to provide plugins for all users in the notepad++ plugins directory in the program files install folder. now plugins are only in the current users profile? seriously? -
@Zanzaraaa
i understand your point, but it’s not quite a big step back for np++ imho.multiuser installs was just something noone of us users had tested thoroughly enough prior to the 7.6 release, so it’s more our fault as “pre release testers”.
the only thing needed to fix this behavior is that a present DoLocalConf.xml overrules the trigger that plugins manager ignores DoLocalConf.xml if the install is within %PROGRAMFILES% or %PROGRAMFILES(x86)%
currently plugins manager and the plugin routine just ignores a DoLocalConf.xml (don’t use %APPDATA% setting at install) if notepad++ lies within %PROGRAMFILES% or %PROGRAMFILES(x86)%
maybe @donho has a fix soon, maybe not, but anyway noone is really forced to use 7.6 instead of 7.5.9 or a later release, so it doesn’t seem that much of a problem
-
@dinkumoil said:
Point 1. is also nasty for users because currently they can not download easily a NppPluginList.dll and I already thought you will not refuse to change that.
Which folder is suitable for this enhancement?
-
@Andrew-Briggs said:
I confirm as well. Notepad++ needs to use folder names based on architecture e.g. %USERPROFILE%\AppData\Local\Notepad++\x64\ and %USERPROFILE%\AppData\Local\Notepad++\x86 etc or some other structure that has unique folders for the 2 x64 and x86 architectures.
Please give me a reason that we need that.
-
@donho said:
Which folder is suitable for this enhancement?
As @SinghRajenM already suggested here:
%allusersprofile% … or can it be kept in %programfiles% itself
-
@Zanzaraaa said:
now its not possible anymore for sysadmins to provide plugins for all users in the notepad++ plugins directory in the program files install folder. now plugins are only in the current users profile? seriously?
IMO, every user has his/her need, so it makes sens that each user installs his/her plugins in his/her space. Or am I missing some cases?
-
@donho said:
IMO, every user has his/her need, so it makes sens that each user installs his/her plugins in his/her space. Or am I missing some cases?
yes this seems ok for home users.
but in company environment where you have some plugins that you want or have to provide to ALL users, you just had to copy the plugins into the program files plugin folder and every user has it when he starts notepad++. no need for users to manually mess around.
also normally i delete the plugin manager after installation because we dont want users to use it to manually install or update plugins. they should only use the ones we provide. -
There is also the case when some plugins are needed by ALL users using the computer and some are for personal use.
Best would be to be able to install and load plugins from %ALLUSERSPROFILE% as well as from %LOCALAPPDATA%. -
@Zanzaraaa said:
but in company environment where you have some plugins that you want or have to provide to ALL users, you just had to copy the plugins into the program files plugin folder and every user has it when he starts notepad++. no need for users to manually mess around.
OK, I see. How about an empty file
pluginsForAllUser.xmlmakes Notepad++ load from %ALLUSERSPROFILE% ?also normally i delete the plugin manager after installation because we dont want users to use it to manually install or update plugins. they should only use the ones we provide.
So I will provide a simpler way for the deployment of Notepad++ - could you test to see if it’s suitable for companies?
-
@donho said:
@Zanzaraaa said:
OK, I see. How about an empty filepluginsForAllUser.xmlmakes Notepad++ load from %ALLUSERSPROFILE% ?Yes that sounds good. Also pnedevs idea is good. it should be possible to define if you want plugins to be loaded from both paths or only one.
But why use %ALLUSERSPROFILE% and not keep the plugins folder in the program files install folder like in pre 5.7 versions?
Also i’m still concerned about migration of existing plugins. i wonder if it is possible to keep things like they were in pre 5.7. that you dont have to migration plugins from the plugin folder into their own subfolder.So I will provide a simpler way for the deployment of Notepad++ - could you test to see if it’s suitable for companies?
Sure, i can test it.
-
@donho said:
@Andrew-Briggs said:
I confirm as well. Notepad++ needs to use folder names based on architecture e.g. %USERPROFILE%\AppData\Local\Notepad++\x64\ and %USERPROFILE%\AppData\Local\Notepad++\x86 etc or some other structure that has unique folders for the 2 x64 and x86 architectures.
Please give me a reason that we need that.
This was not my comment, but I agree with it. Since DLLs can only be loaded by a version of Notepad++ compiled for the same architecture, it makes sense to design it such it can safely execute the 32-bit version and a 64-bit version side-by-side on the same machine.
-
@dinkumoil said:
@donho said:
Which folder is suitable for this enhancement?
As @SinghRajenM already suggested here:
%allusersprofile% … or can it be kept in %programfiles% itself
Use of the Notepad++ execution directory may also make Notepad++ running in portable mode more plugin friendly since it will all be self-contained.
-
@pnedev said:
There is also the case when some plugins are needed by ALL users using the computer and some are for personal use.
Best would be to be able to install and load plugins from %ALLUSERSPROFILE% as well as from %LOCALAPPDATA%.The idea is good, but there’ll be some situation which make Plugins Admin behaviour inconsistent:
If the same plugin foo.dll is in 2 different location,%ALLUSERSPROFILE%\Notepad++\plugins\foo\foo.dlland%LOCALAPPDATA%\Notepad++\plugins\foo\foo.dll
Notepad++ will load only one (old behaviour). If user removes one of 2, the remain one will be loaded by Notepad++ - user will be confused.So the best behaviour (to me) is loading plugins only from one location.
-
@NoMoreFood said:
@dinkumoil said:
@donho said:
Which folder is suitable for this enhancement?
As @SinghRajenM already suggested here:
%allusersprofile% … or can it be kept in %programfiles% itself
Use of the Notepad++ execution directory may also make Notepad++ running in portable mode more plugin friendly since it will all be self-contained.
Indeed, it’s the current behaviour - if Notepad++ is not installed in
Program Files. -
@NoMoreFood said:
it makes sense to design it such it can safely execute the 32-bit version and a 64-bit version side-by-side on the same machine.
Why, what is the justification behind that?
Just curious.
