v8.8.9 and ConfigUpdater plugin
-
@donho said in Notepad++ 8.8.9 release candidate:
- Add ability to update users’ langs.xml & stylers.xml from model XML files. (Fix #17128)
Because this change is listed here, I’m posting this ConfigUpdater plugin error here.
Let me know if I should also direct it to the plugin repository as an issue:The same error is reported for all four files, even after N++ is re-launched in admin mode:
--- ConfigUpdater run at Friday, 5 December 2025 13:42:41 ... --- Checking Styler/Theme File: 'C:\Users\...\AppData\Roaming\Notepad++\stylers.xml' --- Checking Styler/Theme File: 'C:\Users\...\AppData\Roaming\Notepad++\themes\DarkModeDefault.xml' --- Checking Styler/Theme File: 'C:\Program Files\Notepad++\themes\Bespin.xml' --- Checking Language File: 'C:\Users\...\AppData\Roaming\Notepad++\langs.xml' XML validation FAILED: The attribute 'modelDate' on the element 'NotepadPlus' is not defined in the DTD/Schema.@PeterJones something for you?
-
It’s already fixed in the GitHub, but I didn’t make the plugin list cutoff deadline.
And no, plugin bugs shouldn’t ever be in the announcement topic replies, until it’s proven that N++ stopped honoring the API contract, which is not the case here.
-
I guess I should have also said that the new version of ConfigUpdater has a new action, Reset Validators, which is what you need to run in order to fix that validation problem. So download the newest ConfigUpdater plugin v2.4.0 from GitHub releases, manually update your copy, run Notepad++, and run Plugins > ConfigUpdater > Reset Validators, and from then on, it should no longer complain about
modelDate. -
It’s already fixed in the GitHub, but I didn’t make the plugin list cutoff deadline.
Are you talking about it?
https://github.com/notepad-plus-plus/nppPluginList/pull/999It’s in the current PluginList in RC normally.
-
@donho said in v8.8.9 and ConfigUpdater plugin:
It’s in the current PluginList in RC normally.
Sorry, you’re right. I must’ve misread what I saw in the Plugins Admin.
@Users: Even better: you can just update the plugin using Plugins Admin, then Reset Validators, and the ConfigUpdater will stop complaining. :-)
-
@donho said in v8.8.9 and ConfigUpdater plugin:
It’s already fixed in the GitHub, but I didn’t make the plugin list cutoff deadline.
Are you talking about it?
https://github.com/notepad-plus-plus/nppPluginList/pull/999It’s in the current PluginList in RC normally.
I ran:
- Plugins > ConfigUpdater > Reset Validators
- Plugins > ConfigUpdater > Update Config Files
The open tab with ConfigUpdater.log no longer shows any errors