> Platonides wrote:
> No. Only those (and all of them) that contain another $wgVariable into
> its default value.
OK, that makes sense now, thanks for the explanation.
> I think it is only confusing if you look at DefaultSettings expecting to
> see the default there and can't find it.
I think that's a separate issue, but it certainly is making things worse.
Let's see if I understand correctly:
1. DefaultSettings.php is run. Here all variables are set to the
default values, *except* those that are dependent on other variables,
which are set to false (as a placeholder).
2. LocalSettings.php is run. Here users can set any variables to
whatever they like.
3. Setup.php is run. Here any variables that are dependent on other
variables *and* that have not been customised in LocalSettings.php are
set to their default value, based on other variables that may or may
not have been changed in LocalSettings.php
If this is correct, I think the documentation does not make it clear.
Here are the changes I propose.
DefaultSettings.php, line 10, reads
* Note that since all these string interpolations are expanded
* before LocalSettings is included, if you localize something
* like $wgScriptPath, you must also localize everything that
* depends on it.
If my understanding is correct, then this is not only confusing, it is
wrong. I propose something like the following instead
* In this file, variables whose default values depend on other
* variables (for example $wgStylePath, which defaults to
* "{$wgScriptPath}/skins") are set to false.
* The sequence of execution is DefaultSettings.php >
LocalSettings.php > Setup.php
* The actual default value of these variables will only be set in Setup.php,
* taking into account any custom settings performed in LocalSettings.php.
Also in DefaultSettings.php, I propose changing these comments
$wgStylePath = false; ///< defaults to "{$wgScriptPath}/skins"
to something like
$wgStylePath = false; ///< will default to
"{$wgScriptPath}/skins" in Setup.php
Here there is a minor point of mantainability, in that if the default
value changes we need to change it both in Setup.php,
DefaultSettings.php and on the Manual page in MediaWiki's wiki. Let's
sidestep this issue for now.
Then there are the Manual pages. I propose the following note is
included in the Manual pages *of each variable* that has this
behaviour.
<small>(Note: Since the defult value of this variable depends on other
variables, such default value is set in Setup.php, after
LocalSettings.php is executed)</small>
If there are no objections, I'm happy to apply the changes to the
Manual. For the code comments, please let me know how to submit the
patches.
Thanks.
Hi, I wonder why one of my website suddenly shows the following on the
article page when I put in a thumbnail. The message is: "Retrieved
from [whatever the image page is]. Also, the image page shows:
* File
* File history
* File links
* Metadata
at the top of the image page. Did I accidentally change my settings?
--
PM Poon
* http://dummipedia.org The 5-Minute Concise Encyclopedia
* http://dummipedia.com The Dummipedia Amazon Online Store
Hi,
Sessions fail on my wiki for some reason. I get the following error
message:
Sorry! We could not process your edit due to a loss of session data.
I verified the rights-settings of the session dir:
mauer:/var/log/apache2# ls -lad /var/lib/php5
drwx-wx-wt 2 root root 4096 2009-11-14 19:16 /var/lib/php5
Also, other php applications can create sessions just fine! e.g.
gallery2 keeps its sessions. In the error-log of the wiki no errors
appear.
Using mediawiki 1.15.1
Anyone got a suggestion what could be the cause?
Folkert van Heusden
--
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
Hi All,
I would like to be able to monitor the traffic of my wiki (powered by
mediawiki). I attempted to use google analytics, but could not successfully
install the traffic code.
Could anyone provide me with information that could either
1) Help me to successfully install the google analytics traffic code on
my wiki pages
2) Or provide an alternative solution to monitoring traffic on my wiki
Thanks!
Sharon
Hi all,
I've found the solution to my question myself:
after cloning the server I just had to add a new database via phpMyAdmin, Re-run
the installer and change the corresponding entries in LocalSettings.php. :-)
Greetings Katharina
Katharina Wolkwitz schrieb am 12.11.2009 11:46:
> Hi all,
>
> I'm toying with the idea to set up a new wiki-server for a new wiki by cloning
> my existing virtual machine and thus getting all the configuration in one go.
>
> The "only" problem is, that the new wiki should be empty of any content from the
> "old" wiki, so I'm looking for a way of cleaning out the entire content and
> users from the cloned wiki-installation. Any suggestions?
>
> I know that this approach is rather unusual, because otherwise I'd found more
> helpful information via Google ;-), but I think it would save a lot of time in
> contrast to starting the new server and mediawiki-installation from scratch.
MediaWiki version: 1.15.1
PHP version: 5.3.0
MySQL version: 5.1.37
URL: N/A (localhost)
I'm using XAMPP 1.7.2 When I'm editing an article and then navigate to an
new page and afterwards press back the content that I edited reverts to the
version before the edit. Also when pressing back after pressing Show preview
I get a session timeout error.
This doesn't happen on the official English Wikipedia.
Can you help me fix this?
Reading "The Art of Unix programming" I was thinking to use a
professional way to do versioning inside mediawiki.
Why not to use git inside?
Another my pb is working offline, writing readme guide of my linux
embedded setup.
I'd like to write it on my pc and than do git push to send to mediawiki server.
But git is good to do it, because I can manage merges.
It is possible to do it?
How much work can be estimated?
--
www.opensurf.it
Hi,
I've setup a Mediawiki which mirrors part of another german mediawiki.
Therefore I download the pages and try to upload them in my wiki.
For doing the upload I use a perl program and the Perl package
CMS::Mediawiki. Everythings wents well as long as the names of the pages
are standard ASCII, but since I mirror a german mediawiki some pages
contain german umlauts. Prefetching the pages, e.g. with
GET
http://mars.wiwi.hu-berlin.de/mediawiki/statistik/index.php?title=%C3%84hnl…
delivers me the right page. But if I try to update the page via
POST
http://mars.wiwi.hu-berlin.de/mediawiki/statistik/index.php?title=Ähnlichke…
it changes the page
http://mars.wiwi.hu-berlin.de/mediawiki/statistik/index.php/%C3%83%C2%84hnl…
Using
POST
http://mars.wiwi.hu-berlin.de/mediawiki/statistik/index.php?title=%C3%84hnl…
delivers me a "Original title: Spezial:Badtitle" error.
So, my questions are:
11) Has someone used successfully another software to upload pages with
german umlauts from files (it can be in any programming language :)
2.) Has someone successfully used CMS::Mediawiki, encountered the same
problem and found a solution?
3.) Maybe someone has an idea what went wrong and can tell me.
Thanks in advance
Sigbert Klinke
Platonides wrote:
> I see what you mean. I don't think this can be "fixed", since you need
> to wait after LocalSettings has been included to set those variables
> which rely on other variables. So that leaves us with the option of
> clarifying the documentation. As someone who has fallen on it, how do
> you think it would be expressed to note that the default value that we
> are reporting on those pages won't be effective until after
> LocalSettings execution?
Thanks for listening.
I suppose a template with an appropriate wording, applied to all such
$wgVariables that have this funny default behaviour, would be good.
Mr.Z-man recently had a stab at this with
http://www.mediawiki.org/wiki/Manual:$wgLogo
<small>(note: set dynamically in Setup.php, not in
DefaultSettings.php)</small>
but to be honest I'm not sure if that clarifies the whole situation.
I would like to take one step back and ask a couple of questions
1. Do all $wgVariable defaults behave this way, or are there two kinds
of defaults, one that gets set before LocalSettings and one after?
2. In any case, who is actually interested in the latter class (i.e.
default values that are set *after* LocalSettings)? From my short
experience, the average installer and admin is not. Maybe we need to
make it clear that these default values are for use of extension
developers (just guessing here) as opposed to administrators. In fact,
if this is the case, then I would probably remove altogether this
confusing default documentation from what is the *user* (i.e. admin)
manual of MediaWiki - as opposed to what would be a developer's
manual.
Then of course we need to make sure that there are no inappropriate
references to these variable in prominent documents like the FAQ etc.
By inappropriate I mean stuff like the first block removed with this
change
http://www.mediawiki.org/w/index.php?title=Manual%3AFAQ&action=historysubmi…
Thanks
According to http://www.mediawiki.org/wiki/Manual:$wgScriptPath
the default value for $wgScriptPath is '/wiki'. Why isn't it
'dirname($_SERVER['SCRIPT_NAME'])'? I can then move the content in
my wiki around my website without having to update $wgScriptPath on
every move (?). Or am I missing something? I've set it in
LocalSettings.php and seems to work ok...