Talk:Resultsheaderwithcolumns

From FollowTheScore
Revision as of 17:41, 4 February 2010 by Gero (talk | contribs)
Jump to: navigation, search

Any reason why columns doesn't work right when used in a template? -—Eep² 13:40, 2 February 2010 (UTC)

Probably yes ;-) The question might be: is it "bug or feature"? What problem are you exactly talking of? Gero 18:03, 2 February 2010 (UTC)
Well, you know how DPL can be called as a tag (<dpl>...</dpl>) or as a template ({{#dpl:...}})? Well, using columns inside the DPL template causes the wiki table markup to show but fails to render as a table:


Which, for some reason, renders like this on my wiki:
{|

|

    * Entry
    * Entry
    * Entry

|valign=top|

    * Entry
    * Entry
    * Entry

|valign=top|

    * Entry
    * Entry

|valign=top|

|}

But I haven't upgraded in a while so that might be the problem. -—Eep² 03:37, 3 February 2010 (UTC)

So I upgrade to the latest version, but now I get this error:
Fatal error: Call to a member function getText() on a non-object in .../httpdocs/wiki/includes/Parser.php on line 3715
Any ideas? All I did was copy all of DPL's files to a new extensions subfolder, then add this to LocalSettings.php:
require_once("$IP/extensions/DynamicPageList/DynamicPageList2.php"); 	#4
And commenting out the line for the old version:
#require_once("$IP/extensions/DynamicPageList2/DynamicPageList2.php"); 	#4
-—Eep² 04:10, 3 February 2010 (UTC)
I notice my user page test also generates a similar error:
Fatal error: Call to a member function getNamespace() on a non-object in /www/htdocs/w0057617/dpldemo/extensions/SimpleForms/SimpleForms.php on line 457
Eep² 04:27, 3 February 2010 (UTC)

Reply

I can reproduce the effect you describe if I use a resultsheader without trailing newline:

7 pages in total.{| |

|valign=top|

|valign=top|

|valign=top|

|}


Is that the reason? Gero 15:41, 4 February 2010 (UTC)