Добрый день, могу я внести свою википедию в поисковик?
Project:Support desk
Hello
Dear Madams and Sirs,
Attentions
Alll wrong decisions and all wrong laws as chosen ideas of people and all wrong educations systems and all wrong types of ideas reffering to all nations have been and are and will be thier own unhealthy chosen decisions as generations of all generations . They should not at all chosen unhealthy decisions and countinuely with thier selfishnesse denying and justifying themselves as nations of Roman Empire , Greece, Italy, Spain , Romania, Egypt , France , aTurkey , China , Japan , Korea, Iran- Persia , African countries, Australia, Newzeland, Lebenan , Auutria, Greece, Tiland m Tiwan , African countries, Sweden , Switzerland, Finland , Denmark , India, Pakesyan , Afghanistan, all other too
I did move the MW to new hosting account (same php version, 7.4.33) and upgrade relatively successfully. (copy DB, upload new MW files (1.40.1) and execute mw-config/index.php)
and all articles looks well-opened but when I open Special:Version, it makes error below.
Warning: is_readable(): open_basedir restriction in effect. File(/gitinfo/info.json) is not within the allowed path(s): (/var/www/clients/client338/web1632/web:/var/www/clients/client338/web1632/private:/var/www/clients/client338/web1632/tmp:/var/www/smile.sfuhost.com/web:/srv/www/smile.sfuhost.com/web:/usr/share/php5:/usr/share/php:/tmp:/usr/share/phpmyadmin:/etc/phpmyadmin:/var/lib/phpmyadmin) in /var/www/clients/client338/web1632/web/includes/GitInfo.php on line 173
Warning: is_readable(): open_basedir restriction in effect. File(/gitinfo/info-skins-MinervaNeue.json) is not within the allowed path(s): (/var/www/clients/client338/web1632/web:/var/www/clients/client338/web1632/private:/var/www/clients/client338/web1632/tmp:/var/www/smile.sfuhost.com/web:/srv/www/smile.sfuhost.com/web:/usr/share/php5:/usr/share/php:/tmp:/usr/share/phpmyadmin:/etc/phpmyadmin:/var/lib/phpmyadmin) in /var/www/clients/client338/web1632/web/includes/GitInfo.php on line 173
(the rest omitted)
I tried to find answers and added '$wgGitBin = false;' on LocalSettings.php but it didn't help. is there any other method to solve this? I cannot edit 'php.ini' because server isn't mine.
Thank you in advance.
The file for "chunk" could not be stored for processing due to a server misconfiguration (write failed).
I want to use replace an existing website with mediawiki, but to preserve incoming links I need to remove some path names using .htaccess
So https://subbrit.org.uk/sites/fan-bay-deep-shelter should become https://subbrit.org.uk/fan-bay-deep-shelter, ditto features and a few more
I already use the shortURL logic to shorten paths
LocalSettings.php
$wgScriptExtension = ".php"; $wgArticlePath = "/$1"; $wgUsePathInfo = true; $wgScriptPath = "";
.htaccess
RewriteEngine On RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d RewriteRule ^(.*)$ %{DOCUMENT_ROOT}/index.php [L]
But my attempts to add new rules like
RewriteRule ^sites/(.*)$ /$1 [L]
just don't take effect, it just asks if I want to create a new page Sites/fan-bay-deep-shelter. The rules do work on the server away from the wiki area
I've not checked but how about putting the "sites" line as the first thing after "RewriteEngine On"?
In addition to putting it first, i would suggest using [R] instead of [L] to make it an http redirect.
See
https://httpd.apache.org/docs/2.4/rewrite/flags.html for what that does
Moving the line around and changing the flags doesn't help, I suspect that the problem is that the rewrite does not fundamentally change the URI Mediawiki processes, this is after all why
RewriteRule ^(.*)$ %{DOCUMENT_ROOT}/index.php [L]
can work. I fear there are many thousand #REDIRECTs in my future
In throry the [R,L] flag should change the url mediawiki processes because it should restart the request
I'm having no luck with placing the command, or using the PT flag which should change the URI. I've asked for help in https://www.mediawiki.org/wiki/Manual_talk:Short_URL/Apache, as there are statements there about REQUEST_URI which I think is the source of my problem
I've got the same $wgArticlePath and $wgScriptPath settings as you, and the same original four lines in .htaccess. In between "RewriteEngine On" and the rest, I have "RewriteRule" lines. One ends with "[R=301,L]" and another "[R=301,NC,L]". Don't ask me what "NC" means now, but it all seems to work all right!
There's a non-.htaccess way of organising redirects. Maybe your Apache is not set up to obey .htaccess, and you had previously got short URLs to work the other way. That might explain why your changes are having no effect. How about removing the original four lines, or adding something simple but absurd, and seeing whether it changes anything.
NC is case insensitive. I can see the rule changing things if I disable the conventional shortening logic, its the combination that doesn't work. I checked, the apache server configuration on my test machine is clean. a server conf solution wouldn't be acceptable for the production solution anyway, as that's hosted.
What are the full contents of your .htaccess now?
RewriteEngine On RewriteRule ^Sites/(.*)$ /$1 [NC,R] RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d RewriteRule ^(.*)$ %{DOCUMENT_ROOT}/index.php [L]
What about changing the flags on the second line to "[R=301,NC,L]"?
Internal server error with the 301, with either L (which stops the rewrites, which I'm sure I don't want) or R
You say either L or R, but what about trying both, as suggested?
I've tried the following out and it works for me, e.g. it'll show example.com/Main_Page as normal, and will also convert example.com/sites/Main_Page to example.com/Main_Page.
RewriteEngine on
RewriteRule ^sites/(.*)$ /$1 [R=301,NC,L]
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteRule ^(.*)$ %{DOCUMENT_ROOT}/index.php [L]
There must be something different about your server if that doesn't work.
I'm getting caught up with caches on my local webserver and different browsers. Sometimes it works, sometimes not. I will check on the production webserver and report back.
Seems to be working with a clean install on my production server. Thank you both for your help
I'm having a little problem after moving a wiki.
My hoster limited the number of subdomains, which is why I had to move my wiki (version 1.34.1.)
MySQL (5.7.42-0ubuntu0) and PHP version (7.4.33) are identical. I wanted to upgrade PHP to 8.x after the move.
So I copied all the files from the server to my computer using FTP and then uploaded them to the new folder on the same virtual server.
Old address: http://wiki.mydomain.de (subdomain must be removed by the end of the year)
New address: http://subdomain.mydomain.de/wiki (subdomain already existed and will be kept)
If I create an HTML file in the new server path and connect to it with a browser, the page displays without any problems. I checked this first before continuing.
Then I corrected the path for $wgServer to “http://subdomain.mydomain.de/wiki” in LocalSettings.php
If I rename the HTML file, the browser uses the index.php from MediWiki and something is displayed, but without any formatting (complete CSS is missing). Tried with Edge and Mozilla, both show the same error.
There is also a message that the wiki can only be viewed after logging in, which is how it was configured.
But the links on the homepage all point to "http://subdomain.mydomain.de/..." instead of "http://subdomain.mydomain.de/wiki/..." somehow the wiki subdirectory doesn't appear to be known even though the LocalSettings.php has been changed. Of course, all links bring a 404 error too.
Everything still works fine at the old address.
Quick help would be great!
Thank you very much and have a nice weekend
Hello
I tried to upgrade from 1.39 to 1.40.1
I published all the 1.40 files on top of my 1.39 installation as I usually did.
However, I'm getting a lot of errors.
Can anyone help?
You can see the errors list at https://www.gennievre.net/wiki/index.php?title=Accueil
I don't know. They say it's better not to add the new files over the existing ones. Maybe try again without doing that? What other steps did you take when upgrading?
Thanks for this reply, I'll try to get my backup back online. And redo a different installation.
This looks like a missing composer package. You did not (correctly) update the vendor directory most likely.
Thank you for your reply, but I don't know how to correct it. Do you have a suggestion?
This rings a bell. Once I decided to use git for MediaWiki core. I think the vendor directory is in the tarball but with git you have to run an extra command using composer. There's a page here: Download from Git. I now just use the tarball, extract it into a new folder, then copy across the old files I still need.
Thank you for this reply, but I don't understand the answer. I downloaded a zip archive which decompressed without any error message and I published it using ftp.
This is based on what I'd try rather than what I know, but if doing from scratch (without overwriting the existing files) doesn't work, maybe try disabling all your extensions. You might get some ideas at Manual:Upgrading.
Hello
Where can I find the step-by-step process for upgrading from version 1.39 to version 1.40.1 without taking any risks?
Windows PC + Filezilla
--------------------
Mise à niveau mediawiki
Où puis-je trouver le processus pas à pas pour passer de la version 1.39 à la version 1.40.1 sans prendre de risques ?
PC sous Windows + Filezilla
wikis typically have like custom stuff in the sidebar to take you to certain pages like certain categories, how would i go about doing this for my wiki (i use miraheze)