1 Mar 2005 01:16
1 Mar 2005 07:10
Re: blog extension
Hi François, I don't quite follow what it does. Could you elaborate? By the way, I saw on your wiki that you have a [comment] link next to each section. That's a nice touch. Would you mind explain how to add that? (I suppose it involves some php hacking.) thanks, -- John FxParlant wrote: > Hello all, > > I've made a little clumsy extension to help aggregating quotes: so > that a quote appears in all the pages it links to. > > http://meta.wikimedia.org/wiki/User:Fxparlant/Blog > > Please do use of the discussion page to comment and help me correct it >(Continue reading)> > To see a first version of its use : > > http://www.fxparlant.net/Lacan_S1 > Scroll down after the dates list, and you'll see an aggregation of > notes, with links for pages and comments (some of these pages are > themself aggregations)
1 Mar 2005 08:01
Re: blog extension
> I've made a little clumsy extension to help aggregating quotes: so > that a quote appears in all the pages it links to. > http://meta.wikimedia.org/wiki/User:Fxparlant/Blog I like this feature, plus the dynamic menu. And as a phenomenologist, I like also the topics of the site.See, however, this displacement http://www.fxparlant.net/Category:Vocabulary P.
1 Mar 2005 17:02
Disable all caching?
Hi. Im running mediawiki (CVS version) and i have som innoing problems .. I update my ur_rights in the database to reflect that I want to be "sysop" but everytime i actually tries to use it( or login/logout) the entry in the database gets automatically set back to "read,edit,move,upload" again. update user_rights set ur_rights = 'read,edit,move,upload,sysop' where ur_user= 3; Jesper -- -- ./Jesper Krogh, jesper@..., Jabber ID: jesper@... Danmark har fået sit eget Mozillaforum: http://forum.mozilladanmark.dk/ eller nntp://news.sslug.dk/mozilladanmark.*
1 Mar 2005 18:09
Re: Caching is making me crazy...
On Mon, 28 Feb 2005 22:22:25 +0100, Sebastien BARRE <sebastien.barre@...> wrote: > At 2/28/2005 07:58 PM, Rowan Collins wrote: > > >The point is, this is a chicken-and-egg problem - if the page is being > >read from cache, there is no way of knowing whether or not it contains > >an extension tag, or any other feature. > > Unless I'm missing something, it does seem possible to me, I'm pretty sure > it's done for other features: when you edit the page and save it, it is > parsed and tables in the database are modified accordingly. For example, > the links, categorylinks, imagelinks tables, etc. So at that time, you can > detect an extension tag in the page, and fill an extensionlinks table for > example, with ids of the pages using extensions. You don't even need to > actually refer to any extension, so it would basically be one column if > needed. When it's time to serve the page, check the table to see if that > page uses an extension, otherwise use the cache, etc. Am I correct ? Well, yes, that's more-or-less similar to what I was saying - the crucial point is that you have to decide whether it should be read from cache *next* time, not *this* time. I guess I misunderstood what you were saying in the first place, because you made it sound like the process was [detect tag] -> [recreate content], whereas it would actually be more like [detect tag] -> [flag article as dynamic] and then later [detect dynamic flag] -> [ignore cached copy] After thinking about it for a while, I went further and, rather than having an is_dynamic flag (which would be just one field in the cur / revision / whatever table, you don't need a whole new table for it) and storing a cached copy that you know you're not going to use, I(Continue reading)
1 Mar 2005 18:32
Re: Linking to "parent page"
On Tue, 01 Mar 2005 01:16:07 +0100, Dorthe Luebbert <luebbert@...> wrote: > Hi, > > is it possible to link to the parent page automatically? E.g. using a > special variable ? MediaWiki doesn't really have a concept of "parent page" - it's not a hierarchical structure. That said, there is limited support for a "sub-pages" system, which is disabled by default for the main namespace to encourage a "web" rather than "tree" structure, which was deemed to be much more useful (specifically, in the context of an encyclopedia, but the same arguments apply to many other projects too). And it does indeed provide links to the "parents" of pages. But it is based entirely on the names of the pages - [[Section 1/Page 1]] would be a "sub-page" of [[Section 1]], and [[Section 1/Page 1/Supplement]] would be a "sub-page" of that. You might find that rather limiting and ugly - or maybe it would be exactly what you were after. I couldn't find any very good documentation on this, but DefaultSettings.php conatins the following: /** Which namespaces should support subpages? * See Language.php for a list of namespaces. */ $wgNamespacesWithSubpages = array( -1 => 0, 0 => 0, 1 => 1, 2 => 1, 3 => 1, 4 => 0, 5 => 1, 6 => 0, 7 => 1, 8 => 0, 9 => 1, 10 => 0, 11 => 1);(Continue reading)
1 Mar 2005 19:08
installation problem: ... cannot contact the database server
My log page is attached below...The error message does not help me, maybe someone have seen it before. Any help is appreciated. Terry MediaWiki 1.3.11 installation Please include all of the lines below when reporting installation problems. Checking environment... * PHP 4.3.10RC1: ok * PHP server API is apache2handler; ok, using pretty URLs (index.php/Page_Title) * Have XML / Latin1-UTF-8 conversion support. * PHP is configured with no memory_limit. * No zlib support. * Couldn't find GD library or ImageMagick; image thumbnailing disabled. * Installation directory: /cad/local/Linux/apache2/htdocs/wiki * Script URI path: /wiki * Connected as root (automatic) * Connected to database... 4.1.10; enabling MySQL 4 enhancements * Database wikidb exists * There are already MediaWiki tables in this database. Checking if updates are needed...(Continue reading)
1 Mar 2005 18:51
Re: Caching is making me crazy...
At 3/1/2005 06:09 PM, Rowan Collins wrote:
>process was [detect tag] -> [recreate content], whereas it would
>actually be more like [detect tag] -> [flag article as dynamic] and
>then later [detect dynamic flag] -> [ignore cached copy]
You got it, that's what I meant.
>After thinking about it for a while, I went further and, rather than
>having an is_dynamic flag (which would be just one field in the cur /
>revision / whatever table, you don't need a whole new table for it)
Yes, definitely, but I did not want to be flamed too early on by suggesting
a new column in 'cur' :)
Now more seriously, out of curiosity, we would have talked about an extra
bit or an extra-byte per page record, wouldn't we ? Are you guys concerned
by that in regards to web sites like Wikipedia ? My gut feeling is that the
list of pages using extensions or dynamic contents would probably be *way*
smaller than the total number of pages, so maybe a whole new table would
not have been a totally stupid idea, it would have saved space and
computational resources, and made wikimedia easier to maintain or upgrade
once we had figured out that maybe there was a better or different way to
solve this caching issue.
>In other words
>
>Current / normal: [parse] -> [store in cache] and on request [check
>cache] -> [load from cache]
>Proposal for "dynamic pages": [parse] {[detect tag] -> [disable
>cache]} and on request [check cache] -> [can't load from cache, so
(Continue reading)
1 Mar 2005 22:44
Re: Caching is making me crazy...
On 28 Feb 2005, at 10:58, Rowan Collins wrote: > The point is, this is a chicken-and-egg problem - if the page is being > read from cache, there is no way of knowing whether or not it contains > an extension tag, or any other feature. It is logically impossible to > determine whether to parse something as part of the process of parsing > it. I suggested a specific namespace, and asked for comments, and got a big yawn. It seems to me one could subclass Article or something so that the namespace "Dynamic:" would never be cached, for example. I ask again: comments? :::: If you succumb to the temptation of using violence in the struggle, unborn generations will be the recipients of a long and desolate night of bitterness, and your chief legacy to the future will be an endless reign of meaningless chaos. - Martin Luther King Jr. :::: Jan Steinman <http://www.Bytesmiths.com/Item/99-0590-18>
1 Mar 2005 22:51
Re: Caching is making me crazy...
At 3/1/2005 10:44 PM, Jan Steinman wrote: >On 28 Feb 2005, at 10:58, Rowan Collins wrote: > >>The point is, this is a chicken-and-egg problem - if the page is being >>read from cache, there is no way of knowing whether or not it contains >>an extension tag, or any other feature. It is logically impossible to >>determine whether to parse something as part of the process of parsing >>it. > >I suggested a specific namespace, and asked for comments, and got a big yawn. > >It seems to me one could subclass Article or something so that the >namespace "Dynamic:" would never be cached, for example. > >I ask again: comments? Well that does not look like a great idea, I mean, I need namespaces too, they are pretty useful, I can't just move everything or part of a project into a new namespace... And if the page is not dynamic anymore (for example, if you don't use the extension in this specific page), you have to move the page out of Dynamic: ? Tedious. Eventually if it was a specific reserved *category*, not a namespace, but even that... I think Rowan had a decent implementation scheme for this problem (see thread). -- Sebastien Barre
>
> To see a first version of its use :
>
>
RSS Feed