[00:26:29] <qtum>	 is there a way to add a onfocus event to the default edit box? <textarea tabindex="1" accesskey="," id="wpTextbox1"> --- I was hoping to add onfocus="function" to it
[00:45:14] <MaxSem>	 qtum, $( '#wpTextbox1' ).on( 'focus', function() { ... } )
[00:47:51] <qtum>	 i'm allowed to inject javascript onto the page?
[00:48:23] <MaxSem>	 no, of course. you can do it in your user JS
[00:48:56] <qtum>	 ResourceLoader::makeInlineScript($js) I think is the thing for it?
[00:49:18] <Esther>	 For all users or just one user?
[00:49:30] <qtum>	 all users, I have server access
[00:49:33] <Esther>	 There's a "MediaWiki:Common.js" page you can use to inject JavaScript.
[00:49:35] <Esther>	 It's a wiki page.
[00:49:37] <MaxSem>	 ah, in MW
[00:50:15] <MaxSem>	 the proper way is to register a ResourceLoader module and add it to pages where it's needed
[00:50:35] <qtum>	 is Common.js preferable to using RequestContext::getMain()->getOutput()->addScript(ResourceLoader::makeInlineScript($javascript)) ?
[00:50:40] <MaxSem>	 https://www.mediawiki.org/wiki/ResourceLoader/Developing_with_ResourceLoader
[00:50:52] <MaxSem>	 really depends on what you want to do
[00:51:56] <MaxSem>	 inline scrpts is something you shouldn't do unless you have some insanely specific requirement
[00:52:19] <MaxSem>	 it's either on-wiki scripts or via ResourceLoader modules
[00:52:36] <Esther>	 You could make a JavaScript gadget.
[00:52:42] <Esther>	 If you want to default on and allow users to override.
[00:53:02] <Esther>	 (That's from the Gadgets MediaWiki extension.)
[00:53:51] <MaxSem>	 what do you want to do?
[00:54:57] <qtum>	 Just execute some JavaScript every time &action=edit is hit
[00:55:36] <MaxSem>	 for yourself or everyone?
[00:56:09] <qtum>	 everyone
[11:05:53] <Dror_[FFS]>	 Hi, guys - I'm writing a new extension, which needs to create new articles (well, redirects) on another *local* wiki. Is there another way besides using the API (since both wikis are local)? And If not, is there a built-in way to access the API for this purpose? Using a custom MWHttpRequest seems just wrong.
[11:22:04] <Nikerabbit>	 Dror_[FFS]: since it is a different wiki with different configuration, I wouldn't skip the API. you need to make a web request
[11:24:37] <Dror_[FFS]>	 @Nikerabbit, so just a regular request? While there's a built-in ForeignApi for JS, there doesn't seem to be anything like that for PHP.
[11:26:55] <Nikerabbit>	 none that I am aware of
[11:27:07] <Nikerabbit>	 but it's so simple, why would you need any :)
[11:27:53] <Nikerabbit>	 Dror_[FFS]: well, for logging in and tokens, I guess
[11:29:02] <Dror_[FFS]>	 Because I hate re-inventing the wheel, even if it's a simple spoked wheel. And the logging in and tokens, exactly. Well, technically, since its the same user, it will already be authenticated, right?
[11:30:19] <Nikerabbit>	 Dror_[FFS]: see TranslationNotificationJob.php in the TranslationNotifications extension for an example
[11:30:47] <Nikerabbit>	 the authentication depends on cookies and whether the wikis are configured to share same auth or not
[11:33:31] <Dror_[FFS]>	 Nikerabbit:  thanks, that's a great reference! See what I meant about reinventing the wheel? This is actually the beginning of implementing another API client...
[11:34:10] <Nikerabbit>	 Dror_[FFS]: yeah I agree
[11:35:01] <Nikerabbit>	 Dror_[FFS]: a non-lazy person with extra time would take that code, polish it for such a class and submit it for inclusion in core :)
[11:35:45] <Dror_[FFS]>	 Dror_[FFS] looks behind him to see if such a person is standing there...
[13:49:07] <Rosencrantz>	 What are the consequences of setting autocreateaccount to true for all users?
[13:49:16] <Rosencrantz>	 I ran into issues with the LDAP extensions, found this https://phabricator.wikimedia.org/T142094
[13:50:02] <Rosencrantz>	 I tried what it had there, but it didn't work for the user group, but it did for all users (i.e. * )
[13:50:19] <Rosencrantz>	 I just want to make sure that there's not any other weird consequences I might be unaware of
[14:24:25] <Nemo_bis>	 apache 2.2.x end of life, whoo https://www.apache.org/dist/httpd/Announcement2.2.html
[15:31:26] <Fabiano>	 hi, my wiki not show images
[15:33:30] <Fabiano>	 http://www.crmnetxpert.com.br/wiki_/index.php?title=P%C3%A1gina_principal
[15:34:05] <Fabiano>	 help
[15:44:04] <FoxT>	 Fabiano: When loading the images the server sends an HTTP 500 error code, i.e. internal server error, but without more info it is hard to tell what went wrong
[15:45:02] <FoxT>	 Fabiano: see https://www.mediawiki.org/wiki/Manual:How_to_debug#PHP_errors on how to turn error  messages on
[15:46:23] <Fabiano>	  I enabled the debug
[15:46:24] <Fabiano>	 http://www.crmnetxpert.com.br/wiki_/index.php?title=P%C3%A1gina_principal
[15:48:49] <FoxT>	 Fabiano: Hmm, that does not yield much. :(
[15:48:52] <FoxT>	 See http://www.crmnetxpert.com.br/wiki_/images/c/cc/Botao-lancamentos.png
[15:51:18] <Fabiano>	 How to solve this?
[15:54:47] <FoxT>	 Fabiano: No idea, sorry. Without a clue on what the error may be it's hard to say. Maybe somebody else has an idea
[15:56:04] <Fabiano>	 thanks
[16:15:47] <mobi9>	 Skizzerz not sure if you're there, but I tried using WebRequest to set a session value and it gave an error about calling a member function on null https://dpaste.de/ujMY
[16:16:55] <Skizzerz>	 where is that code
[16:17:02] <Skizzerz>	 i.e. is it inside of a hook?
[16:17:36] <Skizzerz>	 if so, which hook. If not, where is it
[16:17:55] <Skizzerz>	 my first guess is that you're trying to retrieve the request before mediawiki is fully initialized
[16:19:59] <mobi9>	 I just put it in LocalSettings.php cause I was testing if it would work
[16:22:07] <Skizzerz>	 that's too early
[16:22:16] <Skizzerz>	 mediawiki is not initilized by the time LocalSettings is run
[16:22:21] <Skizzerz>	 you need to do it in a hook
[16:22:38] <Skizzerz>	 or via an extension function
[16:23:22] <Skizzerz>	 (the best way would be to use a hook that gives you a context object or the request object as a parameter so you don't need to use global methods to get at it)
[16:25:39] <mobi9>	 is there a way to find hooks which give you a context object/webrequest object?
[16:29:12] <Skizzerz>	 https://www.mediawiki.org/wiki/Manual:Hooks :)
[16:29:30] <Skizzerz>	 look for the one that seems most applicable to you
[16:30:37] <mobi9>	 lol this feels like back in middle school
[16:30:54] <mobi9>	 i'm thinking UserLoginComplete -> set a unique session variable
[16:31:28] <Skizzerz>	 sure; this will require that all of your users log out and log back in again though in order to get it (or wait until their current login expires)
[16:32:03] <Skizzerz>	 although it's easy enough to force a mass-logout
[16:33:01] <mobi9>	 that's also mean it would never trigger for anonymous edits too i guess
[16:33:53] <mobi9>	 but anonymous users don't have sessions anyway
[16:35:01] <Skizzerz>	 yes they do
[16:36:19] <Skizzerz>	 er, I thought they did
[16:36:24] <mobi9>	 why would an anonymous user need a session? there's nothing important to persist i thought?
[16:36:37] <Skizzerz>	 oh it's in session storage, not a cookie
[16:36:58] <Skizzerz>	 mediawiki unconditionally starts a session (or resumes an existing session) on every request
[16:39:48] <Skizzerz>	 that said, I don't think an anon session is actually used for anything besides perhaps rate limiting (but that may be by IP)
[16:40:43] <mobi9>	 when do anon sessions end though? for logged in ones it's going to be when the user logs out
[16:41:06] <mobi9>	 but if i setsessiondata() on an anon session, i have no idea how long that's valid for
[16:42:34] <Skizzerz>	 depends on the storage mechanism. For example I went to wikipedia in an incognito window (so anon), and had a session id in my sessionStorage
[16:42:56] <Skizzerz>	 sessionStorage is unique to an individual tab/window, so if I opened a second tab that'd be a different session
[16:43:07] <Skizzerz>	 however if it was stored as a cookie then that would be shared across all tabs
[16:43:33] <Skizzerz>	 sessionStorage goes away when the tab/window is closed. The cookie goes away when it expires
[16:44:42] <Skizzerz>	 I'd need to actually dig into the session handling code to see if mediawiki treats anon sessions as "live" or not
[16:44:52] <Skizzerz>	 so, take everything I said above with a grain of salt
[16:45:01] <mobi9>	 I believe mediawiki stores the session information in a cookie named mediawiki_session or something
[16:47:34] <Skizzerz>	 you may find some of the things at https://www.mediawiki.org/wiki/Manual:SessionManager_and_AuthManager/Updating_tips#SessionManager useful
[16:47:42] <mobi9>	 nvm I think AlternateEdit or one of the EditPage hooks would be best
[16:47:48] <Skizzerz>	 it describes some of the changes to session handling made in 1.27, and how things worked before/after those changes
[16:48:17] <mobi9>	 thanks
[16:48:45] <mobi9>	 so the biggest issue was calling the function before it was initialized, and adding it to a hook should resolve that.
[16:48:51] <mobi9>	 the issue now is how to handle anonymous users
[16:51:38] <mobi9>	 on a related note, do you think killing rapid edits would be an effective way of stopping spam?
[16:52:03] <Skizzerz>	 !spam
[16:52:03] <wm-bot>	 For information about combating and handling spam in MediaWiki, see <https://www.mediawiki.org/wiki/Manual:Combating_spam>.
[16:52:06] <mobi9>	 if the time between edit text area load and edit submission was < 1 second or something, block the edit
[16:52:28] <Skizzerz>	 maybe, although you'd probably want to *not* block edits made in such fashion via the API
[16:52:47] <Skizzerz>	 something like Extension:ConfirmEdit is probably a bit more foolproof
[16:54:03] <mobi9>	 the old recaptcha was surprisingly useless, but the new one seems better
[17:58:48] <ShakespeareFan00>	 Hi
[17:58:58] <ShakespeareFan00>	 Currently when an edit is saved it saves the entire edit form text
[17:59:19] <ShakespeareFan00>	 Is there a way to set up mediawiki so it only needs to save what's actually changed..?
[18:00:29] <Skizzerz>	 ShakespeareFan00: not that I'm aware of; that would be problematic for a number of reasons
[18:00:39] <Skizzerz>	 for example, what happens if you delete a revision in the middle of page history
[18:00:55] <ShakespeareFan00>	 Skizzerz:  Hmm
[18:01:48] <Skizzerz>	 if you're running into storage space concerns, you can permanently delete deleted revisions, or you can permanently delete all old revisions via maintenance scripts
[18:01:49] <ShakespeareFan00>	 Skizzerz:  The problem is that I sometimes have very large pages at English Wikisource, where I make a minor edit of 2-3 charcters typo fixing
[18:02:26] <ShakespeareFan00>	 It seems a waste of bandwidth to be sending back and forth 1K long text blocks, when all that's changed is 2-3 characters
[18:02:46] <Skizzerz>	 oh, I was thinking you meant storing diffs in the backend rather than full text
[18:03:23] <Skizzerz>	 you can do a section edit if the page has multiple sections
[18:03:30] <Skizzerz>	 that will reduce roundtrip bandwidth
[18:03:41] <Skizzerz>	 (editing section=0 edits the article lead)
[18:03:48] <ShakespeareFan00>	 Skizzerz:  Yes..
[18:03:56] <ShakespeareFan00>	 which is applicable on Wikipedia
[18:04:07] <Skizzerz>	 otherwise, I don't see of a way to submit only a diff/patch
[18:04:34] <ShakespeareFan00>	 English Wikisource doesn't necessarily use sections in the same way
[18:04:52] <ShakespeareFan00>	 And this was about reducing transactional size, not storage
[18:08:15] <ShakespeareFan00>	 Storing backend as diffs wouldn't work for the reasons you outlined..
[18:08:46] <ShakespeareFan00>	 However,  It should in theory be possible to generate some kind of "journal" log based on the stored edits?
[18:09:23] <ShakespeareFan00>	 The client side API could then request this journal to update a local copy of a section rather than needding to download everything
[18:11:41] <DanielK_WMDE>	 ShakespeareFan00: that journal is called a diff. you can get the difference between any two revisions from the api, as a unified diff. then you can apply it as a patch.
[18:12:14] <DanielK_WMDE>	 but that doesn't work per section. sections are not first class citizens in mediawiki
[18:12:37] <DanielK_WMDE>	 section editing was hacked in as an afterthought. there is no per-section history, or per-section diff.
[18:13:12] <DanielK_WMDE>	 re storing edits as diffs: compressing adjecent revisions togetehr is simpler and more robust.
[18:18:21] <Skizzerz>	 DanielK_WMDE: I think he was trying to *submit* a diff as an edit, as opposed to submitting the full new page text
[18:18:33] <Skizzerz>	 rather than backend concerns
[18:28:19] <DanielK_WMDE>	 ah, i see
[18:28:43] <DanielK_WMDE>	 well, we *could* support that. why not. "someone" could write an extension :)
[19:00:01] <ShakespeareFan00>	 Skizzerz:  Thanks
[19:00:08] <ShakespeareFan00>	 Thats what I meant
[19:00:38] <ShakespeareFan00>	 The BIG idea would be have to pages you could see other edits on in REAL time  like on Google Docs
[19:00:50] <ShakespeareFan00>	 You see people changing the page as it happens
[19:01:03] <ShakespeareFan00>	 but that's a BIG thing to implement properly
[19:01:25] <ShakespeareFan00>	 I'm not sure there's a way of doing "wiki-whiteboards" like that at present
[19:03:16] <ShakespeareFan00>	 Skizzerz:  Also only sumitting the diff would say upload width for some users, like those on Mobile
[19:03:21] <ShakespeareFan00>	 *save
[20:05:20] <cwre>	 This: body.mediawiki:before {content: "REFERENCE ONLY"; position: fixed; top: 0%; left: 50%; font-size: 40px;} doesn't display anything when placed in MediaWiki:Common.css... Anyone know why? My CSS is not very good.
[20:14:35] <MatmaRex>	 cwre: looks like it should work… is your site public so that we could try to debug there?
[20:21:30] <cwre>	 This isn't a public wiki, no.
[21:09:45] <Skizzerz>	 cwre: before needs :: in front of it, not :
[21:09:49] <Skizzerz>	 i.e. body.mediawiki::before
[21:10:34] <Skizzerz>	 (although :before should technically work, it's just nonstandard)
[21:10:54] <cwre>	 Skizzerz: it worked without, I'll change it. My positioning was all wrong.
[21:10:55] <Skizzerz>	 did you remember to clear your cache?
[21:11:08] <Skizzerz>	 ah
[21:11:18] <cwre>	 Skizzerz: yeah, do you know how I can repeat this at each page?
[21:11:39] <cwre>	 I'm looking to apply this on print in Print.css, I want every page to have it.
[21:11:43] <Skizzerz>	 what do you mean by "repeat this at each page?"
[21:11:56] <cwre>	 Sorry, I didn't explain, did my previous message clarify?
[21:12:20] <Skizzerz>	 as-written, that should apply to every page
[21:12:36] <cwre>	 It's not.
[21:12:43] <Skizzerz>	 did you clear your cache? ;)
[21:13:02] <cwre>	 Yeah it's applying on the one page but not on subsequent pages
[21:14:52] <Skizzerz>	 unfortunately I can't really assist there then, all I can say is that it *should* be working
[21:15:16] <Skizzerz>	 if you have a frontend cache like varnish you may need to clear that, maybe
[21:15:33] <cwre>	 I don't think we do.
[21:15:38] <cwre>	 I'll have to look around.
[21:16:26] <cwre>	 Skizzerz: I realize I don't have position set, that's probably the issue. I said it was wrong, so I just stripped it. That's probably what's applying on each page.
[21:17:29] <Skizzerz>	 I'm slightly questioning why you want to apply that rule to the body, as opposed to one of the inner layout divs
[21:17:44] <cwre>	 Skizzerz: what would a better div be?
[21:17:54] <Skizzerz>	 idk, where are you trying to put it?
[21:17:59] <cwre>	 Open to suggestions... My CSS is trash.
[21:18:14] <Skizzerz>	 check the page source of a page, see what the layout is like
[21:18:18] <cwre>	 Skizzerz: It has to be at the top of each page, maybe we can also do the bottom?
[21:18:23] <Skizzerz>	 to see where the best spot to inject for your use-case is
[21:18:24] <cwre>	 Probably top center bottom center?
[21:18:59] <Skizzerz>	 div#content is the beginning of the page content, for instance
[21:19:34] <cwre>	 Skizzerz: so div#content::before?
[21:19:36] <Skizzerz>	 (above the page heading)
[21:19:42] <cwre>	 I'll try that.
[21:19:49] <Skizzerz>	 <Skizzerz> check the page source of a page, see what the layout is like <Skizzerz> to see where the best spot to inject for your use-case is
[21:20:05] <Skizzerz>	 as I don't know exactly what you're trying to accomplish, you'll need to experiment and see what works best
[21:20:13] <cwre>	 Skizzerz: I'm asking if that's how the reference mode works 
[21:20:27] <Skizzerz>	 yes?
[21:38:05] <cwre>	 Skizzerz: if I do ::before and ::after, is there a way to force conent to go around it?
[21:38:22] <cwre>	 Rather than just having it overlayed on content?