[08:57:51] Hi. I just tried to insert a link in a table (i.e. [example.com Example]) and it just displays the raw text instead of a link.. [09:05:50] Nevermind, probably just a job problem [15:32:23] Fun on shared hosting to install MediaWiki 1.31 [15:32:23] 17.27 < jrwr> you should see the crazy I had to do to get this to run, the native version of PHP on the machine is 5.2 [15:32:27] 17.28 < jrwr> I had to static compile php7.2 and configure using htaccess a new cgi handler [15:53:22] Nemo_bis: Easy solution: don't use shared hosting. ^_^ [15:53:38] A private virtual machine with root access is cheaper. [16:05:28] Sure, I'm not recommending anything :) [20:13:33] hi. I'm trying to understand an API error I'm getting. Is this the right channel to ask about that? [20:42:02] ehuelsmann: sure [20:42:42] it's best if you state as much detail as possible (although please use a pastebin if things are going to take up a lot of lines so the anti-spam bot doesn't ban you) [20:43:01] someone who knows the answer can then get back to you [20:43:15] saves a bunch of time wasted in back-and-forth if there's nobody around right at the moment :) [20:45:28] Skizzerz: whats the best way to have a javascript modify the frontpage of the wiki? mw.load? [20:46:34] what are you trying to accomplish? [20:48:27] like it came to my mind [20:48:38] having like snowflakes on the frontpage [20:48:38] lol [20:50:11] biberao: just put it in MediaWiki:Common.js or Skinname.js (e.g. Vector.js) [20:50:28] you'll want to wrap it in $() or something so it runs on domready instead of immediately [20:50:59] i see [20:51:09] when to use mw.load? [20:51:33] and i again can i also mess with the frontpage elements by using common.js or skin.js? [20:52:20] use mw.load when you need APIs provided by resourceloader modules [20:52:39] ok will read thanks. [20:52:48] the only thing you can't mess with in common.js is the login/registration page [20:52:54] and other security-sensitive pages [20:53:02] i see [20:53:09] then where can i mess with that [20:53:12] extensions [20:53:14] through php? [20:53:35] but think really hard before you do [20:53:43] you may introduce security vulnerabilities with your modifications [20:55:39] ok [20:55:41] thanks [20:55:44] just learning :D [20:55:54] im into skinning and maybe an extension later [21:06:19] Skizzerz: stupid question if wanted to use jquery/js i need to add an element if a did [21:06:23] Skizzerz: stupid question if wanted to use jquery/js i need to add an element if a div or whatever [21:08:37] consult the documentation for the libraries you wish to use to see how they can be used [21:09:44] also [21:09:58] whats the best wy to add div or other elements on wiki pages [21:09:58] ? [21:10:13] just add the element and have a class and done? [21:46:31] Skizzerz: in summary, I'm trying to update the release number and date on the LedgerSMB page (https://en.wikipedia.org/wiki/LedgerSMB); to do that, I have a Perl script (https://github.com/ledgersmb/ledgersmb-release-tools/blob/master/notify/notification-helpers/release-wikipedia.pl) which uses the API (through MediaWiki::API) [21:47:01] it logs in, retrieves the current content, updates the release number (with a regex) and then pushes the new content back into the wiki. [21:49:49] Skizzerz: All requests proceed correctly, until the edit/write action takes place, at which point the response says "blocked". The block suggests that the API thinks the session isn't logged it. [21:49:57] in* [21:50:12] Skizzerz: I'll upload the logs to a pastebin. [21:53:37] Skizzerz: https://pastebin.com/tfZYtFVH [21:53:46] that's the transcript of the session. [21:54:04] I think the problem is likely in which tokens get used when. [22:40:52] ehuelsmann: well for starters, you should really be using a token from Special:BotPasswords and the bot login mechanism instead of action=login [22:41:21] ehuelsmann: second, it means the IP you're connecting from is blocked. Looking up the block, it is *not* set to "anonymous users only", so it'll hit logged in accounts editing under that IP as well [22:41:38] https://en.wikipedia.org/wiki/Special:BlockList?wpTarget=%238717087&limit=50&wpFormIdentifier=blocklist [22:42:03] Skizzerz: ok. thanks! [22:42:30] Skizzerz: Then the second is most likely the actual problem I'm running into now. [22:42:36] yes [22:42:53] Skizzerz: what is the name of the mechanism that the library should be using (for bots)? [22:42:54] but the first will be a problem in the near future as well [22:43:13] ok. but first things first :-) [22:43:32] action=login with a token from Special:BotPasswords [22:43:45] (as opposed to the actual user account's password) [22:44:15] action=clientlogin is meant for use with the user account's password, and is not meant for bots as it could feature interactive steps such as 2-factor auth [22:44:34] ok. I understand. thanks. [22:51:06] Skizzerz: I've sent a request to stewards@ to help me with the block to start with. [22:51:25] Skizzerz: after that, I'll have to fix the library, or at least send an upstream merge request. [22:51:35] to fix the login procedure. [23:03:30] ehuelsmann: well, just specify a token as the password instead of the normal account password, I think the flow should work as-is in that case [23:03:58] for the block, appealing on the account's talk page is probably going to be more expedient? You could request the ip block exemption group [23:04:12] not sure what the policy or process around that is on en.wikipedia [23:06:18] Skizzerz: ok. I've tried with the token instead of the account -- it ends me up on the same block so far. [23:06:31] I'll appeal on the talk page too :-) [23:07:12] yeah, token vs account pw won't impact the block at all [23:07:29] it just means that in the future the login will still work, and you can give it a token that restricts what it's able to do [23:08:10] I restricted it to being able to edit existing pages. [23:08:17] I'd even restrict it to a list of pages. [23:08:21] but that's not an option. [23:52:44] (as in: that's not an option being offered)