[00:07:23] enabling this VisualEditor with 1.23 is impossible [00:10:11] i got the Error "Error loading data from server: parsoidserver-http-curl-error: couldn't connect to host. Would you like to retry?" [00:10:15] any idea? [00:18:08] Sia-: That means you haven't set up Parsoid correctly [00:18:11] Or it may not be running [00:21:11] RoanKattouw, is enabled but can't loaded it [00:21:37] Is Parsoid running? On what URL? Can you point your browser to that URL? [00:21:44] (Something like http://localhost:8000/ ) [00:22:06] chawg.org/wiki [00:22:57] Sia-: OK let me put it this way, what is $wgVisualEditorParsoidURL set to in your settings? [00:23:17] yes to loacalhost [00:24:24] localhost:8000 ? Or :8142? Or something else? [00:25:40] i've tried both because on chawg.org running debian [00:25:47] Oh OK [00:26:12] If you click on either of these links: http://localhost:8000/ http://localhost:8142/ does either of them give you a Parsoid welcome page? [00:26:37] i get the localhost from my machine note my server [00:26:49] Oh it's your server, right [00:26:50] server is in France not at home [00:26:51] OK [00:27:11] Try running the following on the server's command line: [00:27:13] wget -O- http://localhost:8142 [00:27:16] Then try again with 8000 [00:27:29] For at least one you will see an error like Connecting to localhost (localhost)|127.0.0.1|:8142... failed: Connection refused. [00:27:42] ok [00:27:43] But hopefully for one of them you'll get a long response with HTML tags in it [00:29:36] If both of them fail in exactly the same way, then most likely Parsoid isn't running [00:32:24] RoanKattouw, http://pastie.org/9775231 [00:32:37] OK, so probably Parsoid isn't running [00:33:31] i'm using mediawiki 1.23.7 and as mediawiki howto page, have enabled the Pasoid extension also [00:33:35] OK [00:33:42] But did you install the Parsoid Debian package? [00:33:47] https://www.mediawiki.org/wiki/Parsoid/Setup [00:34:12] chawg.org/wiki/Special:Version [00:35:11] You should follow the instructions at https://www.mediawiki.org/wiki/Parsoid/Setup#Ubuntu_.2F_Debian_on_amd64 if you haven't already [00:35:31] ok [00:35:44] i found that if your /etc/hosts file does not have a '127.0.0.1 domain.name.used.for.parsoid' visual editor will fail. also, for parsoid, make sure your firewall is not blocking connections [00:36:27] ok [00:36:34] hl3fx: Good to know. Could you add those bits of information to the documentation on mediawiki.org, perhaps? [00:36:41] Maybe in the troubleshooting section [00:36:55] i actually created a full installation procedure, very in depth... since it took me so long to figure it out. [00:37:12] it's on a private wiki, right now. i will add it to a public wiki tonight [00:37:12] RoanKattouw, then user with shared hosting, should forget this VirsualEditor, right [00:37:27] with shared hosting, yes. it would be sooo hard [00:37:40] There are alternative setup instructions that don't require root [00:37:47] getting a vps is easy and cheap though [00:37:51] That too [00:38:03] $3/month typically [00:38:13] yes, get a vps. i use linode, but atlantic.net has $5/mo that would work as well [00:38:17] example: http://www.ovh.com/us/vps/ [00:38:24] If you want to, you can do https://www.mediawiki.org/wiki/Parsoid/Setup#Manual_installation_on_Linux_or_Mac_OS_X instead and that lets you set things up locally without root [00:38:28] gwicke, vps server is not a kindergarten, to run all this stuff [00:38:29] Even on shared hosting [00:38:54] It's just that those instructions are more complicated so we don't point people to them unless we have to [00:38:59] Sia-: in many ways it's easier than shared hosting, as you get to use proper packages [00:39:16] apt-get install parsoid instead of all this manual installation stuff [00:39:17] thanks for the tip gwicke, ovh.com* [00:39:44] RoanKattouw, ok thanks because iøm afraid to install even contrib repos in my server [00:39:57] Sure, yeah [00:40:01] gwicke, hehehe OVH is sick [00:40:10] I am actually more familiar with the manual instructions because that's what I did [00:40:34] i was with them almost, 2 years. just stupid company ever [00:40:38] I have used OVH in the past, worked well for me then [00:40:43] The manual instructions are also good for VisualEditor developers :) [00:41:23] yeah, for development packages are less ideal [00:43:04] RoanKattouw, where should i update any info for troubleshooting VisualEditor (as you mentioned) [00:43:15] can you just link me [00:43:23] Probably https://www.mediawiki.org/wiki/Parsoid/Troubleshooting [00:43:39] thanks [00:44:41] RoanKattouw, this "git clone https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid" where should i put to get working, that just Persoid package [00:45:01] Sia-: Any directory that you own is fine [00:45:08] It can literally be anyhwere [00:45:28] ok how to link to Parsoid ? [00:45:37] in Localsetting.php [00:48:32] $wgVisualEditorParsoidURL = 'http://localhost:8000'; [00:48:44] Also check that that wget thing from before now works [00:48:56] (once you have finished installing Parsoid and have started it) [00:49:44] $wgVisualEditorParsoidURL = 'http://localhost:8000' [00:49:59] is added and doesn't change anything [00:50:39] where can i tell in LocalSettings.php to load Parsoid manually? [00:52:00] RoanKattouw, http://pastie.org/9775253 [00:52:04] is the same [00:52:50] Did you follow the instructions all the way through? [00:53:13] You also have to follow "Nodejs", "JS dependencies", "Configuration" and "Run the serfver" [00:53:16] -f [00:53:22] which one, you linked 10 links [00:53:28] Sorry [00:53:32] https://www.mediawiki.org/wiki/Parsoid/Setup#Manual_installation_on_Linux_or_Mac_OS_X [00:53:36] The first subsection is "Get the Parsoid code" [00:53:49] But you also have to do "Nodejs", "JS dependencies", "Configuration" and "Run the server" [00:54:14] And once you've got everything working you should do "Starting the Parsoid service automatically" as well [00:54:49] NodeJS need root as you see in that page [00:54:55] sudo apt-get ---- [00:56:39] argh right [00:56:44] Unless nodejs is installed already [00:57:04] You can also install nodejs locally [00:57:11] There are instructions for that on the nodejs web site [00:57:23] But it's worth running node --version and nodejs --version to see if it's already installed [00:58:20] RoanKattouw, thanks anyway i tried before, isn't working this way. [00:58:53] i'll skip this visual editor, until get stable and worked version. as i see google is full with issues [00:59:21] Well if you don't have root access it's never going to be easy [00:59:36] Waiting for a stable/better version isn't going to make the installation process much easier [00:59:50] * gwicke nods; those VPS's are really fun ;) [00:59:52] i have root access even with root access doesn't work i've posted you the [01:00:55] Well, you could use your root access to install nodejs, and then it would work [01:00:55] RoanKattouw, the installation is Buggy [01:01:00] How is the installation buggy? [01:01:10] What did you do from the instructions that didn't behave as it should have? [01:01:24] no i don't install JS or any non supported package from debian repos [01:01:30] Well [01:01:49] If you refuse to do things that the instructions tell you to do, then it won't work [01:02:00] no that not true [01:02:06] the installation is Buggy [01:02:12] You need nodejs in order to use VisualEditor, that is true now and it will be true forever [01:02:22] take a look in Talk page from Visual studio [01:02:33] even with VPS and root not working [01:03:16] Are you talking about the "not working for logged users" thread? [01:03:27] Because at the end that person says "This error occurs after enable the extension "BetaFeatures". Without it I have not this error and VE work for logged user." [01:04:26] if somebody survive the mine field, it doesn't mean the minefield doesn't exist. sorry but is Buggy Editor [01:04:56] if for you working, doesn't mean also is working perfect [01:06:30] Yeah the installation process is complicated and people run into problems [01:07:08] Most of the questions we get are people not following the instructions correctly [01:07:13] Which probably means they're not clear enough [01:07:15] IF you have [01:07:24] If you have specific suggestions for improving the instructions I'd love to hear them [01:09:24] you know I tested my action=visualeditoredit changes with no parsoid installed [01:09:33] haha [01:09:38] the method is probably not for everyone though [01:09:40] Pointed it to production? [01:09:47] And faked local oldids? [01:10:12] I've done that before to test experimental VE code against specific buggy pages on enwiki [01:11:08] Or did you just mock a service on localhost:8000? [01:11:17] http://paste.tstarling.com/p/FVPPVr.html [01:11:24] LOL [01:11:37] James_F is laughing uncontrollably right now [01:27:33] TimStarling: Good job [01:27:45] gwicke is kicking himself thinking "it's so SIMPLE" [01:29:25] ;) [01:41:48] is there a way to make a single page public on a private wiki? [01:42:23] i suppose i could google it. i have read a bunch on it all already, i just have not decided what i could use yet [01:42:42] and, i understand that it's not what a wiki is intended for, bla bla bla. [01:42:43] hl3fx: There's a whitelist read variable, yes. [01:42:49] oh, ok cool [01:42:53] i think i saw that before actually [01:42:57] The Main Page is readable by all by default. [01:42:59] As is Special:UserLogin. [01:43:07] Though I think the latter is hardcoded. [01:43:13] But you can specify an additional page. [01:43:31] yay, thanks. i'll check it out [01:48:01] can you see this page? http://wiki.storm5.com/w/Mediawiki_with_VisualEdtitor_Extension_Installation_on_Ubuntu_14.04 [01:49:39] i made it as i was creating a new wiki for a client, so hopefully it's accurate. i have not tested it yet. [02:50:11] !wg ReadWhitelist [02:50:11] https://www.mediawiki.org/wiki/Manual:%24wgReadWhitelist [02:50:15] hl3fx: ---^^ [02:51:54] i'm trying to install 1.24.0 with the installer, and at the step "Options" it's supposed to detect the skins in my skins folder [02:51:59] but it's saying it can't find any [02:52:44] oh, i already figured it out. i posted the link above of the tutorial i wrote. it should be working [02:53:17] i had to white list that, and the discussions for that [02:58:57] also, it seems to be setting $wgDBmysql5 = true; [02:59:03] when the manual page seems to say it should be false [03:07:06] hello! I am using mediawiki-vagrant for development purpose [03:07:30] There's a slight trouble I face every time I run vagrant up [03:07:50] It won't set up the environment if there's no internet connection [03:08:26] Is that a necessity or is vagrant up supposed to run even without an internet connection? [03:08:38] To whoever's on: What would you consider the difference between a pain point and a bug? [03:09:47] My initial thoughts are that a pain point might be something that works but it very difficult to use, while a bug is something that doesn't work at all [03:25:34] aaronbeaty123, that makes sense, I'd pretty much agree [03:26:40] Evan_M: Thanks! [03:32:26] also, doesn't seem like the installer is giving the user ID it creates the proper authorizations to the database it creates [04:22:43] Hello! I am new here. I want to contribute to Mediawiki. [04:23:26] May anyone please guide me? [04:45:07] Hi everyone! I am trying to install MediaWiki-Vagrant using instructions in https://www.mediawiki.org/wiki/MediaWiki-Vagrant but on executing command setup.bat "Failed to execute command vagrant plugin list" error occurs. Need help to resolve this issue . [04:47:52] phoenix303: what happens if you run 'vagrant plugin list'? [04:50:16] I have not run vagrant plugin list [04:51:04] can you try? [04:52:25] How should i run it? [04:53:39] do you know how to use the command prompt? ('cmd.exe') [04:53:56] yes [04:55:24] what is the command to give? "vagrant plugin install" ? [04:56:16] yes [04:56:59] It show "Failed to find vagrant!" [05:14:32] hi! [05:15:01] can i directly use the git clone commands to clone any repo in vagrant/mediawiki ? [05:15:28] or is it meant only for core/ [05:15:29] ? [07:13:15] hi, could someone please help me with vagrant? [07:16:32] i have the local setup running on one branch that i once created for submitting a bug [07:16:41] whereas for the master branch, the screen displays an error "Class undefined: MWLogger" [07:22:43] can i get some help on recreating this infobox? [07:22:44] http://hdm.wikia.com/wiki/Template:Individual_infobox [07:31:20] please [10:54:29] hi@example.com is becoming increasingly common, I'll keep it mind for next time I email sysadmins of ancient MediaWiki releases ;) [11:06:48] Hi, can someone tell me, how i can edit the Email-Templates sent to mediawiki users? I found: "MediaWiki:Confirmemail_body" but there has to be more ;-) [11:09:33] hello, I have a very simple problem but cannot get to solve it: I want the domain name in the URL shown, not the servername. I can access the mediawiki with http://mywiki.domain.com, but the url changes to http://servername/mediawiki/.... [11:10:19] my sites-enabled/mediawiki: ServerName mywiki.domain.com DocumentRoot /var/www/mediawiki. all the rest unchanged [11:10:48] my LocalSettings.php: $wgServer="http://servername"; (if I change to domain name I cannot access the wiki any more [11:11:14] I tried aliases in my apache config but this didn't change anything [11:49:02] did you reload apache [12:03:26] hello zuzak, yes of course I did [13:00:15] hello [13:00:34] how can I include a css with @font-face in my skin, if I'd like to use html('headelement') ? [14:24:30] ;< [15:20:03] anyone here that could help me out with recording from a kinect model 1414 im using ubuntu 14.04 and im just new to opencv and ubuntu. Just need it for my project, any help would mean a lot thank you [15:21:00] anyone please? im having trouble with libusb.h not being found by freenect.hpp :( [15:43:37] Wow, what a crazy case of wrong channel. [15:44:16] <^d> srsly. [16:43:15] Does someone here have an example modsec chain that will prevent brute force attempts on Special:UserLogin [16:52:36] Is there any way to insert a multiline
 or  block in the middle of a numbered list? I keep getting my second item labeled as '1'.
[16:53:34] 	 ad0nis: only if you use HTML syntax for the entire list. 
  1. Item 1
  2. Item 2
  3. code block
[16:54:54] MatmaRex: Thank you for that work-around. Any chance that'll be simpler in a future version? It seems that code blocks in a numbered list should be something a lot of people would use - like almost any code-related tutorial... [16:55:21] no idea. filing a feature request definitely won't hurt. :) [16:55:22] !newbug [16:55:22] https://phabricator.wikimedia.org/maniphest/task/create/ [16:56:27] ad0nis: there's a bug for that: https://phabricator.wikimedia.org/T3581 [16:57:37] reported back in 2005, so don't expect a fix anytime soon :) [16:57:52] maybe for MediaWiki 2.0 :D [16:58:03] Vulpix: Thank you. [17:03:45] MatmaRex: The
  • method you gave gives me a bullet-pointed list - I am aiming for numbered steps... [17:04:03] ad0nis: use the
      tag around the list [17:05:15] MatmaRex: That did it. Thank you! [17:05:32] :) [17:05:36] I can't believe how much HTML I've forgotten - I should have known that. [17:09:46] Just a thought for that bug - Perhaps numbered lists (lines starting with #) shouldn't be terminated by a single newline? - Perhaps you should need a second newline to start that second list - this would be much more intuitive, and would also simultaneously fix the usability issue of having to use "# Step 2: Do the Needful.
      [[File:diagram.png]]" to keep pictures from breaking lists, and they could be naturally added between steps. [17:10:53] Just my $0.02 after having to spend more time trying to figure out how to mark up my steps than I did creating the tutorial in the first place. [17:12:32] that would probably not be done, since it could potentially break a lot of existing pages [17:15:56] As you joked earlier, perhaps it could be a Version 2.0 sort of thing? Your old syntax will work up until the last version of 1 that's released, but 2.0 will support our new "sane syntax". [17:16:32] XD [17:16:51] Anyway. Sorry for all the gripes. I really do appreciate the quick answers to my questions. [17:17:06] Have a good one. [17:23:47] !2.0 [17:23:47] No, seriously, 2.0. Have a tracking bug: https://phabricator.wikimedia.org/T72000 [17:23:58] wm-bot troll [17:30:06] https://www.mediawiki.org/wiki/Future [18:27:01] hello [18:27:02] o/ [18:27:19] does anyone have an example of a mediawiki apache configuration file for debian/ubuntu? [18:29:30] aelevadoan: it depends on what do you need to configure. You can perfectly put all the contents in htdocs and not configure anything in apache [18:30:20] but i want the configuration file [18:31:28] Vulpix: [18:32:01] what configuration file? httpd.conf? [18:32:24] NO [18:32:28] Sorry [18:32:31] caps lock got stuck [18:32:36] I mean the mediawiki.conf [18:32:45] in sites-available [18:35:59] I don't have that information, sorry. Maybe see if there's an existing example configuration file, or a configuration for anything else and copy it, changing the directory as needed [18:36:53] Vulpix: I cant find an example configuration file on the internet [18:37:15] I mean in your sites-available [18:37:44] i did that [18:37:50] but i need a more specific one [18:38:00] because its giving me an error when I try to acces the wiki [18:39:06] oh, please, say what error are you getting [18:39:13] !xy [18:39:13] The XY problem is asking about your attempted *solution* rather than your *actual problem*. http://meta.stackoverflow.com/a/66378 [18:45:25] that's such a ridiculous response [18:56:49] James_F|Away: dr0ptp4kt: do you knw how to configure mediawiki with apache on a ubuntu? [18:58:31] aelevadoan: yes. simplest if doing your own local testing is to use MediaWiki-Vagrant, though. what's up? [18:59:35] im getting an error to access to localhost/mediawiki dr0ptp4kt [19:00:10] i have mediawiki in /var/www [19:01:48] i get a 404 not found error [19:03:15] dr0ptp4kt: i have a mediawiki.conf file in sites-available [19:03:25] i see a lot alias definitions [19:03:34] in the apache2.conf file [19:04:22] aelevadoan: could you pastebin your mediawiki.conf? [19:04:47] ok [19:04:48] aelevadoan: yeah, a lot of things that can go askew there. had a chance to look at https://www.mediawiki.org/wiki/Manual:Running_MediaWiki_on_Ubuntu ? if you're trying to test out local stuff, i would maybe consider skipping the setup hassles and instead use https://www.mediawiki.org/wiki/MediaWiki-Vagrant [19:06:02] aelevadoan: alsowhat Vulpix said. [19:06:11] Vulpix: dr0ptp4kt: http://pastebin.com/9A97DfxB [19:07:12] dr0ptp4kt: is it easier to use? [19:07:58] aelevadoan: i think it's easier to use, particularly for developing stuff on mediawiki core and on extensions. [19:08:33] aelevadoan: you have /var/www/mediawiki/mediawiki-1.24.0/ in RewriteRule, but /var/www/mediawiki/mediawiki-1.0.24.0 in everything else (look at the version number) [19:08:37] aelevadoan: maybe try changing "aelevadoan: try pointing ServerName wiki.yourdomain.com to "ServerName wiki.yourdomain.com" to "ServerName localhost", and then go and access http://localhost after doing a sudo apachectl restart [19:08:37] Im not going to develop [19:08:55] Vulpix: thanks [19:09:07] k [19:10:18] if all your sites are in localhost, I don't think you should use virtual hosts at all [19:11:15] well, unless you use something like testwiki.localdomain.com and add an entry in /etc/hosts pointing testwiki.localdomain.com to 127.0.0.1 for example (that's what I use for testing) [19:11:52] Vulpix: do you suggest I outrule virtual host? [19:13:41] Vulpix: dr0ptp4kt: I changed the servername to local host [19:13:47] and it hasnt changed anything [19:13:53] it still gives me 404 [19:14:05] you could unpack all files directly in the root public directory of apache, no need to configure more things [19:14:33] in var/www/html? [19:14:41] Vulpix: [19:16:11] in ubuntu I don't know. Googling a bit some people point at /var/www [19:33:21] aelevadoan: gotta drop to go on a videoconference, but feel free to email me if you'd like to setup a time to troubleshoot on Skype or Google Hangouts. i do recommend trying that mediawiki-vagrant stuff. it tends to "just work". one challenge with the manual setup in https://www.mediawiki.org/wiki/Manual:Running_MediaWiki_on_Ubuntu or more generally, https://www.mediawiki.org/wiki/Manual:Installing_MediaWiki is that the instructions need to be [19:33:22] followed very carefully. and even then you gotta sometimes adjust for your particular machine's setup. hence why i like mediawiki-vagrant - sometimes you gotta destroy a virtual machine and startover, but not so many configuration differences due its design of having everything built in. [19:33:32] i'm adam baso in real life - find me on wikimediafoundation.org [19:33:35] gotta go [19:52:14] When writing a custom mediawiki skin, is it possible to disable default css? [19:52:32] mediawiki loads some css rules for my site which I don't want, for example the a:visited{} rule [19:53:04] usually yes [19:53:05] why not override it in your skin's CSS? [19:53:48] samu: your skin's code probably loads some of the mediawiki.skinning.* modules, which implement these kinds of things - just don't load them :) [19:54:13] MatmaRex: yeah, I guessed that, I just don't know where to look for it [19:54:42] oh, wait, I think I got it [19:54:50] now that I grepped for mediawiki.skinning, let's try that. [19:56:08] that was it. I didn't know what was mediawiki.skinning.interface for. Thanks ;) [20:00:43] MatmaRex: just one last question - does the same apply for javascript? [20:01:29] um, no, generally you can't kill mediawiki's javascript from a skin. [20:01:58] well, ok. that's fine, because my javascript doesn't really interfere with it [20:02:28] but I'm asking, because I've added bootstrap javascript to the 'scripts' array, but It does not get loaded. [20:21:32] Ho ho ho guys! [20:23:51] Is it correct that $wgValidSkinNames is not used anymore? [20:25:29] I am asking, because it at least does no longer seem to contain the vector skin in MediaWiki 1.24... [20:26:28] Skins aren't shipped by default (if you haven't noticed) [20:26:40] So it won't have been updated... [20:28:09] So ... are you saying that it _should_ add itself to that array? [20:29:36] Vector has its configuration Vector.php, where such a line would fit nicely (and where it would also be included, when the skin gets included with require_once().) [20:32:16] Joergi: it can be used by a skin, but doesn't have to [20:32:27] Joergi: you should use Skin::getSkinNames() to get a link of installed skins [20:33:02] MatmaRex: So if it does not contain all skins, what is this variable good for? [20:33:24] um [20:33:37] it can be used to register a skin [20:33:44] that's all it's good for [20:33:55] it's not good for getting a list of all registered skins, since there are other ways to register one [20:34:00] (and there have always been) [20:34:22] So it also doesn't make sense to use it to register a skin. [20:34:26] So... [20:34:59] It should either contain a _complete_ list or it should be deprecated? [20:35:01] "and there have always been" -> not in prehistoric days [20:35:23] Platonides: but these are past. [20:47:29] MatmaRex: Nevermind, thanks for the hint! [20:47:59] Platonides: even in prehistoric days [20:48:09] Platonides: skin autodiscovery predates that configuration option, even [21:16:11] what's the best way to redirect domain.com to domain.com/wiki? i tried a rewrite rule in my Apache conf file, but it broke the path to my skins [21:44:55] matthewburton: Did you find https://www.mediawiki.org/wiki/Manual:Short_URL in the meanwhile? [21:45:59] no, i switched to Redirect, which caused an infinite loop, which i then fixed