Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi Kendy,

Jan Holesovsky wrote on 2012-12-19 17:05:

Seems to work nicely to me - so go ahead & switch! :-)

cool, happy to hear that! :-)
The only thing missing (besides some cleanup and removing of unused extensions) is to enable the API.

If I set

$wgEnableAPI = true;
$wgEnableWriteAPI = true;

you should be able to access the API. However, in your setup, I found that you had to disable $wgArticlePath ("must be disabled for API, otherwise it is confused").

Can you briefly explain what the issue is? Maybe I find a solution so we can have both in one instance. If not, I'll simply set-up a second instance for the API access.

Florian

--
Florian Effenberger, Chairman of the Board (Vorstandsvorsitzender)
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Jabber: floeff@jabber.org | SIP: floeff@iptel.org
The Document Foundation, Zimmerstr. 69, 10117 Berlin, Germany
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: http://www.documentfoundation.org/imprint

--
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.