Last modified: 2013-09-04 10:36:24 UTC
I'm not 100% sure this should be posted as an api issue. With Mediawiki 1.17 the Send To Wiki feature of OpenOffice/Libreoffice is broken. This could of course be intentional, because of some other feature that needed to change how remote publishing works, but I wanted to be sure and let everyone know.
Is that this OOo extension? http://extensions.services.openoffice.org/project/wikipublisher
Download link there gives "502 Bad Gateway" error, so can't try it...
That's the extension. It's built into the more recent versions of openoffice and libreoffice, so you don't have to download it, it's already there. I've confirmed that it works on 1.16.5 and 1.16.4 but not on 1.17.Beta1
Ah quite so -- it is hiding in there in LibreOffice 3.3.2. :D Did a quick test sending a page to local test wiki; it didn't actually save the edit successfully, but did go ahead and open up the (empty) page in my web browser as though it had been successful. Will see if I can see what it's actually doing...
As far as I can tell, the plugin just doesn't send any text along with the save POST... array ( 'wpTextbox1' => '', 'wpSummary' => 'whaaaaat', 'wpSection' => '', 'wpEdittime' => '20110602183351', 'wpSave' => 'Save page', 'wpEditToken' => '5eb180c19a480b22bd373da0cdd4fc47+\\', ) The wpTextbox1 field should contain the page text to be saved, but there's just nothing there.
(In reply to comment #5) > As far as I can tell, the plugin just doesn't send any text along with the save > POST... > > array ( > 'wpTextbox1' => '', > 'wpSummary' => 'whaaaaat', > 'wpSection' => '', > 'wpEdittime' => '20110602183351', > 'wpSave' => 'Save page', > 'wpEditToken' => '5eb180c19a480b22bd373da0cdd4fc47+\\', > ) > > The wpTextbox1 field should contain the page text to be saved, but there's just > nothing there. Ewww. So it doesn't even use the API? :(
lovely, guess i'm not totally crazy and the plugin is the culprit not mediawiki. Thanks for looking at it. Such a bad addon, but I was hoping it would make publishing articles easier for my users.
I get the same with 1.16 and current trunk (1.19-svn); no page gets saved.