headers
Derrick Farnell | 1 Jun 2008 09:24
Picon

Re: value displayed by {{NUMBEROFEDITS}} doesn't change after edits

I've just been told that having "$wgEnableParserCache => false;" in
LocalSettings.php will significantly slow-down the site if it ever has more
than a few users, which is why parsercaching exists in the first place - not
that I know what 'parsercaching' is myself!

On Sat, May 31, 2008 at 8:18 PM, Derrick Farnell <derrick.farnell@...>
wrote:

> Great.
>
>
> On Sat, May 31, 2008 at 8:11 PM, Darren VanBuren <onekopaka@...>
> wrote:
>
>> No, there should be no downsides.
>> On May 31, 2008, at 12:02 PM, Derrick Farnell wrote:
>>
>> > P.S. Are there any downsides, of any kind, of having
>> > "$wgEnableParserCache =
>> > false;" in LocalSettings?
>> >
>> >
>> > On Sat, May 31, 2008 at 6:57 PM, Derrick Farnell <
>> derrick.farnell@...
>> > >
>> > wrote:
>> >
>> >> Yes, I've tried it and not noticed a reduction in speed. Thanks.
>> >>
>> >>
(Continue reading)

Permalink | Reply | 2 comments |
headers
DanTMan | 1 Jun 2008 09:46

Re: value displayed by {{NUMBEROFEDITS}} doesn't change after edits

The parsercache is a cache which saves the parsed state of a page after 
MW has parsed it, and it's retrieved from the cache instead of being 
reparsed on each page view, up until the page is saved again, a or the 
job que or a user purges it.

Believe it or not, but MediaWiki's parser is NOT fast. It is quite 
inefficient, it's a big kludge made up of a huge pile of regexes and 
other stuff. Not to mention that things like #ifexist and other things 
end up doing a costly query to the database. Which in itself is 
something that can quickly slow down a site by doing to many of those on 
every page view.

~Daniel Friesen(Dantman) of:
-The Gaiapedia (http://gaia.wikia.com)
-Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG)
-and Wiki-Tools.com (http://wiki-tools.com)

Derrick Farnell wrote:
> I've just been told that having "$wgEnableParserCache => false;" in
> LocalSettings.php will significantly slow-down the site if it ever has more
> than a few users, which is why parsercaching exists in the first place - not
> that I know what 'parsercaching' is myself!
>
>
> On Sat, May 31, 2008 at 8:18 PM, Derrick Farnell <derrick.farnell@...>
> wrote:
>
>   
>> Great.
>>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Derrick Farnell | 1 Jun 2008 10:57
Picon

Re: value displayed by {{NUMBEROFEDITS}} doesn't change after edits

I see - thanks for explaining that, which also explains why disabling the
parsercache isn't a good idea if you have more than a few users using the
wiki at the same time.

On Sun, Jun 1, 2008 at 8:46 AM, DanTMan <dan_the_man@...> wrote:

> The parsercache is a cache which saves the parsed state of a page after
> MW has parsed it, and it's retrieved from the cache instead of being
> reparsed on each page view, up until the page is saved again, a or the
> job que or a user purges it.
>
> Believe it or not, but MediaWiki's parser is NOT fast. It is quite
> inefficient, it's a big kludge made up of a huge pile of regexes and
> other stuff. Not to mention that things like #ifexist and other things
> end up doing a costly query to the database. Which in itself is
> something that can quickly slow down a site by doing to many of those on
> every page view.
>
> ~Daniel Friesen(Dantman) of:
> -The Gaiapedia (http://gaia.wikia.com)
> -Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG)
> -and Wiki-Tools.com (http://wiki-tools.com)
>
> Derrick Farnell wrote:
> > I've just been told that having "$wgEnableParserCache => false;" in
> > LocalSettings.php will significantly slow-down the site if it ever has
> more
> > than a few users, which is why parsercaching exists in the first place -
> not
> > that I know what 'parsercaching' is myself!
(Continue reading)

Permalink | Reply | 0 comments |
headers
Derrick Farnell | 1 Jun 2008 11:05
Picon

Re: problems with 'Variables' extension

That works - thanks!

Derrick

On Sat, May 31, 2008 at 10:27 PM, Platonides <Platonides@...> wrote:

> Derrick Farnell wrote:
> > then it doesn't work - the layout of the wiki pages just becomes a bit
> > broken-up and there are several lines of code superimposed along the top
> of
> > every page.
>
> Those lines are errors. giving out what they said would be very helpful
> to diagnose it. Although if what you were including didn't begin with
> <?php, it's probably that.
>
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l@...
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
Permalink | Reply | 0 comments |
headers
Rein | 1 Jun 2008 13:01
Picon
Favicon

links navigation bar not working in Ferefox

I installed Wiki again, and now the problem is gone.
But I still can't figure out what caused it, because the sidebar is exactly the same, and all scripts and
extra lines in monobook.php (in connection with the sidebar) had been removed.
It makes you uneasy to change anything again.
And why problems in Firefox and not in Explorer?
Rein
Permalink | Reply | 1 comment |
headers
Alain | 1 Jun 2008 13:21
Picon
Favicon

Re: links navigation bar not working in Ferefox

Hi,

Next time copy the monobook skin to a new skin and edit that. That way 
you can always just switch back.

Alain

Rein wrote:
> I installed Wiki again, and now the problem is gone.
> But I still can't figure out what caused it, because the sidebar is exactly the same, and all scripts and
extra lines in monobook.php (in connection with the sidebar) had been removed.
> It makes you uneasy to change anything again.
> And why problems in Firefox and not in Explorer?
> Rein
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l@...
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
>
Permalink | Reply | 0 comments |
headers
Daniel Barrett | 1 Jun 2008 15:44
Favicon

Protected titles howto?


How do you enable MediaWiki's "native protection of nonexistent pages"
mentioned at:

http://www.mediawiki.org/wiki/Project:Protected_titles#Method_1:_Protecting_a_nonexisting_page_.28preferred.29

I've searched meta and mediawiki.org but can't seem to find the
instructions.

I thought it might involve the page MediaWiki:Titleblacklist, but when I
add entries, they don't seem to have an effect (1.13 alpha).  Also
http://meta.wikimedia.org/wiki/Help:Special_page#Protected seems to imply
this system message is just an alternate method.

Thanks!
DanB
Permalink | Reply | 1 comment |
headers
Rein | 1 Jun 2008 15:48
Picon
Favicon

change position navigation bar

Thank you, Alain, 
"#column-one" was indeed what I was looking for.Lowering the personal also (p-personal) gave a much nicer
look.It meant that p-cactions had to be lowered, and the content need a top as well.This way I was able to
align the logo with the tabs.
Permalink | Reply | 0 comments |
headers
Rein | 1 Jun 2008 15:54
Picon
Favicon

links navigation bar not working in Ferefox

That wasn't the problem actually: I always keep a file which isn't changed.
I think the working with Mediawiki:sidebar did the damage, in combination with the change of monobook.php.
Why it could not be reserved I don't know (I changed monobook.php back off course).
What struck me before is that the JavaScript suggestions on the monobook.js page didn't work either.
But if you have trouble with the navigation links in Firefox you know what to do.
Rein
Permalink | Reply | 0 comments |
headers
LeLorrain | 1 Jun 2008 17:31

upload form

Hi,

Is there a way to do a custom upload form which would replace the native 
one?

Ludo
Permalink | Reply | 2 comments |

Gmane