[02:23:54] is it possible to create some content on one wiki and then transfer it to a new wiki in the future? I have a wiki for one organisation and would like to add some information about another organisation but I can't set up a wiki for the second organisation just yet because I don't own the domain name and I need someone else to create the A and AAAA records for me [02:24:19] !export [02:24:19] To export pages from a wiki, navigate to Special:Export on the wiki, type in the names of the pages to export, and hit "export". See for an example of this form. See also: !import [02:24:20] !import [02:24:20] To import a few pages, use Special:Import - you can also import pages directly from another wiki (see !importsources). For mass imports, use importDump.php - see for details. NOTE: when using content from another wiki, follow the LICENSE TERMS, especially, attribute source and authors! [02:24:42] awesome - thank you :) [03:33:59] I´m evaluating mediawiki for internal documentation for a small company : features, community are really impressive but I´m not clear on the authentication and authorization topic. My need is use activedirectory (or ldap) to authenticate users and authorize then to read/write part of the wiki. Documentation suggests taht authentication seems OK but I´ve seen several pages about the design that is not might never will be to limit access to pages [03:33:59] or name space and at the same time I see a lot of presentation on youtrube about enterprise wiki [03:36:06] so is it possible to limit part of the wiki to users/groups that leaves on an active directory without bending the original design of mediawiki too much ? [03:37:49] dasti: I am no expert, at all, but my impression is that limiting authorization of page edits of specific pages or groups of pages does not come easy. [03:38:46] dasti: We basically 1) require a person create a user and 2) allow users to modify every page. [03:38:52] karlpinc, that´s also my impression according to my reads i.e. https://www.mediawiki.org/wiki/Security_issues_with_authorization_extensions [03:41:21] dasti: I've used moin moin for fine control (moinmo.in). I've no clue how/whether there's AD/LDAP integration. With moin I've setup pages to be editable based on group. [03:42:05] but at the same time the nasa uses mediawiki ? how do they crontrol that ? [03:42:34] ok, moinmoin, I´ll check that [03:42:38] dasti: Different wikis for different sets of people? [03:43:12] hum...maybe [03:43:15] dasti: No reason you could not run multiple mediawikis (and have links between them). [03:43:38] dasti: Really, I've no idea. (Maybe they say? :-) [03:43:55] My case is a small business so the different wikis would be HR, finance, IT. common... [03:44:37] and each department would have private and public informations [03:44:38] dasti: Sounds awkward. Wikis sound easy, but I've had difficulty getting people to edit in situations like yours. It all depends on the people. [03:45:50] at first look creating a wiki for the 4 peoples (i.e HR) seems overkill, but that´s maybe just a newbie feeling [03:46:10] dasti: Awkward with mediawiki. On the other hand, as I say, I'm just "ordinary" when it comes to admining. [03:46:36] dasti: If you need something, you need something. Mostly people don't want to use _anything_. :) [03:48:13] haha [03:49:41] the difficulty when evaluating is to understand the phylosophy/design of a software [03:50:39] dasti: Mediawiki really wants to be a publically editable wiki. [03:51:37] dasti: I wonder if you could not do something at the webserver level to authenciate and allow access. (Don't use shibbolith, it's _way_ too complex.) [03:52:13] dasti: But I don't think this could give you edit/no-edit permissions. [04:05:44] karlpinc, indeed as I read further, it seems that it´s not deseigned to restric access to the content which matches what wikipedia does [04:07:09] karlpinc, on of my side goals was to enable people to contribute to wikipedia as they would learn to use mediawiki in the company [07:24:33] anybody know the likelihood of making this work w/o WikiEditor? https://www.mediawiki.org/wiki/Extension:CodeEditor [07:24:54] editing JavaScript in a plain text box is a horrific experience. [07:26:12] very frustrating that I cannot find a solution that doesn't require WikiEditor [07:26:20] nobody on my wiki ever wants us using that extension [07:27:44] Quasar`: er, what's wrong with WikiEditor? [07:32:25] the old school editors we have don't like its toolbar. [07:32:38] classic toolbar is simple and uniform [07:32:49] new one is more like an Office Ribbon [07:33:04] you can disable the WikiEditor toolbar by default [07:33:12] and then it'll show up only whenever CodeEditor is used...IIRC [07:39:51] guess I'll play around with that then, thanks. [10:30:09] Using 1.31 ArticleFeedbackv5 extension.json includes jquery.appear as a dependency, which is unknown. New to dependency debugging, how would I try to resolve this? [15:41:01] Fun bug I just ran into. For some reason MediaWiki 1.29 is causing PHP_SAPI to be overwritten with 'cli' while in the web server context.(php_sapi_name() stays correct however.) [15:47:58] Trela: do you mean the PHP_SAPI gives the correct value when looking at phpinfo() but wrong inside MediaWiki? [15:48:29] well, phpinfo() probably won't tell that, but a custom php file that prints that value [15:50:26] php_sapi_name() returns correctly, but the PHP_SAPI constant is wrong. [15:51:38] I mean, how do you know it's MediaWiki's fault and not the php or webserver itself? [15:51:40] Making a script that just var_dump()s those outside the context of MediaWiki always returns both correctly. [15:52:00] okay, that's the response I was expecting [15:52:04] Yeah. [15:52:19] funny, weird and scary lol [15:52:37] Weirder: 100% PHP_SAPI is wrong in the context of MediaWiki, but the moment I put var_dump(PHP_SAPI) in LocalSettings.php it becomes about 50% of the time. [15:53:05] I though constants couldn't be redefined, but with PHP anything is possible [15:53:55] :D [15:53:58] The PHP process itself should be able to redefine them internally, but really should not after they are initially set. [15:57:32] BOOM! [15:57:53] @Vulpix: The issue is whatever the last process to load the file into opcache is what sets the PHP_SAPI name. [15:58:08] https://github.com/bobbingwide/oik-batch/issues/19#issuecomment-285929511 [15:58:29] heh, opcache is always a good source of unexpected bugs [15:58:55] Time to make a large MediaWiki patch and submit it. [16:04:00] Actually, this may have been fixed in PHP 7.2. [16:10:21] Semi-fixed in PHP 7.2+, but unrelated. The actual proper fix is to not have opcache.enable_cli enabled. [23:54:38] https://www.mediawiki.org/w/index.php?title=Wikibugs&action=edit§ion=6 [23:54:41] > Note: When you edit this page, you agree to release your contribution according to the license specified in the 'licence' field. [23:54:55] that's new right? [23:55:04] jsonconfig-license-notice-license-unset [23:57:25] -> https://phabricator.wikimedia.org/T202469