Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG Report] NP++ (x86) issues with Config stuff still reading/writing to AppData even doLocalConf.xml is present. #3065

Closed
MelchiorGaspar opened this issue Mar 18, 2017 · 5 comments

Comments

@MelchiorGaspar
Copy link

commented Mar 18, 2017

Description of the Issue

I have been having an issue for a idk a couple of years
or so that is when I upgraded from using Windows XP to using Windows 7
and wanted to finally report it...

I have an issue with NP++ still writing/reading config stuff to the
AppData folder even though I have it setup not to do this during install/updates..
ie. doLocalConf.xml is present

I have found the only workaround was to set the compatibility mode to
Windows XP SP3... then it works right...

however as updates progress using compatibility mode will become more...
troublesome such as the NP++ main program update feature does not work
in the 32bit version because the program thinks its running on ok do to the
above workaround...

Steps to Reproduce the Issue

n/a I guess

Expected Behavior

NP++ should write and read all config files and other files from
C:\Program Files (x86)\Notepad++\
plus all sub folders for plugins and their config files when doLocalConf.xml is present in the main program folder...

Actual Behavior

mentioned in above description.

Debug Information

Notepad++ v7.3.3 (32-bit)
Build time : Mar 8 2017 - 03:37:37
Path : C:\Program Files (x86)\Notepad++\notepad++.exe

Admin mode : OFF <-- While I do not have this enabled in the compatibility tab...
I do have full permissions on the Program Files folder(s)
so like in the in days...

Local Conf mode : ON

OS : Windows XP (64-bit) <-- This is do to the use of compatibility mode as a workaround, I am using
using Windows 7 Ultimate (64-bit)

Plugins : DSpellCheck2.dll mimeTools.dll NppConverter.dll NppCrypt.dll NppExec.dll NppExport.dll NppFTP.dll NPPJSONViewer-win32.dll PluginManager.dll ReloadButton.dll SecurePad.dll SpellChecker.dll

n/a at this time..

@MelchiorGaspar

This comment has been minimized.

Copy link
Author

commented May 10, 2017

I don't know if it works or not but or if its allowed... but.. bump..? ;)
I do so because its been since March since I posted this, and no dev has seen it or replied :/

@MelchiorGaspar MelchiorGaspar changed the title Notepad++ (x86) issues with Config stuff still reading/writing to AppData even doLocalConf.xml is present. [BUG Report] NP++ (x86) issues with Config stuff still reading/writing to AppData even doLocalConf.xml is present. Aug 20, 2017

@MelchiorGaspar

This comment has been minimized.

Copy link
Author

commented Aug 20, 2017

ok I'm gonna bump this again..
no one has replied to this ticket,
since I created it back in March 2017....

@IBaydenI

This comment has been minimized.

Copy link

commented Feb 15, 2018

I had the exact same issue today. Also on Windows 7 64bit. We suspect that it might have something to do with the space characters in "Program Files (x86)". We were using Version 7.5.4. This really is a mayor issue when dealing with machines where multiple users are supposed to be using the same config

@MelchiorGaspar

This comment has been minimized.

Copy link
Author

commented May 1, 2019

my work around was to reinstall NP++(x86) to C:\Notepad++ and then copy all the config data and plugins from the old Program FILES folder to the new location... and it works now...

@MetaChuh

This comment has been minimized.

Copy link
Member

commented May 2, 2019

@MelchiorGaspar

yes, your workaround is the correct way.

due to missing user write permissions at %ProgramFiles% and %ProgramFiles(x86)% notepad++ can not write the config files to these folders.
the newer version installers have the option don't use %AppData% greyed out for this reason, as soon as it detects, that it will be installed at a program files folder.

sorry for the inconvenience and many thanks for reporting back now.

best regards.

@MetaChuh MetaChuh closed this May 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.