[00:36:53] Hello [00:51:48] who here has experience with htmlform/ooui? [01:07:03] Is there any way (perhaps an extension?) to interpret all newlines as linebreaks, similar to the extension? [01:21:05] elven: you mean a single linebreak is an actual linebreak? With the editor two linebreaks = 1 actual linebreak [01:32:02] CZauX - Right. I understand why that behavior is useful for Wikipedia, but for my internal wiki I'd prefer a more literal syntax. [01:46:38] It might be possible to make an extension to do that, though it has to only effect normal text I would guess, and avoid other wiki markup. [02:17:05] Thanks. I modified Parser.php locally to do what I want. It's crude, but it solve the problem. http://pastebin.ca/raw/3724141 [03:21:15] !ops hola alvaro molina [04:53:53] !ops hola alvaro molina [11:04:59] hi. I want to apply a simple "validator" that looks at the structure of a document before it is saved and warns the user of mistakes and errors. I thought it might be the easiest thing to just put on a javascript that validates this. but the [11:05:25] validation includes stuff like "is in a category A, such that category A itself is in a special category B" [11:05:33] is there an ajax-api that can do this? [11:05:50] and if not, what's the best way to modify the mediawiki-code (such that it can easily be updated again)? [11:07:05] it is rather simple otherwise, like "a certain subsection A *must* have at least one subsection B", etc. [11:17:12] I just thought that a javascript would be the least invasive [14:30:49] Hi. I'm trying to develop a plug-in for MediaWiki, but I'm a little bit confused by the documentation (some parts look outdated). According to https://www.mediawiki.org/wiki/Manual:Developing_extensions, the MyExtension.php file is now changed by a json with metadata. However, it seems that https://www.mediawiki.org/wiki/Manual:Special_pages doesn't take this into account when adding the [14:30:49] new Special Page. How should it be done now? [14:36:58] Timvde: it's vaugely the same [14:37:47] Timvde: It's documented in https://www.mediawiki.org/wiki/Manual:Developing_extensions#Making_your_extension_user_configurable [14:38:18] Oh, I guess I shouldn't have skipped that section (it doesn't nee dto be user configurable) [14:38:26] s/nee dto/need to/ [14:39:07] why there is no download for WM 1.28.0? [14:39:16] Asterixf2: Because it's not a release yet [14:39:17] MediaWiki* [14:39:29] Timvde: I filed a bug to have that page updated anyway [14:39:30] I'll use that longer json as a starting point, thanks [14:40:43] Reedy: Thanks :) [14:42:33] Reedy: what is the best approach to installing mediawiki for the purpose of forking some articles? [14:42:43] Bitnami / manual installation on ubuntu? [14:43:05] Depends on your technical ability, I guess [14:45:00] Reedy: with manual install would you recommend using XAMPP or apt-get all packages individually on ubuntu? [14:45:14] I'd do it manually, personally [14:45:17] thx [15:26:56] *push* hi. I want to apply a simple "validator" that looks at the structure of a document before it is saved and warns the user of mistakes and errors. I thought it might be the easiest thing to just put on a javascript that validates this. but the validation includes stuff like "is in a category A, such that category A itself is in a special category B" is there an ajax-api that can do this? and if not, [15:26:58] what's the best way to modify the mediawiki-code (such that it can easily be updated again)? it is rather simple otherwise, like "a certain subsection A *must* have at least one subsection B", etc. [15:27:26] The usual way to modify code so you don't have to patch core... [15:27:40] Is to create an extension, and use the various hooks that MW provides [15:27:41] !hooks [15:27:42] Hooks allow you to run functions at various points in the main MediaWiki code. For more information about using hooks in MediaWiki, see . [15:51:25] hi! [15:51:39] can someone tell me what file contains $wgMaxShellMemory ? Is it in a mediawiki conf file or php? [15:52:12] i'm developing an extension that includes some CSS, which i'm adding to the DOM via the BeforePageDisplay hook, using the $out->addModules method as recommended [15:52:32] but the CSS is loading late, which causes a flash of unstyled content [15:52:38] anyone knows how to solve that ? [15:54:10] Sophivorus, addModuleStyles() [15:54:58] MaxSem: thanks, that was it :-) :-) [15:55:19] chunkymonkey: It's defined in DefaultSettings.php [15:59:21] edit DefaultSettings.php or add to localsettings.php ? [15:59:34] chunkymonkey: What are you trying to do? [16:01:52] having trouble with Semantic Forms [16:02:41] Semantic Forms/Common problems page suggests adding more memory [16:17:55] wikipedia uses ImageMagick or GraphicsMagick? [16:19:22] rsvg I think [16:56:54] Reedy: so you would use PHP? [16:57:06] schoppenhauer: For what? [16:57:16] Asterixf2: imagemagick, rsvg, vips... [16:57:25] Reedy: for validating? [16:57:36] schoppenhauer: depends how important your validation is [16:57:39] Some people don't have JS [16:57:42] Or have it turned off [16:57:54] So... You can't guarantee client side validation is done [16:58:02] In most cases, you should do it in JS and in PHP [16:58:54] hello! [16:59:11] guess what i finally found the solution of my spoiler thing? [16:59:16] Reedy: I do not need *hard* validation. I just want to warn the user. [16:59:34] Reedy: but if a plugin is simple, then I will use it. [16:59:40] just want to minimize maintenance [17:02:53] it's was too simple: i jusrt have to use that https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23switch which it's {{#switch: {{{type|}}} alert = {{Spoiler_Alert}} | comic = {{comic = {{Spoiler_Comic}} | novel = {{Spoiler_Novel}} game = {{Spoiler_Game}} }} and that is all [17:06:42] allaze-eroler: you could also use {{spoiler {{{type}}}}} [17:06:55] oh! [17:07:07] is that so? [17:08:26] heh [17:08:52] does it let me do thing like {{spoiler | type = alert|comic|novel}} ? [17:09:22] the inner most {} will get broken out first [17:09:31] i see [17:14:34] PageContentSaveComplete … is this the right thing to validate? [17:15:18] can I use it to trigger a warning or something? [17:16:29] is there a tutorial for writing mediawiki-plugins? (that is, somewhere to start?) [17:18:10] I suspect that hook would be far too late in the process [17:19:47] the prolem is, I need to validate categories, etc. [17:19:54] so it probably must be saved [17:20:04] ok, what I'd rather want to have is some banner [17:21:18] that is above the page, a warning "This article does not validate" [17:21:38] and maybe adding it into a category "Not Validating" [17:26:16] what is an appropriate hook for this? [17:28:57] So, I'm looking into implementing a shibboleth plugin for Mediawiki (Sadly, my university's shibboleth is not default and doesn't work with the "Shibboleth Authentication" add-ons). I want to use the new Session/AuthManager for his. Just making sure: I need the SessionProvider for this, right? https://www.mediawiki.org/wiki/Manual:SessionManager_and_AuthManager#As_a_provider [17:31:07] schoppenhauer: you may want to take a look at the AbuseFilter extension, which can give a warning on page save [17:31:10] !e AbuseFilter [17:31:10] https://www.mediawiki.org/wiki/Extension:AbuseFilter [17:33:16] Vulpix: thx, i will look into it [17:38:36] hm. can I check for categories the page is in? [17:40:16] because it doesn't look like that [17:41:00] and generally, it doesn't really do parsing [17:41:27] is it possible to pass a function directly to the abuse-filter? [17:47:29] I don't know if you can somehow add an own function to the list of functions that AbuseFilter supports, so you can perform your custom validations in PHP [17:48:10] well, the point is, it just cannot do *anything* of the stuff I want [17:48:18] but thats clear, its made for something else [17:48:41] and i actually do not want to keep people from saving [17:48:55] i just want to show a warning everytime something saved is displayed [17:51:44] like, before rendering or so [17:52:35] AF can display a warning, and if the user hits save again, it saves without displaying the warning again [17:53:43] that's not what i want [17:54:02] but AF doesn'T have the functions I need anyway [17:54:13] https://www.mediawiki.org/wiki/Manual:Hooks/EditFilter ← appears to be the right thing to hook, right? [17:55:48] hm. but I can't modify the page afterwards, apparently [17:56:08] I can just reject it [17:56:26] can I modify the saved text (like adding a banner)? [17:57:07] and: will this work with the preview too? [17:59:45] hm. [17:59:52] http://git.altlinux.org/people/dottedmag/public/mediawiki.git?p=mediawiki.git;a=blob;f=extensions/WarnNoCategories/WarnNoCategories.php;h=42c49e7117466b4f433714c843ff61e0255089a0;hb=HEAD adds a hidden object to $output [17:59:54] wtf? [18:07:09] hm. I don't really understand https://www.mediawiki.org/wiki/Extension:PageNotice … I *think* as far as I understood that I *could* now add a category automatically. is there some extension that shows some banner whenever an argicle is in a specific category? [18:09:26] there appear to be per-namespace headers, etc., but no headers for categorized files [18:09:42] I think we have a feature request and patch-in-review for that for core [18:09:55] Editnotices based on article's category membership [18:10:18] only for action=edit though, not viewing articles [18:15:06] that's … not hat I want :( [18:15:28] anyway … [18:16:01] so as far as I see, with EditFilter, I can warn the user without preventing saving, and automatically add a category to the page, right? [18:16:04] @ Krenair [18:20:46] (2 [18:27:17] Hi [18:30:26] I have installed MW 1.27.1, and I can�t log in. It says: �There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Go back to the previous page, reload that page and then try again.� [18:36:48] Sloyment: if you have set any cache to CACHE_ACCEL in LocalSettings.php, you may need to set $wgSessionCacheType to CACHE_DB [18:40:24] Vulpix: Thanks :-) [18:41:39] But I did not change LocalSettings.php; it was generated automatically with CACHE_ACCEL enabled. [18:43:23] Sloyment: try adding $wgSessionCacheType = CACHE_DB; [18:55:35] ah yes Meneth ! i noticed that in your ambox, there is some error in coding. mostly about class syntax. [18:56:48] Vulpix: Done. It works now. :-) Thank you. [18:57:19] yw [18:58:32] anomie: ^ the installer shouldn't recommend broken settings, shouldn't it set $wgSessionCacheType if it sets $wgMainCacheType to CACHE_ACCEL? [18:59:10] lol, installer [19:01:05] !debug [19:01:05] For information on debugging (including viewing errors), see http://www.mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://www.mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging [19:08:29] going away now [19:08:30] byr [19:08:33] bye [20:24:53] !del php7 [20:24:53] Deleting users is very messy and not recommended, because this breaks referential integrity in the database (they appear in many different tables like users, edit histories, recentchanges, preferences, etc). A safe solution is to block the users, and possibly rename them with . You can also try [20:25:12] !php7 del [20:25:13] Successfully removed php7 [20:40:21] the fact you shouldn't remove users is kinda..awful [20:40:33] Why? [20:41:34] that shouldn't break things [20:42:12] If they've got edits... What are we supposed to do with them? [20:43:37] I think the proper way is to create a trash user and then merge all unwanted accounts with it. [20:44:08] "proper" [20:44:42] ;-) [20:46:32] Maybe there should be a way to undo all traces the user has left, so that on deletion, referential integrity will not be broken as all refernces are gone. [20:46:59] Hmm, that would be even nicer [20:47:40] I had to close a wiki because there were 100 new accounts each day, all of which were spammers.