On 5/17/20 8:15 AM, Carl Marcum wrote:
On 5/17/20 6:18 AM, Marcus wrote:
Am 13.05.20 um 16:07 schrieb Carl Marcum:
Hi All,
There are quite a few pages in the developer guide that display as
blank.
I believe this problem goes back to an upgrade that was done to the
wiki.
After some recent testing I believe the issue is with a custom
plugin of ours referred to as IDLTags.
This plugin uses tags in the wiki like <idlmodule> and <idlm> to
generate links back to the IDL documentation.
There was a page for it but it was removed in 2012 so I can't find
more information on it.
I have no idea where the code for it is.
As this issue has a few birthdays now I propose a workaround to edit
the affected pages and replace these tags with hard links to the IDL
documentation.
We could comment the changes with [IDL WORKAROUND] or something so
we could find them when the plugin problem is resolved.
If this seems reasonable I'll seek lazy consensus after this.
I've no clue what the root cause for the problem is nor how to (try
to) fix it. So, I cannot add much help. However, your proposal sounds
like a good starting point. Or maybe it is alredy the solution. Let's
see.
+1
Marcus
Hi Marcus,
I've confirmed the idl tags are causing the pages to display blank.
I have went ahead and fixed this one [1] and noted the change with
[IDL WORKAROUND] so we can find them later.
The problem links are way down in the Service Manager section.
These pages are too important for developers working on client apps
and extensions ** like me ;) ** to leave them broken.
As Peter noted, fixing the plugin would be better but this can be
undone if that ever happens.
I'm going to seek lazy consensus for the remainder as there are quite
a few broken pages.
[1]
https://wiki.openoffice.org/wiki/Documentation/DevGuide/FirstSteps/First_Contact
Thanks,
Carl
I think the <idl> tag is okay and the problem may be in the <idlm>
and/or <idls> tags.
I've checked the first 3 sections of the developer guide and found 17
broken pages already.
There are 24 total sections so this may be a large enough issue to also
try to solve the root cause in the wiki extension in parallel.
https://wiki.openoffice.org/wiki/Documentation/DevGuide/FirstSteps/Objects,_Interfaces,_and_Services
https://wiki.openoffice.org/wiki/Documentation/DevGuide/FirstSteps/Using_Services
https://wiki.openoffice.org/wiki/Documentation/DevGuide/FirstSteps/Example:_Working_with_a_Spreadsheet_Document
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Interfaces
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Services
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Modules
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Singletons
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Collections_and_Containers
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Basic/Listeners
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Bridge/Using_Automation_Objects_from_UNO
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/Bridge/Type_Mappings
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/CLI/Type_Mappings
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/CLI/Lifetime_Management_and_Obtaining_Interfaces
https://wiki.openoffice.org/wiki/Documentation/DevGuide/ProUNO/CLI/Writing_Client_Programs
https://wiki.openoffice.org/wiki/Documentation/DevGuide/WritingUNO/Predefining_Values
https://wiki.openoffice.org/wiki/Documentation/DevGuide/WritingUNO/Jobs/Implementation
https://wiki.openoffice.org/wiki/Documentation/DevGuide/WritingUNO/Intercepting_Context_Menus
Best regards,
Carl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
