[09:11:09] hi....I have MediaWiki 1.31.3 php 7.0 MySQL 5.5.6 ....after upgrading from 1.28 to 1.31 auto suggestion is not working for pages created after upgrade...I have to give the complete name...its working ofr pages created before upgrade [09:31:52] any suggestions? [09:40:19] digit20: just to be sure, have you tried ctrl-f5 to force reload the page bypassing the cache? [09:40:55] also, did you try enabling logs and checking what happens when you are trying to search [09:44:01] suggestions use Ajax and that stuff can be cached locally [09:56:18] tried ctrl-f5 and $wgUseAjax = true; [09:56:25] still not working [09:56:42] how to enable logs [09:56:57] i'm new to this...can you help [15:25:56] Can someone explain what determines when a page preview tooltip will display an image? For example, on this page https://en.wikipedia.org/wiki/King%27s_Fianchetto_Opening, the pages for several chess players mentioned in the summary have images in their summaries, but the images are not displayed in their previews. [16:22:22] jmviz: see https://www.mediawiki.org/wiki/Extension:PageImages#Image_choice [16:31:34] Thanks tgr [18:08:24] Hello everyone, I have a system that uses the internal MW API as the engine to CRUD contents on our site. It was at 1.21.1 and we are trying to upgrade to 1.31.3 right now. I notice that a lot of the Hooks are migrated to be ran in DeferredUpdates. Is there any way to turn this off? [18:10:13] Or it seems that the internal API doesn't run the MW->doPostOutputShutdown(), hence no deferred updates are being processed. Am I supposed to add this manually? [18:11:49] The "internal" api? As in the web api, just called internally? [18:11:55] I guess the API won't call it for internal requests, because it obviously doesn't know that it's the end of the process... [18:12:07] https://www.mediawiki.org/wiki/API:Calling_internally [18:12:19] like this [18:12:28] Ok, right. It's not particularly an "internal api", it's the same, just called internally ;) [18:12:39] rather than a http type request to the api endpoint [18:13:26] That's right [18:14:08] is there a way to turn off deferred updates? [18:14:18] I don't think you can, no [18:14:22] from where/when are calling the API? [18:14:47] It kinda seems like some oversight (ie a bug) if MW isn't doing the "shutdown" stuff from an internal API request [18:15:15] in our business logic, for example, it runs the "action=edit" when a user is trying to edit a page [18:16:04] I'd suggest it's probably best filing a bug, explaining your use case, what's happening, what's not happening... [18:16:12] Would 1.32 / 1.33 solve this issue? [18:16:22] I don't think speicifcally, but I can't say for definite [18:16:27] And then the result should be said bug being fixed, or the docs being updated [23:03:21] Hi, I'm new to MediaWiki and this chat system (i.e., freenode.net). Does anybody know how to install Elasticsearch onto a Mediawiki? I'm currently setting up on Shared Hosting, but I'll move to VPS later so I can install VisualEditor. Do I need either sudo or root access in order to install Elasticsearch? [23:05:09] My Special:Version shows that I've installed Elastica and CirrusSearch, but Elasticsearch isn't listed under my installed Software [23:05:46] I don't think you *need* root to install ElasticSearch but it helps a lot if you do [23:05:55] I'm using MediaWiki 1.33.0, Elastica 1.3.0.0 and CirrusSearch 0.2 [23:06:15] you'll need a gigantic pile of RAM, and I guarantee that your shared host isn't going to give that to you [23:07:05] NeedsHelp: is there a reason you want ElasticSearch? [23:07:17] it's generally not useful unless your wiki has a very large number of pages [23:09:18] Yeah, I'm moving to VPS. Will that work? I learned last night that my shared hosting doesn't provide access to Node.js, but VPS does (again, I'm new). What's considered a very large number of pages? I'm hoping to build a wiki with a few thousand pages with 3000+ words each. Should I wait until we've built all those pages to install Elasticsearch? [23:10:43] how much RAM? [23:11:21] I can do 1GB, 2GB, 4GB, or 8GB RAM [23:12:10] How much do I need? the Mediawiki entries on CirrusSearch don't mention this [23:12:20] How long is a piece of string? [23:13:10] so reasons you would want ES: 1) you have high volume of searches which is causing undue resource stress on mysql, 2) your pages contain words or symbols that mysql is not able to index properly, 3) your searches are having terrible performance and take a long time to complete [23:17:05] Skizzerz I see. Then do you suggest that I postpone installing ES until one of those three has happened? I thought it would be best to install all the extensions I need at the beginning Reedy I'm not sure what you mean. The number of characters in the string? [23:17:35] elastic search can take as much memory as you throw at it, effectively [23:17:57] I'd personally recommend against making your deployment overly complex, which means not installing things unless or until you need them [23:19:27] I see, ok. That helps a lot [23:20:03] Thank you [23:20:26] oh, I missed 4) your users are finding it difficult to find the correct results with mysql searches, and could use the additional power that ES searches provides [23:21:19] ES is a powerful search engine, but it's a bit of a pain to keep maintained. Namely, version upgrades suck [23:22:29] (there's a reason the mediawiki extension tells you to install a specific version of ES to match the extension's version -- it's because newer versions have almost certainly broken compatibility with what the extension is trying to do) [23:25:33] That makes sense. How would I install ES without root access? Where would I do it? I'm guessing it's not like other extensions where all I need to do is put it into the extensions folder and call it in LocalSettings.php. [23:25:54] your shared host will likely prevent you from running it [23:26:07] it's a separate server daemon written in java [23:26:49] otherwise, you would follow the installation instructions on the elasticsearch website for running from their downloaded files [23:28:33] Oh ok. My hosting provider seems to allow for daemon server processes [23:28:43] NeedsHelp: here's the install guide for Elasticsearch v6.5 (comptabile with mw 1.33): https://www.elastic.co/guide/en/elasticsearch/reference/6.5/install-elasticsearch.html [23:29:08] You'd be looking at the first option: "Install Elasticsearch with .zip or .tar.gz" [23:31:02] I see. I saw that WikiHow (https://www.wikihow.com/Special:Version) uses MW 1.33.0, but their Elasticsearch is 6.8.2 How is that possible? Doesn't MW 1.33.x require Elasticsearch 6.5.x? [23:31:36] 6.8 might work, but you may need to do some work to resolve any compatibility issues [23:31:55] 7.x may also work, but the same applies [23:32:02] Maintaining ES is hard, as Skizzerz said [23:32:10] Upgrading it for Wikimedia isn't an easy or quick process [23:32:26] So the support in MediaWiki will follow the version used in Wikimedia [23:34:43] Do you know how to quantify or describe how hard it would be? Maybe how much expertise is required or the time it takes per week to maintain? [23:35:44] [00:12:20] How long is a piece of string? [23:36:56] Lol. I get it now [23:36:58] Thanks agin [23:37:04] Thanks again [23:37:10] Sorry I can't give a better answer [23:37:26] It's ok. I think it depends on the wiki