[00:25:15] Hi, I get a request timeout when a fresh 1.32 install attempts to update the database [00:26:39] Can you do commandline update.php [00:26:52] I have no server access [00:27:33] You can try running install update script multiple times . It should continue where it left off [00:27:57] From a fresh install though there really shouldnt be anything to update [00:28:45] I tried, but it went straight to the request timeout message and that's all it will show now [00:29:15] The fresh install still has to connect the existing database [00:30:23] This worked with a smaller wiki but this one is big [00:30:31] Maybe something else wrong. Check php error logs if you have access [00:31:02] If its a fresh install how is it bigger/smaller then the other? [00:31:21] The existing database is big [00:33:02] Usually in mediawiki parlance fresh install means no existing db [00:34:05] Fresh install as opposed to using the upgrade function as that doesn't work [00:34:45] I mean. What you are describing is the upgrade function [00:35:22] Upgrade = with LocalSettings.php present [00:37:39] To spell it out, what I am doing now is running the install with no LocalSettings.php, then add it manually before going to the wiki, and then upload the images [00:38:19] I suspect running with no localsettings.php just creates a new empty db [00:38:32] No, it asks for the db [00:39:01] That can be a new empty one or an existing one [00:39:41] Even if that works. I suspect that very few people test that code path [00:40:54] It's the only possibility that remains short of importing the content of the database to a new empty one [00:41:10] Regardless. For certain size wikis you eventually have to run update.php commandline as there is a limit how long mw can keep a page open [00:41:33] I had to do this with every upgrade in the past, too [00:41:51] No idea if you are at that size yet. I think it has to be a pretty big wiki before you reach that point [00:41:53] Can I change the limit? [00:42:23] You can adjust apach configs to adjust max timeout [00:42:50] But if you dont have shell access you prob dont have that either [00:43:02] The zipped database is 1 GB [00:43:46] That is kind of getting bigish [00:44:23] Works fine though as long as I don't need to do any upgrades [00:44:44] Its not big to use [00:45:10] Just to be able to upgrade entire db in one page load [00:48:06] Yes, it would be nice if the software could do that in steps [00:49:25] To an extent it does - it remembers where it is mostly and pucks up where it left off if restarted mostly [00:49:35] But its difficult [00:49:47] To truly make it step by step [00:59:16] Got it!!!! I uploaded 1.32 again for another install attempt and apparently it started with the database already partly updated, and made it through!!! [10:07:06] Hello [10:43:18] Hello everybody i am totally lost with the installation of Wikibase query services is there a real step by step configuration documentations somewhere [12:27:08] hi. it seems that minervaneue is running in mobile mode (while i browse on desktop) on my wiki [12:27:45] wfLoadExtension( "MobileFrontend" ); [12:27:45] $wgMFAutodetectMobileView = true; [12:27:46] ... [12:27:46] wfLoadSkin( "MinervaNeue" ); [12:27:46] $wgDefaultSkin = "minerva"; [12:28:41] can't seem to fix this... [14:00:08] what is the recommended MW config/extension to address a the conflict that arises when 2 contributors are editing different rows of the same table (of the same page) .. and one hits save and then the other ... is there a page in the manual that I can point people to to explain how to resolve this situation without having to explain and train them myself? thx [14:21:16] I see that Extension:TwoColConflict somethign is under WMF version control and used on Wikimedia projects.. is this something that is expected to be MW core someday? [14:21:16] https://www.mediawiki.org/wiki/Extension:TwoColConflict [14:46:02] revansx[m]: typically stuff like that remains as extensions for a long, long time [15:11:47] ok. thanks [15:55:27] Hi All :) [16:01:17] I recently started to develop to MediaWiki that I installed on my server, but I'm having difficulties that have to beginners. [16:01:28] And for weeks I dug up the web ... the Google and MediaWiki-media and various guides, and I did not find answers. [16:10:07] Yoni_: what specifically are you having trouble with? You aren't going to get any help here unless you actually state what your issues are [16:13:19] Citoid Does not appear in my edit menu, I want to edit my footer, and I do not know how, I want to completely remove and add tabs on my pages according to different permissions.... [16:13:29] The existing manuals, not updated, the extensions do not work - do not match the latest version, I want to develop a management panel for my system, but again... I am encountering the obstacles of beginners. [16:15:32] Citoid: No idea, check the docs. It probably depends on Extension:WikiEditor (or maybe VE, not sure) [16:16:25] Footer: Simple edits can be performed by editing pages in the MediaWiki namespace. Check Special:AllMessages for a list of all interface text you can customize this way. You can use this to, e.g. insert additional links. More complex changes will require either an extension or a custom skin [16:18:12] Tabs: Configure $wgGroupPermissions to modify whether or not built-in tabs are displayed. MediaWiki doesn't provide fine-grained read controls (e.g. restricting access to history, etc.), and any solution you attempt to develop there will almost certainly have numerous holes in it. It's best to just not bother. For adding new tabs, usually accomplished via extension although you can do it in js as well (recommend Extension:Gadgets if using [16:18:13] js to add tabs) [16:19:25] for anything where I said "write an extension", look through the developer guides on mediawiki.org and get acquainted with the actual php codebase as well to learn how it's pieced together. Looking at the list of hooks and what existing extensions use those hooks can provide a starting point [16:20:16] but like all programming tasks, it's up to you to become familiar with the platform enough to actually understand how your code interacts with everything else, so you need to be willing to put forth that effort [16:37:36] Thanks Skizzerz [16:37:45] I installed VE, I activated Cito simple. I do not have the richer - the one you write a link, and automatically completes all the information. I've read it: https://www.mediawiki.org/wiki/Citoid and everything that's relevant to it. [16:38:01] The current extension for footer editing is not working properly. [16:38:11] I hide tabs using CSS, I want to hide history and the like that, in the code itself of the page template. So that it will not be possible to reach it at all. [16:38:23] Really, if I write here, it means I went through all the relevant guides, and everything I could find online. If I write here, I have given up. I really studied the subject thoroughly and got along with a lot of other obstacles. [16:38:35] you can always browse to the history url directly, there's really no easy way to prevent that [16:38:36] I'm working hard to become a specialist code developer for MediaWiki, but getting stuck on small things. [16:38:49] mediawiki really is simply not designed for such levels of access control [16:39:15] as long as you're fine only hiding it from casual contributors, then css is fine [16:39:31] if you want to block access entirely, consider using some other platform instead of mediawiki which provides the features you seek [16:40:54] I have (in the past) dealt with blocking history access programatically via a custom extension, so it's doable, but you first need to be very well versed in how mediawiki acls are put together and used internally, which requires a lot of digging through the php code [16:45:53] I really like MediaWiki. Using the platform answers my goals. I am trying to make the platform flexible for my changes and requirements. [16:47:44] I've been digging PHP code for the past few weeks. I study the system. And I thought maybe here I could get some answers on how the platform works. [16:50:45] your questions are still too vague and over-arching for me or anyone to give concrete answers. [16:51:20] I think it's time to create a simple but rich management panel for the platform that will allow flexible platform use. [16:51:36] are you volunteering? [16:52:49] such a thing almost certainly won't be championed by the WMF because it's simply not relevant to their needs and use cases, so the only way it'll happen is if a volunteer developer or group of developers steps up to do it [16:54:25] I need you to at least tell me which files to check. And from where the information is called, from which json file or database. [16:55:11] Well maybe mwstake would be interested in something like that [16:55:17] I am trying to establish such a community - to develop a mediawiki management panel. [16:55:58] They keep talking about sponsoring development. But so far havent really put any money where their mouths are [17:00:21] I thought to produce an Hackathon for it, voluntarily, I am an expert in that and does Hackathons to other organizations day by day [17:00:39] a* [17:01:51] I just fell in love with MediaWiki, and I want it flexible. [17:05:26] If someone is interested in taking part in a development community to develop a MediaWiki management panel - send me an email: me@yoninfo.me [19:31:57] Is it possible to use a different markup language, out of curiosity? [19:43:46] N3X15: in place of wikitext? [19:44:07] Yes. [19:44:25] I don't know, but my guess is yes. Dunno if it is easy though [19:44:25] Like say, Markdown or BBCode. [19:45:04] Figure I'd ask here before embarking on digging through mediawiki's internals :P [19:46:34] I Seems like there existed some markdown extensions but that they are no longer maintained [19:47:31] Thanks. [19:48:45] https://www.mediawiki.org/wiki/Requests_for_comment/Markdown [19:57:48] Its possible [19:57:56] See content handler [20:56:41] Good afternoon. I was wondering if there is an extension that allows mediawiki to pull from an api that requires an Authorization: Bearer token in the header of the request? I looked at ExternalData but can't seem to find anything about including the token. Trying to get data from Asana to present to the page. [20:58:16] You'll prob have to do something custom i think