Extracting the tarball you have in your question will create the directory mediawiki-1.33.0 which contains the following sub-directories:
$ tree -dL 1 mediawiki-1.33.0
1) Create a file exclude.me with:
2) Extract the archive
tar xvzf mediawiki-1.33.0.tar.gz --exclude-from=exclude.me --strip-components 1 -C /path/to/your/wiki
In suggestion see:
But if ...
It's not a derivative of Debian, but Arch's wiki has information I've often found useful, presented with the right amount of detail for me to solve my problems.
If that's not it, Debian's wiki includes a list of its own derivatives.
I found a perfect solution at dougie.io's Using Wget, Grep, and Sed to Download Public Domain Wallpapers From a Web Page. I'm trying to boil it down to the main steps (to keep it available here as well):
Download the HTML page using wget:
wget https://en.wikipedia.org/wiki/Thirty-six_Views_of_Mount_Fuji \
-O page.html -O page.html
Extract the image ...
Solution in my case was to comment the following lines out of the /etc/httpd/conf.d/nss.conf file:
#LoadModule nss_module modules/libmodnss.so
service httpd start
and it works again!
thanks for all!
Given I only created the user and did nothing else with it afterwards, I was able to fully delete the user from the MediaWiki system this way:
I deleted the (MySQL) database table-row for that user (TEST_USER), from these tables:
Then to ensure no data remains for that user in database, I opened the database itself (without ...
I fixed it, thanks to Christopher for pointing me in the right direction with his query about cgi.fix_pathinfo=0 in php.ini.
His specific question did not fix the issue, but I continued to play around with settings near cgi.fix_pathinfo=0 in php.ini and was able to get a different error message with NO error from PHP-FPM complaining about not being able to ...
If the wiki is up, the most robust method is to just ask (via the generator property of the siteinfo API, for example) - changes to that are subject to a deprecation policy, while any internal structure you rely on could change without warning.
If that's not an option, you can try parsing out the value of $wgVersion from includes/DefaultSettings.php. E.g.
The standard upgrade process is:
Update the files. If you are using git, this will be something like git checkout REL1_32. If you are using a tarball, you can just uncompress it over an old one (although for a live server a better approach is to have a separate directory for the old and new version, and use symlinks to swap them out so it's fast and easy to ...