Bug 132625 - Move mediawiki template and code into external extension
Summary: Move mediawiki template and code into external extension
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-03 07:07 UTC by andreas_k
Modified: 2023-09-22 13:42 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andreas_k 2020-05-03 07:07:57 UTC
In the template manager there is an mediwiki template. What is this template for? from a user point of view it's not easy to understood. 

Is it only an internal template file for the mediwiki export or can it be used from the user to do mediwiki styled writer files?
Comment 1 Heiko Tietze 2020-05-07 14:14:52 UTC
Would require to get insights why this template was added in first place.
Comment 2 Heiko Tietze 2020-05-13 18:19:10 UTC
Quite a lot around mediawiki https://opengrok.libreoffice.org/search?project=core&full=mediawiki likely relying on the template. We could drop everything but this should go through the ESC.
Comment 3 Heiko Tietze 2020-05-14 14:34:28 UTC
Mediawiki export is a bundled extension and if we remove the template we also have to pack the code and scripts into an external extension. Feel free to do so, it's not what the majority of users need. Could also live with keeping everything bundled, meaning WF.
Comment 4 Dennis Roczek 2020-08-25 12:15:03 UTC
I would love to see the whole extension in a separate git. I still think that bundling that extension makes sense, but I have no clue how to move that so that the build does not break.
Comment 5 QA Administrators 2022-08-26 03:36:35 UTC
Dear andreas_k,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug