[00:02:19] Hi - I am having an issue upgrading from mediawiki 1.37.6 to 1.42. I am utilizing docker and docker compose, but the error I am receiving is that I am missing the intl PHP extension. Im having issues navigating the docs as well to try and fix this. Has anyone run into this before? [00:28:16] why is Media Viewer actively sabotaging zooming into an image? it basically makes it undesired to open any image on mediawiki with a simple click in Media Viewer and instead i have to right click it in my browser to open the image in a new tab and zoom into it [00:28:40] i dont understand the rationale for Media Viewer to be in the way of zooming [00:29:31] like how am i supposed not to have Media Viewer like this? https://en.wikipedia.org/wiki/Fermat%27s_Last_Theorem#/media/File:Diophantus-II-8-Fermat.jpg [00:30:19] it would be better if Media Viewer was deleted and the link directly to the image file [01:01:22] i ended up figuring out my issue, i had extensions that were just outdated. ty [01:12:10] de-facto: if you're logged in, you can disable it via Special:Preferences [02:11:23] so i need a login to mediawiki for disabling the zoom blocking? [15:03:13] Hi! I ask here a question that can also be found at https://www.mediawiki.org/wiki/Project:Support_desk [15:03:13] I would like to setup a Mediawiki site. In order to manage the site, I deliver code changes to a Git folder, and the changes are then transmitted to a staging server for test and to production for use. [15:03:14] If I want to make changes to configurations that are in the file system there is no problem since the FS will be on Git. But what if I want to have control even on aspects that are saved in the database, like the categories and the templates that are available on my site? An obvious way would be to dump and restore the database, but I don't want to [15:03:14] store all of it in Git. Is there a way to automate this process (having a configuration file in Git that does the work for you?) [15:03:15] Thanks for your help! [15:04:36] Hi, I post here a question that can be found also at https://www.mediawiki.org/wiki/Project:Support_desk [15:04:36] I would like to setup a Mediawiki site. In order to manage the site, I deliver code changes to a Git folder, and the changes are then transmitted to a staging server for test and to production for use. [15:04:37] If I want to make changes to configurations that are in the file system there is no problem since the FS will be on Git. But what if I want to have control even on aspects that are saved in the database, like the categories and the templates that are available on my site? An obvious way would be to dump and restore the database, but I don't want to [15:04:37] store all of it in Git. Is there a way to automate this process (having a configuration file in Git that does the work for you?) [15:04:38] Thanks for your help!