On 10/4/2017 4:43 PM, Don Lewis wrote: > On 4 Oct, Keith N. McKenna wrote: >> On 10/4/2017 3:03 PM, Don Lewis wrote: >>> On 4 Oct, Matthias Seidel wrote: >>>> Am 04.10.2017 um 18:27 schrieb Keith N. McKenna: >>>>> On 10/4/2017 11:49 AM, Matthias Seidel wrote: >>>>>> Am 04.10.2017 um 17:42 schrieb Keith N. McKenna: >>>>>>> On 9/30/2017 8:42 AM, Don Lewis wrote: >>>>>>>> On 29 Sep, Matthias Seidel wrote: >>>>>>>>> That might explain why I have never seen a working WikiPublisher in >>>>>>>>> the >>>>>>>>> last releases. >>>>>>>>> (Since at least 4.1.2 we build with that option on Windows) >>>>>>>>> >>>>>>>>> The question is: Do we need to build with that option if no one missed >>>>>>>>> the plugin? >>>>>>>> I've never tried to use it, so I don't know if it works or not. >>>>>>>> >>>>>>> Currently in version 4.1.3 the send to MediaWiki option does not work. >>>>>>> My SWAG is that the Sun Wiki Publisher Extension was never updated to >>>>>>> work with the API changes introduced with the 4.0.0 Release. >>>>>> Confirmed (also for 4.1.4 RC4) >>>>>> >>>>>> However it can still be installed as an extension: >>>>>> https://extensions.openoffice.org/en/project/sun-wiki-publisher >>>>>> >>>>>> Last time I tried it the "send to" option was there, but I never tested >>>>>> further... >>>>>> >>>>>> Matthias >>>>>> >>>>> Mathias; >>>>> >>>>> It is the extension that I tested and it does not work. There were API >>>>> changes introduced in AOO Version 4.0.0 that were most likely never >>>>> updated in the extension. It is the extension that adds to MediaWiki >>>>> into File/Send. >>>>> >>>>> Regards >>>>> Keith >>>> >>>> OK, I misunderstood. >>>> >>>> My hope was that at least this old extension would work, since building >>>> with --enable-wiki-publisher (tried also the additional >>>> --with-servlet-api-jar) does not have any effect on a build. >>>> We build releases with that option, so normally there should be no need >>>> to install this (old) extension. >>> >>> The --enable-wiki-publisher should cause the .oxt file for the extension >>> to be built. On FreeBSD that ends up getting packaged along with >>> everything else and gets installed along with the rest. By default, if >>> you want to use it, you have to go into Extension Manager and dig around >>> in the installed tree to find the .oxt file and add it. >>> >>> I haven't tried building this extension on either Linux or Windows, so I >>> don't know if/how it gets packaged. >>> >>> I've got some patches in the FreeBSD port of the snapshot of trunk that >>> causes the extensions that are built along with the rest of the source >>> to be treated as integrated extensions so they automatically show up as >>> installed in Extension Manager. With that I get a functional send >>> button that pops up a dialog box that asks for MediaWiki server and some >>> other info. >>> >>> There is a bunch of stuff scattered around the wiki about bundled and >>> integrated extensions and how they should be packaged. >>> >> This gets more and more interesting. I have added the Sun Wiki Publisher >> extension to my Windows installation and It adds a "to MediaWiki" entry >> to the File/Send options. If clicked it opens the dialog box looking for >> the wiki URL and username and password however it does nothing with the >> information which is what led me to believe that the API changes from >> AOO 4.0 had not been added to the extension. That they hadn't would make >> sense since the last time it had been uploaded to the extension site was >> 2009-09-06. Does the extension code that the FreeBSD port builds and >> installs actually use the information and create the a page on the wiki >> based on the document it is run against? > > I stopped where I did because I don't have a wiki that I can test > against. > Don; I can create an mwiki account for you if you are interested in testing your changes further. Just reply with a user name that you would like.
Regards Keith
signature.asc
Description: OpenPGP digital signature
