Re: [MediaWiki-l] New Wikipedia interface, is it the right place to ask?
Ba Menda via MediaWiki-l a écrit, le mardi 20 octobre 2020 à 15:13:51 :
> i don't know what you're talking about
That is normal, I hadn't asked my question.
I wrote it on the talk page indicated by Amir Aharoni, thanks for the link!
I copy it here, just so that you know what I'm talking about, no special need
to reply :
I'm blind and using lynx.
So, first of all, I would like to thank mediawiki developers for the great
level of accessibility of wikimedia.
Then you may place yourself in the context of non-visual rendering and no fast
track to browse the screen with the eyes but search line by line for the
relevant content.
With the old skin, in this context, the content used to start on the first
screen, not right at the beginning nor at the end of it, so it required some
research to find the exact place, but it was always on the first screen.
With the new skin, it starts further, often on the fifth screen, which means I
have to pres 4 times on PageDown to go on the screen where the article begins
and then browse line by line with my braille device to find the exact place.
Pressing 4 times PageDown isn't a problem in itself, although it's less
friendly than before, but the article doesn't always begin in the 5th screen.
For example, on the French Wikipedia, if I open the page "Jimi Hendrix", it
starts on the 12th screen, so it starts to make it painful to find the
beginning of the article, because we never exactly know.
I probably could change this behaviour in my preferences, but, will it work if
I'm not logged in? and I think it could be solved another way.
Indeed, I wanted to use the "Aller au contenu" ("Go to content") link, which
points to
https://fr.wikipedia.org/wiki/Jimi_Hendrix#content
but it just brings me to the very beginning of the page.
If there is a way to make this link work, with lynx, it would be, for me at
least, for others I hope, an even more convenient way than with the old skin.
Pascal
>
> On Monday, October 19, 2020, 2:16:11 p.m. EDT, יגאל חיטרון
> wrote:
>
> Hi there.Try to uncheck "Use Legacy Vector"on
> https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-rendering.Igal
> (User:IKhitron)
>
> בתאריך יום ב׳, 19 באוק׳ 2020 ב-19:21 מאת Pascal GREGIS
> <gra...@free.fr>:
>
> Hello,
>
> I noticed that recently the interface of the french wikipedia had changed.
> Surprisingly, it doesn't seem to be the case on the english wikipedia.
> Is it the right place here to make some remarks about it?
>
> Thanks
>
> Pascal
>
> - End forwarded message -
>
> ___
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
> ___
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
> ___
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] New Wikipedia interface, is it the right place to ask?
Hello, I noticed that recently the interface of the french wikipedia had changed. Surprisingly, it doesn't seem to be the case on the english wikipedia. Is it the right place here to make some remarks about it? Thanks Pascal - End forwarded message - ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Restoring a mediawiki site
Thank you Greg for the tip, I'll try it as sonn as I'll have time again for this issue. Regards Pascal eQuality Technology a écrit, le vendredi 31 juillet 2020 à 15:23:48 : > Pascal, > > I suggest using MediaWiki Vagrant [1] as the simplest method for setting up > a local MediaWiki environment. It may be all new to you, but it should > "just work" and you'll save yourself lots of headaches trying to install > and manage things separately. Once you have MediaWiki Vagrant setup, you > should be able to load your database backup, LocalSettings.php, and images > so that you have a good working development environment. > > [1] https://www.mediawiki.org/wiki/MediaWiki-Vagrant > > ~ Greg > > eQuality Technology > > *Let's work together* > > https://equality-tech.com > follow us: https://twitter.com/eQualityTech > *creators of https://QualityBox.us <https://QualityBox.us> * > > > On Fri, Jul 31, 2020 at 2:18 PM Pascal GREGIS wrote: > > > Hi, > > > > Tnaks Brian. > > Unfortunately I don't have access to the server, only via http and ftp. > > So I guess the best I could do in a first time would be to set up an > > Apache + MySQL installation on my computer to restore my wiki and test the > > restoration locally. I have been reluctant to do it until now because I'm > > not cumfortable with setting up Apache, I have some souvenirs of it being > > quite painful but hopefully my souvenirs have no reason to be. > > If it comes to work and my restoration to be all right, I would be > > reassured to know that my backups are valid and complete and give me time > > to find a solution to the restoration part. > > Just one thing, do you confirm that xml dumps are of no use for my backup > > / restore issue ? > > > > And yes, I know there are some other elements to backup, already done for > > the LocalSettings, and to be done for images and extensions but it's not a > > big issue in my case, I have very few. > > > > Regards > > > > Pascal > > > > Brian Wolff a écrit, le jeudi 30 juillet 2020 à 03:52:43 : > > > It sounds like there was some error during the import process, and your > > db > > > wasnt fully imported (at the very least an index was missing). Its also > > > possible that maybe the export didnt include indicies (i dont know what > > > phpmyadmin does by default. It might be optional) > > > > > > If possible i would suggest using the mysql command line client to do the > > > import, and commandline mysqldump to make the backup. > > > > > > > > > Additionally dont forget for a complete backup you also need to backup > > > LocalSettings.php and the images subdirectory (and maybe extensions > > > subdirectory) > > > > > > -- > > > Brian > > > On Monday, July 13, 2020, Pascal GREGIS wrote: > > > > > > > Hello, > > > > > > > > I have tried to restore one of my wiki sites for testing, because I've > > > > always learnt that a non-tested backup is a useless backup. > > > > > > > > I have exported my database named pascal_wikidb using phpmyadmin on my > > > > host site and obtained an sql file. > > > > Then I have tried to import this sql file on another database (on the > > same > > > > host site) named pascal_dbtest. I have had hard time doing it because > > the > > > > import function of phpmyadmin doesn't work well with lynx, but that is > > > > another story. Using Firefox, I managed to do it still with an error > > > > message (I don't remember this message and I cannot reproduce easily > > this > > > > operation); so I wasn't sure my restoration was complete. > > > > I then imported pascal_dbtest and it sounded complete when looking at > > the > > > > sql file, except that there are only 5 "ALTER TABLE" in it, instaed of > > a > > > > few dozens in the file exported from pascal_wikidb. Anyway it's hard to > > > > compare at a manual glance. > > > > > > > > So I changed the LocalSettings.php of my wiki site to have it pointing > > on > > > > pascal_dbtest instead of pascal_wikidb : > > > > > > > > $wgDBname = "pascal_dbtest"; > > > > $wgDBuser = "pascal_testwiki"; > > > > $wgDBpassword = "Undiscloed_password" > > > > > > > > I opened my wiki with the normal URL, I managed to log in, but I > > couldn't > > > > modify a
Re: [MediaWiki-l] Restoring a mediawiki site
Hi, Tnaks Brian. Unfortunately I don't have access to the server, only via http and ftp. So I guess the best I could do in a first time would be to set up an Apache + MySQL installation on my computer to restore my wiki and test the restoration locally. I have been reluctant to do it until now because I'm not cumfortable with setting up Apache, I have some souvenirs of it being quite painful but hopefully my souvenirs have no reason to be. If it comes to work and my restoration to be all right, I would be reassured to know that my backups are valid and complete and give me time to find a solution to the restoration part. Just one thing, do you confirm that xml dumps are of no use for my backup / restore issue ? And yes, I know there are some other elements to backup, already done for the LocalSettings, and to be done for images and extensions but it's not a big issue in my case, I have very few. Regards Pascal Brian Wolff a écrit, le jeudi 30 juillet 2020 à 03:52:43 : > It sounds like there was some error during the import process, and your db > wasnt fully imported (at the very least an index was missing). Its also > possible that maybe the export didnt include indicies (i dont know what > phpmyadmin does by default. It might be optional) > > If possible i would suggest using the mysql command line client to do the > import, and commandline mysqldump to make the backup. > > > Additionally dont forget for a complete backup you also need to backup > LocalSettings.php and the images subdirectory (and maybe extensions > subdirectory) > > -- > Brian > On Monday, July 13, 2020, Pascal GREGIS wrote: > > > Hello, > > > > I have tried to restore one of my wiki sites for testing, because I've > > always learnt that a non-tested backup is a useless backup. > > > > I have exported my database named pascal_wikidb using phpmyadmin on my > > host site and obtained an sql file. > > Then I have tried to import this sql file on another database (on the same > > host site) named pascal_dbtest. I have had hard time doing it because the > > import function of phpmyadmin doesn't work well with lynx, but that is > > another story. Using Firefox, I managed to do it still with an error > > message (I don't remember this message and I cannot reproduce easily this > > operation); so I wasn't sure my restoration was complete. > > I then imported pascal_dbtest and it sounded complete when looking at the > > sql file, except that there are only 5 "ALTER TABLE" in it, instaed of a > > few dozens in the file exported from pascal_wikidb. Anyway it's hard to > > compare at a manual glance. > > > > So I changed the LocalSettings.php of my wiki site to have it pointing on > > pascal_dbtest instead of pascal_wikidb : > > > > $wgDBname = "pascal_dbtest"; > > $wgDBuser = "pascal_testwiki"; > > $wgDBpassword = "Undiscloed_password" > > > > I opened my wiki with the normal URL, I managed to log in, but I couldn't > > modify any page, when I try I get : > > "Alert: HTTP/1.1 500 Internal Server Error" > > then (this is a translation back to english, sorry) > > « > > A database request error occured. It could have been caused by something > > wrong in the software. > > [1cd8b80a4379c26549677281] 2020-07-13 17:30:10: Fatal erreur of type > > "DBQueryError" > > » > > > > Is there any procedure to follow to restore a wiki installation from a > > database backup? > > Or is it likely to be caused by a corruption in my database backup? > > > > I precise that I almost eliminated the hypothesis of an error in the > > user's permissions on this database. > > > > Thanks in advance for any answer > > > > Regards > > > > Pascal GRÉGIS > > > > > > ___ > > MediaWiki-l mailing list > > To unsubscribe, go to: > > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l > > > ___ > MediaWiki-l mailing list > To unsubscribe, go to: > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Restoring a mediawiki site
/pascal.lautre.net/andrapal/includes/Media
Wiki.php(512): MediaWiki->main()
#12
/var/www/alternc/p/pascal/www/pascal.lautre.net/andrapal/index.php(43):
MediaWiki->run()
#13 {main}
»
This gave me the idea to go look in an export of my test database (the one who
fails, on which I had restored), if andrapalrevision existed and if the key
page_timestamp existed. I discovered that page_timestamp was in the 261 missing
ALTER TABLE (which are in the primary database but not in the text database).
So I guess the restoration is incomplete, maybe only these ALTER TABLE are
missing, taht would be why the pages are ok but the history is corrupt.
Halas I wasn't able to execute by hand these ALTER TABLE requests. I isolated
them in a file, and imported that file, but I got, after a very long time
processing :
«
Error
SQL Request:
ALTER TABLE `andrapalexternallinks`
ADD PRIMARY KEY (`el_id`), ADD KEY `el_from` (`el_from`,`el_to`(40)), ADD
KEY `el_to` (`el_to`(60),`el_from`), ADD KEY `el_index` (`el_index`(60));
MYSQL replied: Documentation
#1062 - Duplicate entry '1' for key 'PRIMARY'
»
I precise that this request is the first of the 261 requests in my file.
Well, I hope I wasn't too long. If you have any answers on this issue, I'm all
ears opened.
Regards
Pascal
Robert Vogel a écrit, le mardi 14 juillet 2020 à 05:59:36 :
> Hello!
>
> To get a more detailed error message, please set
>
> $wgShowSQLErrors = true;
> $wgDebugDumpSql = true;
> $wgShowExceptionDetails = true;
> $wgShowDBErrorBacktrace = true;
>
> in your `LocalSettings.php` file.
> Did you run `maintenance/update.php` on you new wiki? Maybe it's just a
> schema change that needs to be applied.
>
> Maybe these links are helpful:
>
> - https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki
> - https://www.mediawiki.org/wiki/Manual:Restoring_a_wiki_from_backup
> - https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script
>
> Good luck,
> Robert
>
> Am Montag, den 13.07.2020, 19:43 +0200 schrieb Pascal GREGIS:
>
> Hello,
>
>
> I have tried to restore one of my wiki sites for testing, because I've always
> learnt that a non-tested backup is a useless backup.
>
>
> I have exported my database named pascal_wikidb using phpmyadmin on my host
> site and obtained an sql file.
>
> Then I have tried to import this sql file on another database (on the same
> host site) named pascal_dbtest. I have had hard time doing it because the
> import function of phpmyadmin doesn't work well with lynx, but that is
> another story. Using Firefox, I managed to do it still with an error message
> (I don't remember this message and I cannot reproduce easily this operation);
> so I wasn't sure my restoration was complete.
>
> I then imported pascal_dbtest and it sounded complete when looking at the sql
> file, except that there are only 5 "ALTER TABLE" in it, instaed of a few
> dozens in the file exported from pascal_wikidb. Anyway it's hard to compare
> at a manual glance.
>
>
> So I changed the LocalSettings.php of my wiki site to have it pointing on
> pascal_dbtest instead of pascal_wikidb :
>
>
> $wgDBname = "pascal_dbtest";
>
> $wgDBuser = "pascal_testwiki";
>
> $wgDBpassword = "Undiscloed_password"
>
>
> I opened my wiki with the normal URL, I managed to log in, but I couldn't
> modify any page, when I try I get :
>
> "Alert: HTTP/1.1 500 Internal Server Error"
>
> then (this is a translation back to english, sorry)
>
> «
>
> A database request error occured. It could have been caused by something
> wrong in the software.
>
> [1cd8b80a4379c26549677281] 2020-07-13 17:30:10: Fatal erreur of type
> "DBQueryError"
>
> »
>
>
> Is there any procedure to follow to restore a wiki installation from a
> database backup?
>
> Or is it likely to be caused by a corruption in my database backup?
>
>
> I precise that I almost eliminated the hypothesis of an error in the user's
> permissions on this database.
>
>
> Thanks in advance for any answer
>
>
> Regards
>
>
> Pascal GRÉGIS
>
>
>
> ___
>
> MediaWiki-l mailing list
>
> To unsubscribe, go to:
>
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
>
> --
>
> Robert Vogel Team Lead Product and Software Development Hallo Welt! GmbH
> Postfach 11 02 09
93015 Regensburg Germany Telefon: +49 (0) 941 - 660 80-0
> Fax: +49 (0) 941 - 660 80-189 hallowelt.com vo...@hallowelt.com Sitz:
> Regensburg Amtsgericht: Regensburg Handelsregister: HRB 10467 E.USt.Nr.: DE
> 253050833 Geschäftsführer: Anja Ebersbach, Markus Glaser, Dr. Richard Heigl
> Besuchen Sie unsere aktuellen BlueSpice-Webinare:
> https://de.bluespice.com/webinar
> ___
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] Restoring a mediawiki site
Hello, I have tried to restore one of my wiki sites for testing, because I've always learnt that a non-tested backup is a useless backup. I have exported my database named pascal_wikidb using phpmyadmin on my host site and obtained an sql file. Then I have tried to import this sql file on another database (on the same host site) named pascal_dbtest. I have had hard time doing it because the import function of phpmyadmin doesn't work well with lynx, but that is another story. Using Firefox, I managed to do it still with an error message (I don't remember this message and I cannot reproduce easily this operation); so I wasn't sure my restoration was complete. I then imported pascal_dbtest and it sounded complete when looking at the sql file, except that there are only 5 "ALTER TABLE" in it, instaed of a few dozens in the file exported from pascal_wikidb. Anyway it's hard to compare at a manual glance. So I changed the LocalSettings.php of my wiki site to have it pointing on pascal_dbtest instead of pascal_wikidb : $wgDBname = "pascal_dbtest"; $wgDBuser = "pascal_testwiki"; $wgDBpassword = "Undiscloed_password" I opened my wiki with the normal URL, I managed to log in, but I couldn't modify any page, when I try I get : "Alert: HTTP/1.1 500 Internal Server Error" then (this is a translation back to english, sorry) « A database request error occured. It could have been caused by something wrong in the software. [1cd8b80a4379c26549677281] 2020-07-13 17:30:10: Fatal erreur of type "DBQueryError" » Is there any procedure to follow to restore a wiki installation from a database backup? Or is it likely to be caused by a corruption in my database backup? I precise that I almost eliminated the hypothesis of an error in the user's permissions on this database. Thanks in advance for any answer Regards Pascal GRÉGIS ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] MediaWiki 1.32 is End of Life
Isn't php 7.2.26 superior to 7.2.9? It looks pretty logical to me but maybe I haven't understood correctly what you mean. Pascal Peter Presland a écrit, le vendredi 24 janvier 2020 à 16:52:02 : > Per other replies about php version requirements and the putative > difficulties involved for Redhat OS users, I am left wondering about how > important the stated Mediawiki php version requirements really are. > > My wondering is prompted by the fact that both Wikipedia and the few > other MW foundation sites I have checked, are all running MW1.35.0 > while still on php 7.2.26. Whereas the stated php minimum version > requirement for the current latest stable MW1.34 is php 7.2.9. > > Probably a simple explanation but as a Centos 7 OS user, I am confused. > > Peter Presland > > On 23/01/2020 22:20, Jeffrey Walton wrote: > > On Thu, Jan 23, 2020 at 2:48 PM Sam Reed wrote: > >> As per the MediaWiki version life cycle [1], I would like to announce the > >> formal end of life (EOL) of MediaWiki 1.32 as of tomorrow, Friday January > >> 24, 2019. > >> > >> This means that MediaWiki 1.32 will no longer receive maintenance or > >> security backports. It is therefore strongly discouraged that you continue > >> to use it. > >> > >> It is recommended to upgrade to MediaWiki 1.34 (due to become EOL in > >> November 2020), or less preferably to MediaWiki 1.33 (due to become EOL in > >> June 2020). The current Long Term Support (LTS) version of MediaWiki, > >> MediaWiki 1.31, is older (and downgrading is not supported), though the > >> next LTS (MediaWiki 1.35) is due to be released in June 2020, and will be > >> supported until June 2023. > >> > >> MediaWiki 1.33 has the same supported PHP version of 7.0 (which is itself > >> unsupported upstream), in case you need longer to upgrade your systems. > >> MediaWiki 1.34 requires PHP 7.2.9 or later. > > This puts some folks in a bad position. > > > > The latest CentOS 7 does not support the versions of Python and PHP > > required, even with Software Collections (SCL) enabled. > > > > (In hindsight a Red Hat-based VM was a bad decision. It ships with > > antique software, and SCL only provides old software. We need modern > > software, and should have selected a Fedora or Ubuntu VM). > > > > Jeff > > > > ___ > > MediaWiki-l mailing list > > To unsubscribe, go to: > > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l > > ___ > MediaWiki-l mailing list > To unsubscribe, go to: > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Re: [MediaWiki-l] Help about running several wikis on a same installation
I should definitely have checked all this before installing, but I was such in a hury. As a result I lost hole days trying to work around. Halas now is a bit late for me to invest time in something new, unless it is really superquick to install and learn to use, but things are rarely superquick for blind people with lynx, and if I was sure It won't mess up with my first installations. Thanks Pascal eQuality Technology a écrit, le Thursday 12 December 2019 à 17:08:17 : > You could use the Meza [1] project to install your wiki environment for > you. Meza does wiki farms. Meza includes essentials like Visual Editor and > Elasticsearch so you can get down to using your wikis instead of building > them. > > 1. https://www.mediawiki.org/wiki/Meza > Full disclosure: I have contributed patches to Meza > > ~ Greg > > eQuality Technology > > *Let's work together* > > https://equality-tech.com > follow us: https://twitter.com/eQualityTech > *creators of https://QualityBox.us <https://QualityBox.us> * > > > On Thu, Dec 12, 2019 at 4:38 PM Brian Wolff wrote: > > > If symlinks aren't an option (It would be weird for a hosting provider to > > disallow that), you can probably use dummy php files that just load the > > real version of themselves. > > > > e.g. Have MediaWiki in a directory named mediawiki > > > > then in a different directory named andra have a file named index.php > > containing only > > > require "../mediawiki/index.php"; > > > > And do similar for load.php, and any other files ending in .php that are > > top-level in MediaWiki (e.g. api.php, load.php,etc. But only the top level > > ones, don't worry about the subdirectories). > > Then do the same thing for the other wikis you want to install in other > > directories. > > > > > > This should mostly just work (WMF wikis actually do something kind of like > > this, but for different reasons), although you will need to adjust > > $wgExtensionAssetsPath to be 'mediawiki/extensions'; If you enable uploads, > > you will need to make sure each wiki has a unique upload directory. > > > > -- > > Brian > > On Thu, Dec 12, 2019 at 9:28 PM Pascal GREGIS wrote: > > > > > Thank you Brian for the explanations. I d'ont have the courage anymore to > > > track down all the hardcoded index.php, and if you say it may be > > fragile, I > > > think I have no other option but to lose 1GB of my available space > > copying > > > mediawiki directory 4 or 5 times. > > > It would be nice however if possible to have other options for > > multiwikis, > > > as all hostings don't allow symlinks or subdomains / domain aliases. > > > > > > For ereg_replace, I don't know why preg_replace gave horrible results on > > > my server, but anyway, I should'nt need it anymore. > > > > > > Pascal > > > > > > Brian Wolff a écrit, le Thursday 12 December 2019 à 18:08:46 : > > > > It would be much better if you could use separate directories instead > > of > > > > renaming index.php. Renaming index.php is not really a supported > > > > configuration. There's the obvious problem of how do other scripts, > > like > > > > load.php know what wiki is being referred to. > > > > > > > > If you're really intent on doing this, You can try ensuring that > > > $wgScript > > > > is set appropriately for each wiki (E.g. $wgScript = '/w/andra.php'; > > for > > > > the andra one). However, there are probably places (especially for > > > > extensions) where index.php is hardcoded, and as i mentioned before, > > > there > > > > are other entry points then index.php like load.php and api.php which > > > will > > > > be confused by this. I expect that this setup will break in subtle > > ways. > > > > > > > > You would also have to ensure there are separate image directories for > > > each > > > > wiki or mediawiki will get confused. > > > > > > > > p.s. ereg_replace is being removed from php, you should use > > preg_replace > > > > instead. > > > > > > > > -- > > > > bawolff > > > > > > > > > > > > On Thu, Dec 12, 2019 at 5:54 PM Pascal GREGIS wrote: > > > > > > > > > Hello everyone, > > > > > > > > > > I have troubles running several wikis on a same installation. > > > > > In fact I cannot use neither symlinks nor subdomain re
Re: [MediaWiki-l] Help about running several wikis on a same installation
Thank you Brian for the explanations. I d'ont have the courage anymore to track
down all the hardcoded index.php, and if you say it may be fragile, I think I
have no other option but to lose 1GB of my available space copying mediawiki
directory 4 or 5 times.
It would be nice however if possible to have other options for multiwikis, as
all hostings don't allow symlinks or subdomains / domain aliases.
For ereg_replace, I don't know why preg_replace gave horrible results on my
server, but anyway, I should'nt need it anymore.
Pascal
Brian Wolff a écrit, le Thursday 12 December 2019 à 18:08:46 :
> It would be much better if you could use separate directories instead of
> renaming index.php. Renaming index.php is not really a supported
> configuration. There's the obvious problem of how do other scripts, like
> load.php know what wiki is being referred to.
>
> If you're really intent on doing this, You can try ensuring that $wgScript
> is set appropriately for each wiki (E.g. $wgScript = '/w/andra.php'; for
> the andra one). However, there are probably places (especially for
> extensions) where index.php is hardcoded, and as i mentioned before, there
> are other entry points then index.php like load.php and api.php which will
> be confused by this. I expect that this setup will break in subtle ways.
>
> You would also have to ensure there are separate image directories for each
> wiki or mediawiki will get confused.
>
> p.s. ereg_replace is being removed from php, you should use preg_replace
> instead.
>
> --
> bawolff
>
>
> On Thu, Dec 12, 2019 at 5:54 PM Pascal GREGIS wrote:
>
> > Hello everyone,
> >
> > I have troubles running several wikis on a same installation.
> > In fact I cannot use neither symlinks nor subdomain redirections to do it.
> > So I have tried a hand-mde solution with a copy of index.php.
> > i.e. : I want to run 4 wikis, that I have called :
> > - andra
> > - anthony
> > - nita
> > - crep
> >
> > To go to andra for example I type the address :
> > pascal.lautre.net/w/andra.php
> >
> > and I have created a LocalSettings-$wikiname.php for each of the 4 wikis,
> > setting a switch in the main LocalSettings.php to include the appropriate
> > one.
> > But I've got all my vairables and paths erased when the wiki redirects, it
> > calls index.php/Accueil for example and I have no way to know what was the
> > original call.
> > I have even tried to use a hook, the BeforePageRedirect hook, but it
> > worked only for loading the Accueil page (I guess it would be called HOme
> > in english, or Welcome), after, I have the problem again when I try to
> > connect, the link points to index.php instead of andra.php.
> >
> > Here is the code of my LocalSettings.php:
> >
> > >
> > $ppw = "/w";
> > if (! isset($pascal_request_uri)) {
> > $pascal_request_uri = split("/", $_SERVER['REQUEST_URI'])[2];
> > }
> >
> > $wgHooks['BeforePageRedirect'][] = function ($out, &$redirect, &$code) {
> > GLOBAL $pascal_request_uri;
> > GLOBAL $ppw;
> >
> > $redirect = ereg_replace("/index.php", "/$pascal_request_uri",
> > $redirect);
> > return true;
> > };
> >
> > switch ($pascal_request_uri) {
> > case "andra.php":
> > case "anthony.php":
> > case "nita.php":
> > case "crep.php":
> > require_once("LocalSettings-$pascal_request_uri");
> > break;
> > default:
> > echo "NO wiki specified. please choose a wiki, ex: \n";
> > echo $_SERVER['SERVER_NAME'] . "$ppw/idees.php\n";
> > exit(1);
> > }
> >
> > Thank you for any help!
> >
> > Pascal
> >
> > ___
> > MediaWiki-l mailing list
> > To unsubscribe, go to:
> > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
> >
> ___
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
___
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[MediaWiki-l] Help about running several wikis on a same installation
Hello everyone, I have troubles running several wikis on a same installation. In fact I cannot use neither symlinks nor subdomain redirections to do it. So I have tried a hand-mde solution with a copy of index.php. i.e. : I want to run 4 wikis, that I have called : - andra - anthony - nita - crep To go to andra for example I type the address : pascal.lautre.net/w/andra.php and I have created a LocalSettings-$wikiname.php for each of the 4 wikis, setting a switch in the main LocalSettings.php to include the appropriate one. But I've got all my vairables and paths erased when the wiki redirects, it calls index.php/Accueil for example and I have no way to know what was the original call. I have even tried to use a hook, the BeforePageRedirect hook, but it worked only for loading the Accueil page (I guess it would be called HOme in english, or Welcome), after, I have the problem again when I try to connect, the link points to index.php instead of andra.php. Here is the code of my LocalSettings.php: NO wiki specified. please choose a wiki, ex: \n"; echo $_SERVER['SERVER_NAME'] . "$ppw/idees.php\n"; exit(1); } Thank you for any help! Pascal ___ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
