I found a similar solution now, without using the internal function. function renderer($input) { global $wgTitle,$wgParser,$wgUser; $output = $wgParser->parse($cal->getCurrentMonthView(), $wgTitle, ParserOptions::newFromUser($wgUser)); return $o->getText(); } but I still think there should be a way for extensions to use the parser without hacks like this. christof On Fri, 21 Jan 2005, Muzaffer Ozakca wrote: -- Christof Damian christof(a)damian.net

Scot Hacker wrote: Try 1.4beta5; the default skin no longer uses the PHPTal template library and does not require storing a compiled template script file. If you still have problems, it would help to know exactly which files it's trying to work with in /tmp. -- brion vibber (brion @ pobox.com)

Scot Hacker wrote: The version of MonoBook in 1.4 doesn't use any temporary files, so there would be nothing to configure. Make sure that you have completely replaced all script files; sometimes people end up with a strange mixture, or put in a new set of files but have their configuration load up the old version of code from another directory instead. Often a filename is included in the error message. If not, usually some information about what script line failed is included in the error message. If not, usually there is _something_ in the error message from which we might identify what code is involved, from which we might figure out what it's trying to do. The only clue we have right now about the error message is "The error message implied that I could set the TMP environment to something else". The only reference to TMP in the current code is a non-fatal notification message about safe_mode in the installer (the bit about TMP is left over from 1.3 and should be removed). Can you read back the exact error message you're currently receiving? Consider also that old pages with error messages on them may be cached by the browser, so remember to refresh and check multiple pages. -- brion vibber (brion @ pobox.com)

On 1/22/05 12:02 AM, Brion Vibber wrote: FYI, the exact error was: "Can't find a writable temp directory for the XHTML template. Check that the TMP environment variable points to a writable directory, or that the default temp dir (/tmp) exists and is writable." And I was getting this even when I had created a writable TMP dir for the user in the apache config. Scot

I will soon need to create thousands of pages with a standard bit of text on each. Is there any reason that I can't just use php and add records to the "cur" table, putting values in the "cur_title" and "cur_text" fields? Do I need to set values in any of the other fields of the "cur" table, or any other tables? (The text is just a set of extension tags, with the Page Name inside. Additional text can be added later by users using normal wiki methods.) James

On Sun, 06 Feb 2005 10:29:03 -0600, =James Birkholz= <j.birchwood(a)verizon.net> wrote: I haven't looked at the code in a long time, but something like $this->mTitle->getText(); -- [[en:User:Dori]]

On Sun, 06 Feb 2005 03:59:32 -0600, =James Birkholz= <j.birchwood(a)verizon.net> wrote: Well, I'm no expert on the database structure, but I'd imagine you'll have to put *something* valid (in the sense of vaguely similar to what MediaWiki would have put there) in *every* field of the cur table, else MediaWiki'll get mighty confused when it tries to do something like display the page history . Importantly, get cur_namespace right - don't be fooled into thinking there are articles called things like "User:Foo", when they're actually called "Foo" with cur_namespace=2 (you may know this already, but I think it's a reasonably common "gotcha", so worth pointing out). Also, I'd create a "fake" user to assign the edits to, and call it "Content seeding script" or something appropriate to show up in the page histories. As for other tables, there are various scripts in the 'maintenance' directory for rebuilding various things, such as recentchanges, the links table, etc. It might be worth running at least some of those to make things consistent after your mass changes. -- Rowan Collins BSc [IMSoP]

I've never used classes yet, is there something else I need to do to use this? Do I need to create an instance or declare a global? At 10:20 AM 2/6/05, Dori wrote:

Jan Steinman wrote: The hashes are salted to make it harder to bulk brute-force users' passwords if the hashes are leaked. (You can turn off the salting to use a system where password hashes can be copied from user to user, but this is a) less secure and b) will invalidate all existing passwords, requiring them all to be reset. See settings in DefaultSettings.php) The hashing algo is MD5(CONCAT(user_id,'-',MD5(password))). AFAIK it's hashed the same was as the main password. -- brion vibber (brion @ pobox.com)