Maybe the time has come for a reset of plugin compatibility, with a revised set of standards which Notepad++ and plugins need to adhere to.

IMO, the management of plugin compatibility is for plugins which cannot run previous certain versions, for example a plugin cannot be loaded/run under v7.8.4 and the previous versions because the API used by the plugin in question was introduced from v7.8.5.

In our actual situation, I don’t see how the plugin compatibility management can help, since the plugins are supposed to work in current version of Notepad++ and its future versions.

I understand that Notepad++ needs to evolve, but changes which make multiple plugins incompatible is a real problem.

Just confirmed PythonScript crashes Notepad++ if the editor.getTextRange() function is called

@PeterJones

Also “PerlScript”:

editor->getTextRange(MIN, MAX)

crashes Notepad++ 8.2.2

Cheers.

Updated list of affected plugins reported

Just confirmed PythonScript crashes Notepad++ if the editor.getTextRange() function is called. Using PythonScript 3.0.7-alpha.

I only have 2 scripts that use this call, so not a big deal for me.

Opened issue: https://github.com/bruderstein/PythonScript/issues/218

Cheers.

@Michael-Vincent

I should have mentioned that the speech plugin rebuild is my own with some modifications since the original author was unresponsive, same with quickcolorpicker and taglet.
I don’t believe quick color picker is in plug-in admin and the speech plugin and tagleet which are in plug-in admin are from their authors, not my rebuilds.

If you (or anyone) who want to maintain them, for the sake of good for the community, you’re welcome.
Otherwise, I can include them in https://github.com/npp-plugins, with the infos of original project of course.

===============================================

I just posted the following announcement in Plugin Development:
https://community.notepad-plus-plus.org/topic/22471/recompile-your-x64-plugins-with-new-header

I should also replace all the Sci_Position.h in every single project of Npp-Plugins, especially in plugintemplate & plugindemo. It’ll be done before the v8.2.2 release (hopefully).

SpeechPlugin, QuickColorPicker, TagLEET

I should have mentioned that the speech plugin rebuild is my own with some modifications since the original author was unresponsive, same with quickcolorpicker and taglet.

I don’t believe quick color picker is in plug-in admin and the speech plugin and tagleet which are in plug-in admin are from their authors, not my rebuilds.

Cheers.

give the plugin authors at least a few days, and maybe even a week, before taking RC5 to “full release”

Yes, I second that.

There is a successful rebuild of the Compare plugin reported:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/11104#issuecomment-1026270038

Updated list of affected plugins reported: DSpellCheck, ComparePlugin, HexEditor, CsvQuery, SpeechPlugin, QuickColorPicker, TagLEET.

I understand you need to do what’s best for the core application. But please make sure you give the plugin authors at least a few days, and maybe even a week, before taking RC5 to “full release”, so that they have a chance to fix the issue before you release (so that you can turn off the plugin removal from the installer). There has only been a day or so since the problem was discovered, let alone before the authors were notified, or have had a chance to update their code. Going to the drastic measures of disabling plugins during the install process is harsh, and will leave many users frustrated or upset.

ComparePlugin and DSpellCheck are two of the most popular plugins, based on what I see in Debug Info posted here, and based on the kinds of questions we get in the Forum. I use ComparePlugin daily, and I will not be able to upgrade to v8.2.2 if it is released with the ComparePlugin incompatibility; and many users require DSpellCheck for their daily workflow as well. It would not surprise me if there were quite a few users who would abandon Notepad++ if DSpellCheck and/or ComparePlugin are not available.