Extension talk:LifeMarks

LifeMarks 0.3.3 on the way
I started rewriting and refactoring of LifeMarks extension. New features includes: ability to delete LifeMarks after article deletion, rendering of &lt;lifemarklist&gt; on the fly without having to reedit the page, internatiolization. I don't want to fork LifeMarks, so I'm asking to cooperate and maintain the code together. Lukasz Rzanek, Radical Group --83.24.170.123 10:55, 12 October 2006 (UTC)


 * By all means, please contribute. Those were my exact gripes with what I'd been unable to defeat on my first extension.  I'm looking forward to your contributions!--Bakerq 14:43, 14 October 2006 (UTC)

LifeMarks idea
Would be great to intergrate it with http://meta.wikimedia.org/wiki/EasyTimeline --Magick 18:35, 12 November 2006 (UTC)
 * The timeline was actually the inspiration for this. My goal was to create a method of creating marks that could be collected and displayed in a timeline.  I'm pretty sure that you can use the output from the LifeMarksList to drive the EasyTimeline, but since the LifeMarksList isn't truly dynamic, it'd mean updating the EasyTimeline each time.--Bakerq 18:56, 25 November 2006 (UTC)

Fatal Error
When i try to open http://mydomain/index.php?title=Spezial:LifeMarks i got the following error: Fatal error: Cannot access protected property OutputPage::$mParserOptions in /wiki/extensions/LifeMarks.php on line 431 which is the following line in the php-script: $tempoutput = $localParser->parse($complete_output, $wgTitle, $wgOut->mParserOptions, false);

I have the same problem in the following line, when using the tag LIFEMARKS or LIFEMARKSLIST: $temp_output = $localParser->parse($processedline, $wgTitle, $wgOut->mParserOptions, false);

Could someone help me? I don't know, what's the problem is.

Best regards


 * Which version of MediaWiki are you running? The LifeMarks extension was developed and tested on 1.6.8, and I can't guarantee that the framework would still function on anyhthing higher. --Bakerq 14:42, 17 February 2007 (UTC)

Great extension
But I had to leave it behind in the upgrade to 1.9.2 with the problem with mParserOptions outlined above. Hopefully someone with more time or brains can figure out the conflict with includes/Parser.php.

Fix for Fatal Error Extension LifeMarks
The problem as stated above is the call to: $wgOut->mParserOptions.

The proper call should be:

$wgOut->parserOptions

Make these changes on lines ~263,493, the extension should work as advertised up to on 1.9.2.

I have put modified code on the discussion page of the source code, here

Other changes:
 * Eliminated additional comments on lines ~559,560 from SpecialPages:LifeMarks
 * Tests for null $lifemarks_buffer

URL Reference: http://www.gossamer-threads.com/lists/wiki/mediawiki/76771

Peace.

Fatal Error with MySQL while trying to install this extension
I couldn't use it yet. When I click the Save Page button this is the error displayed.

Ha ocurrido un error de sintaxis en una consulta a la base de datos. Esto puede indicar un error en el software. La última consulta que se intentó fue: (Consulta SQL oculta) dentro de la función "Database::insert". El error de retorno de MySQL fue "1048: Column 'tags' cannot be null (localhost)".

While its in spanish I think its self explanatory. How can you help?

Thank you

That's because orderbytext just contains "ORDER BY " and then nothing.

Change the line

$options = array( 'ORDER BY'=>$orderby ); //default order

to

if ($orderbytext) $options = array( 'ORDER BY'=>$orderby ); //default order else $options = array; //no order by Kuebel 14:06, 25 September 2007 (UTC)