DPL talk:Manual - DPL parameters: Other parameters

allowcachedresults

Does "allowcachedresults" use the data that is stored in the browser's cache, or is there something like a "server cache" where the results get stored? The later would be really useful in our case because our visitors usually just consult the pages once and it would be fine if the database-query results are updated only once a day or so.

My best, --Gollum2 17:43, 31 May 2008 (CEST)

It's a server-side cache. --Rezyk 02:18, 3 June 2008 (CEST)

Last updated article

Hi everybody,

I use your extension to display an extract of the last updated article on my main page. A couple of articles start with a template and I can't get the first 200 characters because of this template (displayed as a table). I'd like to ignore this template and display only the characters after it. I used reset or eliminate to do that but it didn't work.

Here is my DPL query :

{{#dpl:
  |notnamespace=Event
  |notnamespace=Image
  |notnamespace=User
  |notnamespace=Template
  |ordermethod=lastedit
  |order=descending
  |addeditdate=true
  |userdateformat=d/m/y H:i
  |adduser=true
  |minoredits=exclude
  |count=1
  |skipthispage=yes
  |includepage= %0[200]
  |format= ,[[%PAGE%|%TITLE%]] <br/> <span class='lastArt_details'>by [[User:%USER%|%USER%]] - %DATE%</span> <br/>
  |reset=templates
}}

Thank you for your help -- Marineam 09:42, 14 October 2008 (UTC)

Reply

This is indeed a problem for which there is no simple solution currently. The characters of each paragraph are counted from the beginning , regardless if they contain a template call or represent normal wiki text. I suggest that you start your documents with a headline after the template call (then DPL can be told to show the content after that headline). If you do not want a headline (because it would appear to the user) you could use a pair of section markers for the portion of the text you want to display. This may be the most elegant solution as it allows you to decide exactly what shall be shown. But it requires editing of your articles ... Gero 06:48, 17 October 2008 (UTC)

&action=purge

This very useful command (in combination with allowcachedresults) unfortunately stoped working on our wiki. Instead of refreshing the query it sends the user to a new page ending with "&action=purge". Our wiki seems to read this as part of the address and not as a command. Is it possible that it is not compatible with the latest version of mediawiki? My best, --Gollum2 19:29, 27 October 2008 (UTC)

I believe that this is part of the mediawiki software and not part of this extension, which version of mediawiki are you currently running? Redekopmark 03:37, 29 October 2008 (UTC)

We are running Mediawiki 1.13.0. For more details see WikiProducts:Version. Thanks for the info! --Gollum2 18:42, 30 October 2008 (UTC)

you might want to try getting upgraded to 1.13.2, there's a few bug fixes since 1.13.0, although I don't know if this is one of them. Redekopmark 04:13, 31 October 2008 (UTC)

deleterules and updaterules

Since deleting pages is normally restricted to administrators in most wikis, are these new DPL functions administrator only? Is there an option to set it that way?--Volts 17:52, 4 August 2009 (UTC)

Reply

Sad to say, at the moment "delete" and "update" features bypass standard permission checks. These features are still experimental. You may want to switch them off - either by setting

 ExtDynamicPageList::setFunctionalRichness(3);

in your LocalSettings.php after the require_once() for DPL or by inserting a code line immediately after the declaration of the 'deleteArticleByRule' function:

 function deleteArticleByRule($title,$text,$rulesText) {
    return "deletiont of articles by DPL is disabled.";

Future versions of 'deleterules' will apply standard MW permission checks. Gero 07:17, 5 August 2009 (UTC)

• Ok, thanks for the quick response!--Volts 20:46, 5 August 2009 (UTC)

deleterules

As deleterules now accept normal restrictions i would like to use it. Working in a corporate environment forces me to stick to version 1.7.4 for now.
In which version were deleterules implemented?
Can anyone provide a valid example for inline usage, i cant figure out how to get it working.
Maybe my version is to old, but a example is missing nevertheless.
-- Tac 19:11, 18 February 2010 (UTC)

You are right, I was (and still am) somewhat reluctant in documenting these features completely because I felt they are not mature enough and might be changed in future releases. Have a look at the DPL source code if you would like to use them nonetheless. Gero 23:23, 20 February 2010 (UTC)

Update rules

I've try to use the update rules, but can't get it working. I use this template on my own wiki, but it don't execute anything. I guess I'm missing something, but I don't know what. Can you help me?

Greetings Wbb29 12:15, 25 May 2010 (UTC)

To be honest this DPL feature is not very well tested and documented. I always felt it might be of no interest ...

Maybe I can improve it in one of the next DPL versions. The problem in your case could be a missing "include=*" parameter. But I am not sure. Gero 14:21, 25 May 2010 (UTC)

Glajman 14:49, 25 June 2010 (UTC)

Hi, I have used DPL succesfully fore a while and just tested udpaterules. I think I have preview working OK. However, when I choose "exec set" it gives me session errors. If I choose "edit" it indicates option does not exist (according to other message options are edit, preview and set". This is a great future that would be used a lot by many users. Just 2 questions: 1-Can you show me how to execute the update in batch without preview? 2-Can you test this a bit more and document with some examples?

Thanks!!

"reset" and "eliminate" should also suppress magic words

"reset" and "eliminate" should also suppress magic words like __NOTOC__ on the page containing the DPL query. Filed an issue at http://semeb.com/dpldemo/index.php?title=Issue:%22reset%22_and_%22eliminate%22_should_also_suppress_magic_words

--nakohdo 17:54, 12 July 2011 (CEST)

Aren't you saying, that they should ignore such magic words within the documents being analysed by the DPL query? Or do you really mean the page that contains the DPL query itself? Gero 00:36, 15 July 2011 (CEST)

I use __MAGICNUMBEREDHEADING__ in some of the documents analysed by DPL. If DPL includes a section from one of this pages (using "include") the page with the DPL query "inherits" the numbered headings. Note: This is probably related to my other issue as this seems to only occur if the magic word is inserted at the bottom of the page (mostly using a template). So everything seems to boil down to parsing order. --nakohdo 10:59, 15 July 2011 (CEST)