[02:58:30] delete / block: https://www.mediawiki.org/wiki/MediaWiki_Stakeholders [03:29:43] vandalism - translation abuse - https://www.mediawiki.org/wiki/Special:Contributions/2600:1:B00A:71C8:24BB:C75C:192:1C8D [03:54:40] If I previously had posted a request for user rights, which would be a better approach? Linking and updating the old request to review again, or just create another request on the page? [03:56:48] DSquirrelGM: create a new subpage but append (2) to the title [05:42:34] Can't tell if this person is just having an issue with VE, trying to delete the link, or just posting some sort of notice on that line ... https://www.mediawiki.org/w/index.php?title=Extension:Scribunto/Example_modules&curid=148960&diff=3680256&oldid=2440927 [07:43:47] installed cirrus search in mediawiki and it's great tool for search, is there any way to keep the search bar at the center of main page [07:44:55] karthi344: there's the timeless skin that does this: https://www.mediawiki.org/wiki/Skin:Timeless#/media/File:Timeless_MediaWiki_Skin.png [07:44:56] users are constantly asking us to keep the search bar in the center of page , instead on the right corner [07:45:12] is it possible to so it ? [07:46:52] looks timeless skin keeps the search bar at the top of the page, but I want at the center of the page ? [07:47:44] you basically want a special from page? [07:47:52] s/from/front [07:48:13] the search bar in the middle somewhat means you don't have content to display? [07:49:51] another option is write a Main page using the https://www.mediawiki.org/wiki/Extension:InputBox extension this way you can add a search box anywhere [07:52:04] tried with inputbox, like you said, it brings the search box at the center of main page, but it's not giving auto suggestion like search bar at the right corner of main page [07:53:04] indeed it's one of its limitation... I'm not aware of any solution that would solve your needs [07:53:43] oooh I get it.... [07:54:21] any other way I can bring the special page search bar to center of the main page ? [11:19:20] Hello, I just wanted to ask is there an API call that I can use to check if a wiki page exists or not? Thank you [11:22:08] just request the page...? [11:22:46] https://www.mediawiki.org/wiki/API:Revisions [11:22:54] saper: thanks [11:28:30] https://www.mediawiki.org/wiki/API:Query#Example_3:_Missing_and_invalid_titles [19:44:18] just a comment. it's very counterintuitive that "Email me when a page or a file on my watchlist is changed" is not either in the notifications or watchlist tab of Special:Preferences [19:46:13] I guess it's because it very much pre-dates notifications [19:46:19] And it's in MW core, not an extension [19:46:36] perhaps [19:46:47] I didn't notice it at the bottom of user profile cause it was off the screen [20:00:54] Reedy: are those other tabs provided by an extension or something? [20:00:58] to the user, that isn't clear [20:01:07] To the user, it shouldn't be apparent [20:01:21] well yeah, that's kind of my point [20:01:23] Notifications is [20:01:29] I am explaining from a user perspective [20:01:30] Because it's not core MW functionality [20:01:36] It really shouldn't matter though [20:01:49] Watchlist is in mw core, and is just a grouping thing [20:02:04] ok. well then I submit that it's weird to have a watchlist thing not on the watchlist tab :) [20:07:10] Post a bug :) [20:09:56] haha ok, maybe I will [20:10:47] For most stuff, the audit trail, conversation and discussion [20:12:18] huh? [21:53:35] Hello. A question to the experienced mediawiki devs. What is the easiest way to save some data from about 1k users. For example login-time/logout-time (only an example). [21:55:51] hooks is probably the answer [21:56:04] the problem is "only an example" doesn't mean every scenario is the same [21:58:08] logout-time is a very unreliable measurement [21:59:40] Unless you do it with the caveat it's only based on logout being pressed [22:01:29] Well we have some custom extension and we want to know how often they are used in a month. [22:03:06] I only want to know where to store the data. Better said, are there alternatives to the database [22:03:14] what does the extension do? [22:03:29] Usual advice is create a table for the extension in the database [22:04:27] your metrics need to take into consideration how often the extension code is run, and whether or not every run should be counted. That will vary based on what the extension actually does [22:04:53] how an extension which adds a new parser function operates is very different than how an extension which adds a special page operates [22:04:56] Skizzerz corporate Reedy so you say the only good way is to go for the database, even it is only for a month? [22:05:10] What else would you really use? [22:05:11] A file on disk [22:05:12] ? [22:05:25] Contention and conflicts would be a mess if sufficiently busy [22:05:36] The hooks for the extensions a setup, to get the data is no problem, but I'm not sure where to store it [22:05:59] database or a logging group would be the main go-tos, and logging group is really only useful if you have structured logging configured to dump it somewhere like monolog or logstash [22:07:16] file on disk works ok if your wiki is low traffic and you only have a single web server (as opposed to a load-balanced farm or the like) [22:07:17] That's what I thought. But I wanted to ask you guys. [22:09:04] another option is to hook into an existing APM infrastructure that you have, but you'll be on your own largely speaking for writing that integration code [22:13:45] Thank you guys. A lot of you online. Do you have a meeting :)