[01:14:32] anyway to enforce email authentication to edit without restricting anonymous edits? [01:15:22] Probably with the new authmanager stuff, yes [02:35:23] c: Sounds contradictory. [02:35:49] Esther: not when anonymous users can edit pages but can't create them [02:36:36] Hmm, I read "email authentication" as meaning "have a verified e-mail address." [02:36:48] That's but emailconfirmed, maybe you mean logging in with an e-mail address. [02:37:06] Requiring emailconfirmed and wanting to allow anonymous edits sounded contradictory. [02:37:39] The create and edit permissions are already separate (distinct) in MediaWiki. [02:37:50] So varying behavior on that should be fairly straightforward for most cases. [02:45:17] Esther: the problem is an account can instantly register without verification and create a spam page in not even 5 seconds. I've tried to use abusefilter as a deterrent but it doesn't stop everything [02:45:43] c: i like that idea [02:54:38] c: Can't you tie the create permission to emailconfirmed? [02:55:04] Or rather, you'd tie the create permission to autoconfirmed. And tie autoconfirmed to emailconfirmed? [02:55:12] Would that work? [02:58:26] i thought emailconfirmed was deprecated, i don't see it in anyone's implicit groups [03:56:29] !rights [03:56:30] For information on customizing user access, see < http://www.mediawiki.org/wiki/Help:User_rights >. For common examples of restricting access using both rights and extensions, see < http://www.mediawiki.org/wiki/Manual:Preventing_access >. [03:57:03] c: There's https://www.mediawiki.org/wiki/Manual:$wgEmailConfirmToEdit [03:57:48] c: And https://www.mediawiki.org/wiki/Manual:$wgAutopromote [03:58:16] https://www.mediawiki.org/wiki/Manual:Preventing_access says... [03:58:24] # Note for 1.13: emailconfirmed group and right were removed from default [03:58:24] # setup, if you want to use it, you'll have to re-enable it manually [03:58:29] Whatever that means. [06:18:44] Hi I am a developer for this year's Google Summer of Code [06:19:07] I want to extend Wiktionary's audio widget [06:19:40] to add recording and pronunciation evaluation functionality to it [06:20:17] I am looking for some initial guidance as to how to go about it. Thanks for any pointers. [06:22:51] Here's a snapshot of what I need [06:22:52] https://1.bp.blogspot.com/-RAEco12SX0w/WVkR6HTfDaI/AAAAAAAANQU/CDcD3zRLkV4inVf7bKaS7GIGmpk1tSjlwCLcBGAs/s1600/volmeter.png [09:51:48] I'm having a problem with parsoid timing out. I'm using the latest github build on Ubuntu. Can anyone help me out with that? [09:52:33] This seems to be the relevant error: Jul 10 04:02:45 serv0x00 parsoid[7339]: {"name":"parsoid","hostname":"serv0x00","pid":7500,"level":60,"err":{"message":"Config Request failure for \"http://joshuarosales.com/wiki/api.php\": Error: ETIMEDOUT","name":"lib/index.js","stack":"lib/index.js: Config Request failure for \"http://joshuarosales.com/wiki/api.php\": Error: ETIMEDOUT\n at [09:52:39] ApiRequest._requestCB (/var/www/html/wiki/services/parsoid/lib/mw/ApiRequest.js:415:15)\n at self.callback (/var/www/html/wiki/services/parsoid/node_modules/request/request.js:188:22)\n at emitOne (events.js:77:13)\n at Request.emit (events.js:169:7)\n at Request.onRequestError (/var/www/html/wiki/services/parsoid/node_modules/request/request.js:884:8)\n at emitOne (events.js:82:20)\n [09:52:45] at ClientRequest.emit (events.js:169:7)\n at Socket.socketErrorListener (_http_client.js:258:9)\n at emitOne (events.js:77:13)\n at Socket.emit (events.js:169:7)\n at null._onTimeout (/var/www/html/wiki/services/parsoid/lib/mw/ApiRequest.js:41:8)\n at Timer.listOnTimeout (timers.js:92:15)","levelPath":"fatal/request"},"msg":"Config Request failure for [09:52:50] \"http://joshuarosales.com/wiki/api.php\": Error: ETIMEDOUT","time":"2017-07-10T09:02:45.118Z","v":0} [10:40:28] hello, how can i put more menus to the sidebar where the mainpage/recent changes etc etc are? [11:47:10] is there a build service for packages placed in https://www.mediawiki.org/wiki/Download ? and if so, where can i find the script? [12:01:16] Is user "FlorianSW" usually online ? [12:01:35] I want to send a message to this person https://meta.wikimedia.org/wiki/User:Florianschmidtwelzow [12:09:59] they registered 3y ago and last authed to nickserv 2 weeks ago [12:10:08] see '/msg nickserv info floriansw' [12:11:47] thanks Svetlana [12:12:29] no worries, and thanks for coming by as well [13:01:44] I love mediawiki and everyone who developes it Svetlana :) [13:16:29] tried to set up local host to mediawiki i got core folder in local host but when i m opening iyt its showing help(); [13:16:58] can you guys help me with this? [13:26:29] Hi. I have taken care about some older wiki. There is problem. Some tags like but all of even change the internal editor to tinymce and these images are displayed properly in editor. But after saving the same. [14:23:35] Hi all, not sure if this is an apache issue or an issue related to the confirmaccount extension, but when a user uploads their cv to confirmaccount as a pdf, the link generated WILL save the PDF, but the file itself really wants to be saved as index.php. How do I fix this? [14:43:28] Even setting ForceType doesn't seem to do much good :| [14:53:20] Aw. Shucks. This appears to be extension related :( PHP Warning: call_user_func() expects parameter 1 to be a valid callback, cannot access protected method FSFileBackend::resetOutputBuffer() [15:16:40] How can I put a watermark on an article upon print? [15:17:07] I'm not very good with CSS and I don't remember the Special page for modifying print versions. [16:02:12] I have taken maintenance over some older wiki. As I see there is no support for TinyMCE or FCKeditor. If I want to edit some page there is everything in html code. And not allowed tags like markinfo: erm, are you talking about MediaWiki or DokuWiki? They're different products... if the software you use is DokuWiki, you need to refer to DokuWiki support, not MediaWiki [16:14:56] teward, I am talking about mediawiki. [16:16:45] I need to know if after upgrade of some old mediawiki, which used tinyMCE, is realy necessary to rewrite everything in dokuwiki format. [16:33:40] How can I put a watermark on an article upon print? [16:33:56] I'm not very good with CSS and I don't remember the Special page for modifying print versions. [16:38:41] markinfo: mediawiki markup is different from dokuwiki markup, which I think is causing some confusion here [16:39:27] a/wc [16:39:31] I'm pretty sure all the pages are the same though... are they rendering differently after the upgrade, or are you just taking about the editor? [16:39:32] whops, disregard that [16:40:18] Skizzerz, O.K. But this wiki was maintained with TinyMCE. Now was upgraded and everything is in html code. There is no way to migrate it? [16:43:27] you will need to be more precise [16:43:35] mediawiki markup is allowed to contain some html tags [16:43:40] Skizzerz, after upgrade some html tag are not displayed. Linke Skizzerz, both actually suported Editors WikiEditor and WikEd are working with mediawiki syntax only. [16:48:40] so I see two options; both require editing pages [16:49:03] first is to enable raw HTML mode; I do *not* recommend this on public wikis or wikis with untrusted editors, as it can cause security issues [16:49:17] you'll need to still wrap all page markup in [16:49:43] second is to just convert everything to wikitext, which is probably going to be the easiest. THere are various html to wikitext converters so you may be able to automate it [16:50:08] if you go the 2nd route, you can install the VisualEditor extension which gives a WYSIWG editor experience similar to the old tinymce/fkeditor [16:50:16] (however it works with wikitext instead of html) [16:51:10] oh, I guess option 3 is to move off of mediawiki into a CMS that supports html and just copy/paste page content into it [16:57:17] Skizerz. Hm well. Enable $wgRawHtml = true; and $myeditor = 'wikieditor'; old pages wrap into and for new pages use Mediawikisyntax. It seems to work. [18:10:15] How can I put a watermark on an article upon print? [18:15:21] MediaWiki:Print.css [18:36:22] Hullo, does anyone have any links to information/guides on developing on the MW API? I've had a good look through the MW docs, but can't find any information on modifying the API [18:36:53] Modifying it how? [18:38:24] Reedy: adding a new parameter for example [18:38:35] What do you mean by parameter? [18:38:38] At what level [18:38:42] A module? A query module? [18:38:53] A query parameter to a specific module? [18:40:44] TheresNoTime: you'll need to code the logic in PHP, are you aware of this? [18:41:17] and illogicness too! [18:41:35] Reedy: it'd be a module, am I just being daft and not finding the docs for adding modules to the API? o.O [18:41:56] just use existing code as an example [18:43:40] grep the code for a known module class, and you'll probably find a file that registers all api modules [18:43:44] Autoload the class, add to some specific variables [18:45:36] Ah, ApiMain.php - `List of available modules: action name => module class` [18:46:14] $wgAPIModules['shortname'] = 'PHPClassName'; [18:46:56] are you writing an extension or core patch, TheresNoTime ? [18:48:14] MaxSem: I guess it'd be a patch, I'm literally only just playing around with an idea from T170173, but given legoktm's latest comment I'm not expecting it to go anywhere [18:48:15] T170173: Simulate API calls - https://phabricator.wikimedia.org/T170173 [18:49:58] Shame, the idea sat well in my mind, sort of like the -WhatIf command for ps [18:54:32] it would probably require a new global parameter, and then each module that can perform changes check the presence of this parameter to return a simulated response instead [18:55:00] still, working on this would require/benefit from having those responses documented anyway :) [18:55:40] and may not be reliable on extensions uness someone updates them [18:57:10] Neutering SQL queries that use the api layers would be easy [18:57:22] Beyond that... It's a rabbit hole :) [20:11:22] MaxSem: thank you. [20:14:53] MaxSem: would you be able to help me with the CSS for the watermark? I'm not good with CSS... [20:15:06] This is the CSS I have, and I'm not sure if this is adequate. [20:15:10]
REFERENCE ONLY
[20:33:01] cwre, neither I know CSS. I, however, know enough to tell you that what you posted was HTML, not CSS:P [20:37:35] Hi, i have knowledge of movies and want to improve information about the movies and celebrities, so how can i get started [20:37:55] MaxSem: web things are scary. [20:38:28] Tanveer: Create an account and start editing? [20:39:31] I guess he got what he wanted. [20:50:17] MaxSem: did you got to run cleanupTitles? [20:50:54] it crashed, trying to figure it out [20:51:46] MaxSem: I ***think*** that we don't use cleanupTitles.php anymore [20:51:59] suggestions? [20:52:02] could you run namespaceDupes dry-run and see if there's any conflict? [20:52:19] there are several options to run that script [20:53:07] https://www.mediawiki.org/wiki/Manual:NamespaceDupes.php [20:55:15] was done a billion times. it doesn't and not supposed to fix these kind of problems [20:57:39] as far as I know, it is the only script it is used now, but I'm not an expert so I might be wrong [21:03:15] This watermark garbage is going to be the death of me. [21:58:34] cwre: You prolly want absolute or relative positioning. [21:58:36] For a watermark. [21:58:44] Also, you can use a search engine to find plenty of examples, I imagine. [21:58:54] Not really that explain it. [21:59:25] Everything I've found is just SO and I don't understand what I need to put into Print.css and if I need to put any html into the articles. [22:03:28] Depends what you're trying to do. [22:03:41] Do you want just disclaimer text at the bottom or like a big background image? [22:09:32] cwre: You could probably just slip that html snippet into MediaWiki:Copyright - it is unfortunately a raw html message [22:10:36] If you need to inject HTML. [22:10:51] I want none of this. [22:10:58] For my job, I need a background image. [22:11:07] Then you probably don't need to inject HTML. [22:11:13] You can just use CSS, probably. [22:11:14] Oh, you want a background image for the entire site [22:11:16] And attach to an existing element. [22:11:17] ? [22:11:24] For printing only, I think? [22:11:38] We sort of do this on mediawiki.org for the Help namespace. [22:11:49] With the public domain background. [22:12:13] Yeah, printing only. [22:12:25] You're familiar with ?printable=yes ? [22:12:30] You can see the print output with that URL parameter. [22:12:49] Do browsers even print background images? [22:13:02] I'm not, actually. [22:13:12] they didn't back in the days, but maybe they do with css [22:13:21] * bawolff 's knowledge is clearly out of date [22:14:00] cwre: https://test.wikipedia.org/wiki/Main%20Page?printable=yes is an example. [22:15:45] So, given my lack of CSS knowledge... How can I do this with a background image? [22:18:30] cwre: Do you see the crossed-out C at https://test.wikipedia.org/wiki/Main%20Page?printable=yes ? [22:18:38] In the background? [22:18:43] You may need to refresh, but it's there now. [22:18:48] Stupid cache took a few minutes to clear. [22:19:08] I don't... [22:19:18] Did you refresh? [22:19:26] ctrl-shift-R [22:19:36] Got it [22:19:42] Just cleared [22:19:45] Cool. [22:19:50] So you could do something like that, maybe. [22:19:51] But! [22:20:02] The catch is that browsers typically disable background images by default when printing. [22:20:05] :-) [22:20:11] UGH [22:20:54] How do I find the CSS for this in the page? I've got dev console open, I can't just mouse over it. [22:20:56] :( [22:21:13] So like Chrome has "Background graphics" checkbox when priting. [22:21:15] printing [22:21:20] https://test.wikipedia.org/wiki/Main%20Page?printable=yes is just regular HTML. [22:21:24] You can inspect it. [22:21:35] https://test.wikipedia.org/wiki/MediaWiki:Print.css is where I made the edit. [22:21:48] Which bawolff or someone should revert in a few minutes after we're finished testing. [22:21:58] Since we're not really releasing all those page into the public domain. [22:23:32] Hmmm.. [22:23:49] I put that exact same css into my mediawiki [22:24:29] You may need to wait a minute or two. [22:24:36] And my ?printable=yes isn't changing the output [22:25:15] It's still got CSS in the page. [22:25:24] https://test.wikipedia.org/w/load.php?debug=false&lang=en&modules=site.styles&only=styles&printable=1&skin=monobook [22:25:29] There's a URL similar to that. [22:25:36] That https://test.wikipedia.org/wiki/Main%20Page?printable=yes is loading. [22:25:40] You need to make sure that URL has your new CSS. [22:25:54] And if you're using a custom skin (not Vector or Monobook), your CSS selector may be wrong. [22:25:57] Gotta go. [22:26:15] Darn.... [22:26:20] Okay, thanks for the help!