Hi, BTW, it is extremely rare that anyone ever will face this issue ever. But anyway I'd like to post it here.
I suggest it is a hidden bug (or just such behavior) of XXE in the field of custom configuration. Initial conditions: 1. Imagine you write (or have) your own addon - configuration. And this addon uses a default XXE addon (configuration), supplied by default (there is a <requires> element within a custom .xxe_addon). 2. By default this addon is installed by XXE in a XXE installation directory. 3. Configuration uses include statement to include the default addon. I.e. <include location="xxe-config:docbook51/docbook51.xxe" /> As shown above a setup uses xxe-config get a default configuration docbook51.xxe within its default path. But, if by some reasons someone: - uninstalls the default installed addon (docbook51.xxe in that case) and installs further it to a user preference directory (by changing the appropriate settings in "Install addons" section in "Options|Preferences") or - installs custom addon with a default addons in a user preference directory as a result: a custom configuration will broke because of xxe-config settings. Are there any workaround to get custom addon functioning (by including "root" addon) irrespective the path, where "root" used addon is installed (either in XXE directory, or in user preference directory)? Thanks! -- regards, ET -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com https://www.xmlmind.com/mailman/listinfo/xmleditor-support
