Difference between revisions of "Issue:DPL incompatible with MW 1.16 alpha"

From FollowTheScore
Jump to: navigation, search
(possible solution / hack)
Line 52: Line 52:
 
  return array($dplresult, 'noparse' => false, 'isHTML' => true);
 
  return array($dplresult, 'noparse' => false, 'isHTML' => true);
 
--[[User:Dedlfix|Dedlfix]] 14:25, 16 June 2010 (UTC)
 
--[[User:Dedlfix|Dedlfix]] 14:25, 16 June 2010 (UTC)
 +
: No, this is not the solution, because it works only for results containing <nowiki><html></nowiki> and breaks others. --[[User:Dedlfix|Dedlfix]] 07:09, 17 June 2010 (UTC)

Revision as of 08:09, 17 June 2010

Description: all modes (except 'userformat') produce invalid code
Extension / Version: DPL   /   1.8.9
Type / Status: Bug   /   open

Problem

All modes produce invalid code (except mode='userformat').

Example:

<DPL>
  category=some_cat
  mode=unordered
  randomcount=3
</DPL>

produces:

  • <html><a href="/wikiname/index.php/Article1" title="Article1">Article1</a></html>
  • <html><a href="/wikiname/index.php/Article2" title="Article2">Article2</a></html>
  • <html><a href="/wikiname/index.php/Article3" title="Article3">Article3</a></html>

instead of:

Example in our wiki: DPLbug --Nachteule 09:15, 20 February 2010 (UTC)

Reply

Obviously MW is undergoing another change in its internal structure. I am afraid DPL will have to be changed accordingly. Right now I do not have time for investigations. It would be very helpful if somebody could give details on the nature of change and the consequences for extensions like DPL which use MW interfaces.

I may be able to get DPL running on the latest stable version of MW if somebody could provide details on what the change is and how to cope with it. Last time when something like this happened it was quite a painful process ....

And probably there will be another version incompatibilty - meaning that the modified DPL version will not run on MW versions below 1.16....

The effect you found might be caused by a difference in handling commands which allow "raw HTML".

Gero 23:31, 20 February 2010 (UTC)

The change in revision 61905 is the reason for this "bug"
Comment was: "Remove <a> tag hook for now, pending resolution of implementation issues as discussed on CR r58717." --Nachteule 13:35, 22 February 2010 (UTC)

Maybe this is more a hack than a solution, but in my case it works:
File DPLSetup.php in function ExtDynamicPageList::dplParserFunction I inserted after line 1288

// the following is line 1288
$dplresult = DPLMain::dynamicPageList( $input, $params, $parser, $reset, 'func' );
// this is what I inserted:
return array($dplresult, 'noparse' => false, 'isHTML' => true);

--Dedlfix 14:25, 16 June 2010 (UTC)

No, this is not the solution, because it works only for results containing <html> and breaks others. --Dedlfix 07:09, 17 June 2010 (UTC)