[01:04:44] anyone know a way to include a sort key based off numerical value vs text value? [01:11:43] What? [01:11:51] You mean a category sort key? [01:11:59] {{DEFAULTSORT:001}} should work fine. [01:21:57] Carmela: Im working with a variable length number, (IE 5,10,20,100) as sort keys and want to get the category page sorted by numeric value, not the first # in the string [01:21:58] You can add zero padding. [01:21:59] {{#padleft:}} or something. [01:22:16] thanks [02:45:56] Howdy, is there a way to exclude certain pages from a Semantic Mediawiki Concept? like by page name or any other property [04:45:54] prech: try asking in #semantic-mediawiki ? [13:44:51] hi, i have a category that has about 10,000 pages [13:45:17] and want to build a front end app with angularjs [13:45:54] so how can i get a list of all these pages in the category to show up in the app [13:46:29] using the mediawiki api? [13:47:25] anyone? [13:48:25] arnab: you should probably just ask your question [13:48:39] [14:45:59] so how can i get a list of all these pages in the category to show up in the app [13:48:41] valhallasw`cloud: ^^ [13:48:54] ah, I just missed that :-) [13:49:44] so how to do it? [13:50:30] arnab: https://en.wikipedia.org/w/api.php?action=query&list=categorymembers&cmtitle=Category:Physics [13:50:59] see https://en.wikipedia.org/w/api.php?action=help&recursivesubmodules=1#query+categorymembers for more details on how to use categorymembers [13:51:26] well, i was confused how to use the query continue? [13:51:33] coz there are 10,000 [13:51:45] and ajax requests cant be looped right [13:52:36] arnab: https://www.mediawiki.org/wiki/API:Query#Continuing_queries [13:55:27] valhallasw`cloud >> thx, i ll have to check that properly [13:55:41] also i was reading thru a list of api clients [13:55:52] and it says mw.api is shipped with mediawiki core? [13:56:05] where is mw.api used generally [13:56:17] and can it be useful in my case? [13:59:05] ? [14:00:48] arnab: no clue [14:02:38] oh ok np. thx anyways [15:56:37] hello Nemo_bis [15:56:55] I am not getting reviews on my patch [15:57:52] I want to proceed further [15:57:59] How should I? [16:22:37] Post a link here to try and drum up interest [16:24:03] patch set - https://gerrit.wikimedia.org/r/#/c/167018/ [16:27:52] oh, translate extension.. [16:28:18] Krenair: yeah [17:33:13] How to insert the text of one page (NOT a template) into an other page? [17:37:24] porton: just like any other template. Use the page name preceded by a color. For example, to transclude the [[Main Page]] use {{:Main Page}} [17:37:42] hello, I'm having trouble upgrading from mediawiki 1.21.3 to 1.22.13, I'm getting the following error upon upgrade - C:\wamp\www\includes\db\Database.php: Could not open "patch-indexes.sql". [17:38:42] i also tried upgrading to the latest mediawiki and I get the exact same error [17:39:05] Can I make a table right-to-left (the first cell should be at the right)? [17:39:55] http://i59.tinypic.com/acttsj.png [17:43:41] guest22: look at C:\wamp\www\maintenance\archives\patch-indexes.sql, it should be there [17:43:52] it is [17:44:05] check file permissions [17:44:13] it's on windows [17:44:59] windows filesystems has also file permissions [17:45:23] Vulpix: never seen though :d [17:45:33] file permissions on Windows [17:45:46] well, since Windows NT/Windows 2000 [17:46:21] who should have the permissions, I'm using wamp [17:46:44] i (admin) have full control regular users can read & execute [17:46:45] I guess everyone should have permission to read that file [17:46:50] system has full control ofc [17:47:50] also, wamp may be executing using a specific user account [17:48:11] how do i set it to use my account? [17:48:51] guest22: but the appropriate file exists? [17:48:56] yes [17:49:03] hm, strange [17:49:46] try https://answers.yahoo.com/question/index?qid=20081219034306AAE8WYt [17:50:53] guest22: if in doubt, try adding the special user "EVERYONE" read permissions on the maintenance directory [17:50:58] but aren't you able to run the update.php script with administrator privileges [17:54:56] okay, i gave group "everyone" permissions to read, read & execute directory maintenance, I checked that patch-indexes.sql had inherited these permissions, yet I still get the same error [17:55:41] I do not have experience with wamp though, only with xampp [17:56:48] :( I'd really like to upgrade my wiki [17:56:55] we understand [17:57:27] you do use wampserver? [17:57:36] yes [17:57:52] well, if you can't fix the file permissions, there is another method [17:57:58] sourcing the sql files with a mysql shell. [17:59:02] guest22: apparently, if you execute that patch-indexes.sql file manually on the database, the updater shouldn't try to run it again, so it will continue to the next step [17:59:28] need help on that, or do you want to try to fix the permissions? [17:59:43] what does that mean exactly [17:59:56] what vulpix said [18:00:18] i mean, how do I "execute that patch-indexes.sql file manually" [18:00:44] with the mysql shell or phpmyadmin. [18:01:00] how do I do it on pma? [18:01:49] open pma, select the wiki database, and you should find somewhere a link to execute a SQL query directly [18:02:02] are you logged in in pma and selected your wiki database? [18:02:09] yes [18:02:27] copy the text of the patch indexes file [18:03:23] in the toolbar above you'll see an option "SQL", click on that [18:04:18] #1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IF EXISTS /*$wgDBprefix*/links DROP INDEX l_from, ADD INDEX l_from (l_fr' at line 7 [18:04:40] paste the text there, and click on the startbutton somewhere at the right side. Please note that you first should make some changes to the code if you use a database table prefix [18:04:46] oh my bad [18:06:55] it still says that I have an error in syntax, yet I set the prefix [18:07:06] confirmed, looking. [18:08:10] try to remove the "if exists" part [18:08:12] and try again [18:09:35] Vulpix: would you have an idea in which version this indexes patch has been introduced? [18:10:22] from the code I saw a comment mentioning year 2003 [18:10:47] yeah [18:10:59] alter table if exists is illegal syntax. [18:11:38] ok a site says it isn't but it somehow blocks users from executing that sql. [18:12:25] Table 'databasename.mk_links' doesn't exist [18:12:46] indeed.. [18:13:05] that's the error i was given [18:13:06] and brokenlinks also doesn't. [18:13:25] also by checking the tables brokenlinks doesn't excist also [18:13:31] yes [18:13:59] irc doesn't scroll to the bottom automatically for some reason, when someone posts [18:14:18] in fact I wouldn't recommend it users, but would it be a good idea to skip that tables [18:15:17] i tried removing that part from the command, but then it found another error in recentchanges [18:15:17] guest22: try https://dpaste.de/5W4O [18:15:46] assuming mk is your dbprefix [18:16:02] #1061 - Duplicate key name 'rc_timestamp' [18:18:00] hm. [18:18:44] try to run the mediawiki update again, does it still asks for that file? [18:20:30] i have even more errors now [18:20:48] screenshot? [18:20:49] ill try to reimport the database [18:39:59] okay, apparantly my database was corrupted, upgrade successful after clean import, sorry for wasting your time [18:46:19] np guest22 [18:46:35] and be happy with the upgrade :) [19:28:22] hello, i updated my wiki from 1.21.* to 1.23.*, along with it came the new register/login pages, I have custom css on my wiki using monobook/common.css on mediawiki namespace. all of the pages display fine, except register/login pages, which are not affected by these css pages [19:30:09] known bug :( [19:31:01] what, so i cannot change the style on these pages without changing it directly from server? [19:32:12] guest22: https://www.mediawiki.org/wiki/Thread:Talk:MediaWiki_1.23/Changes_to_Common.css_and_Vector.css_don%E2%80%99t_affect_all_pages%2E [19:33:34] if you've customized your skin's CSS, it would be better to put your customizations on a RL module on the server, although of course it's not as easy to edit than a normal wiki page [19:47:03] are they planning on fixing it any time soon..? [19:49:21] it doesn't seem it will have a fix anytime soon [19:49:29] which is silly [19:58:44] i'm forced to refrain from upgrading the software until a fix is made [20:00:38] guest22: what about implementing a module for your CSS as explained on that page? [20:06:04] guest22: there is a pending patch and discussion about that going on now [20:06:40] guest22: Its a security issue that was discovered and patched [20:06:52] the discussion is going on? I think it's stuck right now [20:08:32] Vulpix: the last post was 21 hours ago [20:08:58] bug 71621? [20:09:06] given that its Friday/Saturday I expect it to cool off [20:09:50] Vulpix https://gerrit.wikimedia.org/r/#/c/165979/3 [20:10:00] let me get the email thread [20:10:42] ah, the patch, that's OK [20:11:09] Vulpix: https://lists.wikimedia.org/pipermail/wikitech-l/2014-November/079309.html [20:11:22] it was stuck a lot of time, I'm glad to see some progress on it :) [20:11:26] its an ongoing email thread [20:12:32] Vulpix: are you any good wiht lua? [20:13:52] no, I haven't touched that language yet :( [20:13:59] I'll have to learn it someday [20:14:31] Im looking for someone to write a basic module for me [20:14:52] should take less than 15 minutes for someone who knows the language [21:12:35] 10-4 [21:18:29] Mornin', I'm having trouble with account creation on a mediawiki instance I setup on an ubuntu server. [21:18:48] When I create a user account and "send temporary email" I can login with that user with the temporary password [21:19:00] when I try to submit the form to change the password however I get this error message: [21:19:06] "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." [21:19:20] I tried setting up session storage with memcache [21:19:25] not sure how to troubleshoot this. [21:23:28] do you even have a sql database configured on the web server? [21:26:37] Jehovahsays: Yes, mysql. [21:26:47] I already connected to it and verified that the mediawiki schema was creaed. [21:26:56] ok [21:27:12] Jehovahsays: I don't see any error messages in syslog or apache2/error.log [21:27:46] what is the link for your mediawiki [21:28:14] It's a private wiki for the internal use of a company. Do you mind if PM you the URL? [21:28:28] sure [21:29:06] Jehovahsays: I'll create an account for you so you can repeat the problem [21:29:32] ok [21:49:39] wkmanire_: can you examine your cookies to see of your getting a valid session? and if it matches whats in the database? [21:52:03] Betacommand: Yes, what table are the session cookies stored in? [21:52:19] user [21:52:59] table user.user_token [21:55:00] They are different [21:55:20] I logged in as my root user and then compared my_wiki_session value from the cookie to the user_token in the user table [21:55:23] And they're not the same. [21:55:58] How can that be? [21:56:12] user_token doesn't contain the session cookie [21:56:33] the session cookie is "stored" in the php session_save_path [21:56:37] I did try to setup memcache, but I disabled that and restarted the server. [21:56:46] ahh, I bet that's the problem. [21:56:48] usually as a filename, but other handlers are possible [21:57:11] I don't know that much about PHP, do I set that in php.ini? [21:57:43] Platonides: thanks, forgot where it was stored [22:00:58] do you know where the php.ini file is located on your ubuntu [22:01:48] Yeah [22:01:53] I have it open already [22:02:35] look for session_save_path [22:03:26] It's not defined in there [22:03:40] .http://php.net/manual/en/session.configuration.php#ini.session.save-path [22:03:43] I think I need to set this? [22:07:02] it will need to be the same as the one in your localsettings.php for mediawiki [22:10:02] when you complete this we will try to login again to see if it works [22:14:45] Yeha, no beans [22:16:22] do you still have memcached configured in LocalSettings.php? [22:16:27] that would override it [22:17:41] I disabled it [22:17:46] be right back [22:22:43] Ok, I got it. [22:23:14] Platonides, Jehovahsays, Betacommand, SPF|Cloud: This is what I had to do: http://www.mediawiki.org/wiki/Thread:Project:Support_desk/Session_Hijacking_error_after_Update_1.19.14 [22:23:26] Apparently there is some sort of regression in that particular form that hasn't been patched yet. [22:23:41] we are back [22:23:44] Applying the change to SpecialChangePassword.php suggested by AKlappe resolved the issue. [22:24:35] which version are you using? [22:25:13] if the field is named wrongly, it's no surprise that it isn't working [22:25:39] Platonides: What's the best way to check the version number? [22:25:50] Special:Version [22:25:52] I just installed mediawiki using the ubuntu package manager, so if the problem was already resolved the package maintainers are behind. [22:26:08] I wouldn't be surprised that they are [22:26:23] 1.19.14+dfsg-1 [22:26:28] I think ubuntu just repackages the debian mediawiki version [22:26:34] which isn't the latest one precisely [22:26:55] "This was a mistake in the backport to MW 1.19.14" [22:27:18] the fix was included in MW 1.19.15 [22:27:54] Debian packages :| [22:27:55] in fact, they could be including 1.19.21 [22:28:06] you should complain to Thorsten Glasser [22:28:13] wkmanire_: is that installed from a repository? [22:28:17] Yes. [22:28:24] !package [22:28:24] Many Linux distributions provide MediaWiki in a packaged format for that distro. These packages typically contain obsolete & unsupported versions of MediaWiki; they also like to move around & change files, & do other super-counterproductive things. You'll get the best support here if you install MediaWiki directly from one of our tarballs - https://www.mediawiki.org/ - or Git https://www.mediawiki.org/wiki/Download_from_Git [22:28:42] or you can download MediaWiki 1.23.6 from mediawiki.org [22:28:43] he he he, now you tell me. [22:28:52] wkmanire_: ^ [22:29:07] I was hoping for a turnkey solution to provisioning this server. [22:29:17] Just wanted to apt-get install and make a few conf file changes. [22:29:28] And it ended probably taking longer than just installing it manually. [22:29:29] not that mediawiki is hard to install... [22:29:30] wkmanire_: doing a checkout/tarball install is easy [22:29:50] Oh well, you live you learn. [22:29:53] Platonides /Betacommand: that completely misses the point of an LTS [22:29:53] wkmanire_: I installed mw in 15 minutes [22:29:54] :) [22:29:54] Thanks for the support everybody. [22:30:12] valhallasw`cloud, mediawiki also has LTS versions [22:30:13] valhallasw`cloud: 1.19 isnt LTS [22:30:17] installing from apt is sensible if you're looking for 'set up once now, never touch for the next 5 years' [22:30:40] I should probably go submit a bug report somewhere, if they're going to have the package on the repository it at the very least should not be broken. [22:30:41] valhallasw`cloud: however apt screws with file/setting placements [22:30:41] (at least, it should be, if the debian people do their job correctly) [22:30:43] and you don't know in advance if manually installing mediawiki is a breeze of painful [22:30:50] s/of/or/ [22:30:51] valhallasw`cloud: they dont [22:31:41] !lts [22:31:41] Current long-term support release is 1.23. The legacy lts is 1.19 and will be supported until May 2015. https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life [22:31:55] valhallasw`cloud: ^ [22:32:32] we are using windows 7 professional OS , keeps getting easier and easier. [22:32:43] Betacommand: where our LTS period is 3 years as opposed to ubuntu's 5 ;-) [22:33:12] Platonides: Yeah exactly. Go back to 2008 and setup a trac instance. [22:33:22] That's something you would think would be easy to setup right? [22:33:34] ha ha ha, I'm glad they have that on the package manager now. [22:33:42] valhallasw`cloud: semantics, you could compare that to Microsoft's 15 years of support for XP [22:34:22] Betacommand: no, it's not semantics. It's 'don't look back for 3 years' vs 'don't look back for 5 years' [22:34:38] but I'm off to bed [22:35:07] valhallasw`cloud: standard upkeep common sense is to do a review at LEAST once a year [22:35:41] Not looking at in 3-5 years is begging for problems [22:35:59] security issues at a minimum [22:36:31] we are always patching security problems [22:39:10] Jehovahsays: I know, especially with the recent flood of massive security holes that have been found [22:39:17] Hardbleed [22:39:27] patched [22:40:30] We invested in a business true id with EV SSL and the patched it [22:42:32] we just recently patched to fight spam bots using recaptcha and google login [22:45:04] we also made a simple extension to add web of trust ratings to all of the links on our mediawiki installation pages to add special features to our patrols. [22:45:27] Welp, screw it. [22:45:33] I've spent 10 minutes trying to figure out how to submit a bug report [22:45:37] It shouldn't take this much effort [22:45:44] what happened? [22:46:07] Nothing, just trying to submit a bug report to the package maintainers for mediawiki on ubuntu [22:48:11] Hey Jon, I figured out the issue. The session_save_path() was absolutely correct inside "LocalSettings.php" but it was set to some different value in "php.ini" inside php installation folder. I modified it there (inside php.ini) and now I am able to log into wiki :) Thanks for your reply :)