Difference between revisions of "User talk:Gero"

From FollowTheScore
Jump to: navigation, search
(New User Questions)
(→‎New User Questions)
Line 448: Line 448:
  
 
- [[User:Tdoyle|Tdoyle]] 16:35, 23 October 2007 (CEST)
 
- [[User:Tdoyle|Tdoyle]] 16:35, 23 October 2007 (CEST)
 +
 +
=== Answer ===
 +
The query looks o.k. and it works here in this wiki (using ordermethod=lastedit and replacing WRG-Members by 'Fictitious country'):
 +
 +
<DPL>
 +
  debug=3
 +
  category=Fictitious country
 +
  format=,[[%PAGE%|%TITLE%]], - ,
 +
  count=20
 +
  ordermethod=lastedit
 +
  order=descending
 +
</DPL>
 +
 +
Adding 'debug=3' shows the DPL statement. It looks exactly like yours apart from the table prefix you are obviously using. You could try that SQL statement directly in your mysql interpreter or in mysqladmin.
 +
You can then strip down the statement until you see why MySQL complains. I suspect that you use an older version of MySQL which has trouble with the syntax used by DPL ...
 +
:[[User:Gero|Gero]] 18:42, 23 October 2007 (CEST)

Revision as of 17:42, 23 October 2007

I am interested to promote DPL to become part of mediawiki / wikipedia. How do you feel about this idea?

I agree, it seems very useful.--Patrick 15:14, 17 February 2007 (CET)
Gero, maybe make a list with possible effects this might have. And then analyse whether you want that. Possible effects:
  • you are not the sole maintainer
  • the development and feedback will be on mediawiki servers - contributers that are blocked there may find it harder to give feedback
  • win people that only contribute directly to mediawiki
  • no need for seperate install
  • no possibility of upgrade, without whole mediawiki upgrade
Tobias Conradi 17:32, 10 August 2007 (CEST)
  • I wouldn´t have problems in not being the sole maintainer. But I must confess that DPL is rather monolithic (I inherited the code and did not dare to change it fundamentally - although looking backwars I probably should have done so).
  • hosting my mediawiki is fine with me, as are the other two points
  • But at the moment I still care for stability. I enjoy the freedom to publish updates every now and then.
  • Used without care DPL could cause a lot of unnecessary and unwanted server load. I am also a little bit concerned about that.
  • But still I think the MediaWiki software should copme as a bundle together with the possibilities DPL provides.
Is there anybody out there who has an opinion on that point? Gero 23:53, 10 August 2007 (CEST)
Well, which point? I think you should not be the sole maintainer because, for example, DPL development stagnates when you aren't around/available. ;) -Eep² 10:59, 11 August 2007 (CEST)
I think DPL functionality should definately be a part of the MediaWiki install, but I don't think it's currently suitable for Wikipedia due to their high traffic and the ability to easily make expensive queries. Perhaps DPL queries could be restricted to protected pages, or the ability could be added to cap the resource that a query can consume...? --Nad 07:13, 3 September 2007 (CEST)

Your message at my Wikisource talk page

Hi, and thanks for your message (you said to reply here).

I tool a look at your DPL extension. It looks nice, and I think I understand some of what you are trying to accomplish with it, but my technical expertise is limited and I don't fully understand it. I am also not entirely clear as to what elements of Labeled Section Transclusion are included in DPL.

As to how to promote these things: First, people with technical expertise have to build a working, tested extension. That has apparently been accomplished both with DPL and LST.

The next step is to get the senior developers to actually apply the extension live at Wikimedia wikis (for instance, LST was designed for Wikisource). I thought that this second step would be easy, but apparently it is not, because the developers are extremely busy and have a huge list of things to be implemented. So you have to keep reminding, lobbying, etc., for instance on IRC or Wikitech mail (I don't have access to IRC).

It would be great if you could further clarify, in layman's terms, about DPL and how it incorporates LST. And lobbying is useful too...

Best to reach me at my Wikisource page as you did. Dovi


please see my answer at the end of Talk:Manual --Gero 20:53, 19 February 2007 (CET)

Developer note

Hi! Thanks for the hard work on the DPL, it's so much more useful than when I used to work on it. Please see my message at Discussion. -- IlyaHaykinson 12:00, 25 February 2007 (CET)

Thanks for the compliment. I think something like DPL is really needed for MediaWiki and it´s worth investing time and energy ... -- Gero 15:31, 26 February 2007 (CET)

Quick turnaround

Gero, just wanted to thank you for your fix to "replaceintitle". We decided this morning to deploy DPL at http://busytonight.com/wiki, specifically because we need "replaceintitle" in one particular context. I tested, it didn't work as advertised -- then I noticed on the issues list here that you made a comment today that it had been fixed, based on a comment yesterday that it wasn't working as advertised in 1.0.7. So I opened an internal ticket for us to upgrade from 1.0.7 to 1.0.8. (The person I assigned it to said, "But I just installed it last week! How can I have to upgrade it already?" :-) Richmintz 18:36, 9 April 2007 (CEST)

glitch in Special:Allmessages

Your code is printing a warning upon loading Special:Allmessages. Just FYI.

cat1 AND cat2

Hi Gero I found no way for "cat1 AND cat2". Is there an example somewhere? 84.190.56.160 11:20, 21 June 2007 (CEST)

Ok, it's category=cat1 category =cat2 ... ;-) regards Tobias 84.190.56.160 11:28, 21 June 2007 (CEST)

css files

Greetings,

This is kind of an obscure request and not directly related to the dpl extension, but I was wondering if you could email me the css files used in your example pages. I'm trying to get wiki tables and html working together, and those pages have some good examples. Or maybe just the classes used? Either would be great! Feel free to email me directly if you'd like. Thanks! --Natebsi 02:29, 20 July 2007 (CEST)

There is no css code except the MediaWiki:Common.css file. 

#n-Manual { background-color: #ffddaa; }
#n-Source { background-color: #ccccff; }
#n-Test { background-color: #ccffcc; }
#n-Type { background-color: #dedede; }
/* wikitable, sortable, and prettytable class definitions
** based on meta.wikimedia.org MediaWiki:Common.css 
*/
table.wikitable, table.sortable, table.prettytable {
  margin: 1em 1em 1em 0;
  background: #f9f9f9;
  border: 1px #aaaaaa solid;
  border-collapse: collapse;
}
table.wikitable td, table.sortable td, table.prettytable td {
  border: 1px #aaaaaa solid;
  padding: 0.2em;
}
table.wikitable th, table.sortable th, table.prettytable th {
  background: #E6E6FA; /* lavender; wikimedia: #f2f2f2 */
  border: 1px #aaaaaa solid;
  text-align: center;
}
table.wikitable caption, table.sortable caption, table.prettytable caption {
  margin-left: inherit;
  margin-right: inherit;
}

Is it that what you were looking for?

Gero 08:00, 20 July 2007 (CEST)
Thats exactly what I'm looking for, thank you so much! --Natebsi 18:35, 20 July 2007 (CEST)

Parsing problems

Recently the Guild Wars Wiki has installed DPL. Currently I'm trying to get DPL to work in a certain fashion. See this page. The problem I am having, is that I am trying to fill my output table with entries that contain a |-character (table cell separator). What I would like to know is, if the following is possible with DPL:

Page "A" (which is included in Category:Skills): 

{{Skill infobox
| description = This skill does {{gr|10|100}} damage.}}

Page "B" calling a DPL function as follows: 

<DPL>
category=Skills
includepage={skill infobox}:description
mode=userformat
listseparators=\n{| {{STDT}} class=sortable\n|- \n! ||Name||Description,\n|-\n|STYLE="padding: 0px;"|[[Image:%PAGE%.jpg]]\n![[%PAGE%]],,\n|}
secseparators=\n|
</DPL>

My output page will only show a table like this:

  Name Description
Skill image Skill name This skill does {{gr

Where I want it to show:

  Name Description
Skill image Skill name This skill does 10...82...100 damage.

Is this possible? CoRrRan --86.87.179.57 23:57, 23 July 2007 (CEST)

Reply to "parsing problems"

First, thank you for this clear explanation about what you want, what you tried and what did not work as expected. And then my answer:

  • The 'include= {macro}:parameter' syntax is meant for simple access to one parameter and indeed it takes the value of the parameter literally (mainly for performance reasons)
  • Therefore you will see the plain wiki text if the value of your parameter contains template calls.
  • But there is another way which should work:
    • write a "phantom" template which is used as a surrogate for the original template and use that template in the include statement.
    • For example: 'include={macro}.xyz' where 'xyz' would be a hopefully meaningful suffix to the name of the original macro (aka template). In your case the macro is named 'skill infobox', so just write 'include={skill infobox}.xyz'.
    • DPL will then use the template 'skill infobox.xyz' instead of 'skill infobox'. And in 'skill infobox.xyz' you can do whatever you want. It receives the same parameters as {skill infobox} PLUS additional parameters named %PAGE% and %TITLE% which you can access in the usual way with triple curly braces.
    • The trick is, that the call to {gr} will be resolved before the parameters are being passed to 'skill infobox.xyz'
    • Last hint: If you do not have a good idea what suffix to use (in place of 'xyz') you might use '.dpl'. This would at least make clear that this template is used within a DPL query. As its basename is the same as the original template, you will find them next to each other in an alphabetical listing.

Last comment: If you get everything to work based on this advice and if you think that others may have the same kind of questions, please create a DPL:FAQ document and use this as a first entry.

Gero 19:37, 24 July 2007 (CEST)
This is exactly the information I wanted to have! I have been able to modify my output table in such a way that my {gr}-template is now properly parsed before being put into the DPL table output.
Now another thing I would like to be able to do: would it be possible to dictate the output to certain table cells? For instance, I would like to be able to do something like this:
  Name Description Rest
{{{Image1|}}} {{{Name1|}}} {{{Description1|}}} {{{Energy1|}}} {{{Cast1|}}} {{{Recharge1|}}}
{{{Campaign1|}}} {{{Quest1|}}}  
{{{Image2|}}} {{{Name2|}}} {{{Description2|}}} {{{Energy2|}}} {{{Cast2|}}} {{{Recharge2|}}}
{{{Campaign2|}}} {{{Quest2|}}}  
Is this at all possible?
Anyway, I really want to thank you with your help on pointing me to the {skill infobox}.dpl-call, that really worked. If the next question isn't possible, that's not too big a problem, just a "nice to have". And regarding that DPL:FAQ : is there a page already for it, because the link you created resulted in a red link... Regards, CoRrRan --86.87.179.57 00:24, 25 July 2007 (CEST)
Yes, this is possible. You just have to create the subtable structure within the "alternate template". The template creates a row of a table each tikme it is called, and one field of this row is another table. I assume that the template has enough information to create the row completely. Maybe Test identical chapters can give you an idea how it works.
Regarding the FAQ: Just go ahead and create it!
Gero 05:10, 25 July 2007 (CEST)

I think the original problem here was actually due to DPL not retrieving the literal value of the parameter. In Page "A", which has: 

{{Skill infobox
| description = This skill does {{gr|10|100}} damage.}}

Is the complete description parameter represented by 

description = This skill does {{gr|10|100}} damage.

or does that pipe symbol after "gr" signal the end of the parameter and start of the next? 

description = This skill does {{gr

By MediaWiki standards, the former is correct, but DPL seems to go by the latter in this case.

You are right. The latest release (1.2.9) handles this now correctly. So the original form you wanted to use should now work as expected.. Gero 08:48, 27 July 2007 (CEST)
Very nice, thanks. Also though, the same bug still exists for pipes within "[[ ]]"s. (See Nigunda Test within Test section inclusion# include a single template parameter).


Thanks for your help

I just wanted to say thanks for your suggestions. Based on your feedback, I wrote an FAQ. Then, to meet our work requirements (see example using Template:Todo2), I wrote an extension that

  1. creates a "My Tasks" personalized button at the upper right hand of every page
  2. creates a Special:TaskList page to list all tasks assigned to a user with the {{todo2}} template
  3. sends out email reminders to task assignees when tasks are created/modified.

I would like to share this extension with everyone who want to use it but don't know the best way to do so. What would you recommend? --Gri6507 19:32, 2 August 2007 (CEST)

P.S. Unfortunately, I cannot do a live example of this extension because our company wiki is behind a firewall :-(

Add it to http://mediawiki.org/wiki/Extension:My_Tasks (or whatever you want to call it; and be sure to add a http://mediawiki.org/wiki/template:extension for it). But you may want to check out http://mediawiki.org/wiki/Extension:Tasks_Extension first... -Eep² 11:23, 3 August 2007 (CEST)
Thanks for the suggestion. I have created the new extension on MediaWiki's website. Please feel free to give feedback. --Gri6507 15:33, 3 August 2007 (CEST)

Hello?

Would you please reply (on the appropriate page) to my comments/suggestions/bugs in the past week or so:

Thanks. -Eep² 06:46, 15 August 2007 (CEST)

DPL talk:Manual - DPL parameters: Controlling output format#resultsfooter bug as parser function too... -Eep² 06:50, 15 August 2007 (CEST)
Talk:C and DPL:Discussion#Redirects to include pages that link to them? too please...you've replied to other people since then...I don't appreciate being ignored and/or blown off like this, Gero... -Eep² 09:29, 24 August 2007 (CEST)
I try to do my best - but my time is limited. I helped you a lot and implemented several things due to your requests. I consider the #redirect problem as too complicated to solve within the php code. I showed you how to solve it with simple query nesting. It is by no means necessary to change something in "each redirect article" as you wrote. The only thing you have to do is to split your query into two articles. I recommend that you have a second look at C and CC. Maybe you want to change the names of these two articles anyway.
I don't understand the C/CC thing, which is why I posted about it on Talk:C, which I would prefer you reply on in order to keep the discussion in context and not require switching back and forth to follow the discussion... You'll note I didn't ask any specific questions about DPL on this talk page--only to get your attention to visit the links (and reply there instead of here)... Please reply on Talk:C and answer my questions there. -Eep² 06:35, 25 August 2007 (CEST)
I appreciate your comments, criticism and stimuli but please accept that I have to set priorities. Extending the booleans e.g. would of course be possible but I can´t see why it should be a big gain.
Again, as I state on DPL:Requests for new features#More boolean support: "on"/"off" (for HTML checkbox form support) and "1"/"0" for easier typing. In other words, HTML form compatibility and user-friendliness is the gain... -Eep² 06:35, 25 August 2007 (CEST)
Row/column is too hard to do
How/why is it "too hard to do"? It should be a fairly simple optional switch to put the headers on the side vs. the top... -Eep² 06:35, 25 August 2007 (CEST)
and Template field output is against the existing concept of template substitution (which I feel is more powerful and better suited).
Not always--especially in my case. Your way forces excessive templating that could better be handled more efficiently in a single template. Why reinvent the wheel and duplicate data unnecessarily? That's basic database design right there... -Eep² 06:35, 25 August 2007 (CEST)
The database error will be corrected (bugs always have priority). The idea of importing text from other wikis has nothing to do with DPL (I answered to that request quite recently).
So, from my side, there is nothing 'open' at the moment.
As DPL is open software it is of course possible for you and all others to make the changes you feel are desirable. From time to time people have done so as you may have observed. If nobody objects I will try to integrate such changes. Therefore I recommend to upload a diff file which shows the code changes.
As long as I feel responsible for DPL (which I currently do) I will be open for ideas from everybody. Have a nice day. Gero 10:25, 24 August 2007 (CEST)
Unfortunately, I'm not a coder. -Eep² 06:35, 25 August 2007 (CEST)

Help on limited lists

Hi Gero, I'm Poke from the official Guild Wars Wiki (see some comments above). Currently I'm working with various DPL lists and came to one issue I want to solve. When I create a limited list with count is there any way to include the number of all found pages instead of the limited one? In my example I limit the list of ~250 pages to 50 and I want to display that there are 250 pages, not 50. Is there any way to do this without using another DPL list?
Thank you very much. Poke 23:41, 29 August 2007 (CEST)

Answer

Currently there is no other solution than using nested queries, for example 

{{#dpl:namespace=Template
|resultsheader=<h2>Templates (%PAGES% out of {{#dpl:namespace=Template|format=,|resultsheader=%PAGES%}})</h2>
|count=10
}}

Templates (10 out of 500)

Gero 09:22, 30 August 2007 (CEST)

Hm, thank you - I hoped there was another method.. Poke 16:51, 30 August 2007 (CEST)

Mootools conflict

Hi Gero, I found that Mootools conflicts with the wikibits.js code prior to MW1.10 but works fine if that script is replaced with the 1.10 version. --Nad 01:00, 3 September 2007 (CEST)

I found the exact problem of the conflict which is outlined at http://www.mediawiki.org/wiki/Mootools. MW1.10's wikibits.js has a simple bug-fix implemented which involves changing the add-button loops to loop only through numerical keys rather than all the children, since many components add event callbacks to such elements. --Nad 07:06, 3 September 2007 (CEST)
Have you tested MW 1.9.x and below to make sure the MW 1.10 wikibits.js is compatible? I've replaced just the for loops and the "undefined" errors go away at least. -Eep² 12:52, 3 September 2007 (CEST)
I've tested replacing the entire file which appears to work but could have problems, replacing only the loops is best. --Nad 13:03, 3 September 2007 (CEST)

TreeView4

The new Treeview4 code is able to handle transclusion much better and allows those templates like Template:Links 2 to include the tree definition within them to make their syntax much simpler. For example see Category Tree Example. TreeView4 is still in testing but seems fine so far and can be run easily along side the current version, see treeview doc page --Nad 13:13, 7 September 2007 (CEST)

Thanks for the information about TreeView4. I will install it here in the next days .. Gero 14:02, 7 September 2007 (CEST)
Treeview 4.0.6 is the current version which handles multiline items, to force a line-break at a particular point use a normal <br>. Otherwise use css to define how the lines are formatted. By default it now uses dotted connector lines which I've uploaded the default images for, but you can set them to the empty spacer image if you don't want them. Also, the css rules have changed slightly, mine are as follows:
.tree-view,
.tree-view td,
.tree-view tr { margin:0; padding:0; vertical-align: top; text-align: left; }
.tree-view td.tree-text,
.tree-view td.tree-text a { font-size:8pt; line-height: 14px; }
.tree-view td.tree-text { padding: 2px 0 0 3px; }

Spambots

Looks like some spambots have found you! the quickest solution is to install Extension:ConfirmEdit which in it's default setup will add a simple numerical addition question to the user account creation. --Nad 04:07, 11 September 2007 (CEST)

Yes, thank you for that advice. I was already thinking about such a measure... --Gero 07:35, 11 September 2007 (CEST)

Hello? #2

These things need your response still please...:

-Eep² 09:01, 16 September 2007 (CEST)

.. Yes, but there are not only your requests, and my time is limited. Let´s see wehat is possible .. Gero 10:04, 16 September 2007 (CEST)
No, they're not, but my requests were before most of the others you have responded to since I replied (which is the same stuff Nad pulled on me before that I got so pissed off at him for)... I am trying to get my wiki formatted how I want and have been working on it now for almost 2 months now and still cannot attain the desired goal, despite having tried many variations/extensions and seeking out help in many different ways (IRC, forums, wikis, etc). Needless to say, my patience is wearing thin...especially since I have been wanting to get this database done for the past 7 years now and MediaWiki is the closest I've come to actually being able to do it. So to be hindered by so many little things is...quite aggravating and frustrating. <twitch> -Eep² 10:33, 16 September 2007 (CEST)
I still need some help with DPL:Discussion#Replace_delimiter-separated_lists_with_links and DPL:Discussion#More_comma_problems please. Also, per DPL:Requests_for_new_features#Template_field_output still, how do I use the multiple template parameter support for include and still get all parameters as links without having to specify each field's formatting specifically in a phantom template? Ideally, it would be nice if DPL could automatically pull in all parameters (with their inherent/native formatting) without having to even specify them (and even a way to exclude specific parameters--with regex or at least wildcard support). See http://www.tnlc.com/wiki/index.php?title=Comparison_table for various attempts. Also, per DPL:Requests_for_new_features#Table_row.2Fcolumn_header_switch, I still need a way to have table "rows" (horizontal) as "columns" (vertical) in order to look like http://www.tnlc.com/eep/compare/table.html —Eep² 15:04, 27 September 2007 (CEST)
  1. I wrote an answer to the 'comma' problem.
  2. I see no way to offer swapping columns and rows in an output table. It may sound strange to you but that would be VERY complicated to do. Maybe you find another extension which can take a complete wiki table and swap it. Taken alone this functionality could be built much easier (but I won´t do it). I might be able to call the API of such an extension once it would be there.
  3. You can use 'multiple template parameters' without 'table' of course. If you want to convert each parameter into a hyperlink you must specify that explicitly as it is by no means clear that template parameters might be interpreted as link targets. The new 'tablerow' statement offers help if you want tro have a table where each template parameter corresponds to one column. If not you have to provide a surrogate ("phantom") template.
Gero 17:19, 27 September 2007 (CEST)

Hey Gero

Thanks very much for feedback on my bugs and FAQ postings.

I wonder if you had time to look at the SQL I wrote here;

http://semeb.com/dpldemo/index.php?title=DPL:Requests_for_new_features#Add_.27contributors.27.3F


Hopefully that would allow you to rank 'contributors' to a page or to a category... ug... or even to pages within a category. Do you ever wonder if DPL is growing beyond all bounds? --Dmb 18:57, 18 September 2007 (CEST)

Thanks for the query! Have you had a look at (debug=3) the current complexity of SQL which is produced by DPL? I really do wonder whether the code (and my head) can cope with adding another chunk of logical branches to that. Lines 2300..2500 in the code deal with the output of the SQL statement. I guess it would have to become another path similar to the handling of multiple revisions. At the moment I am working on something else (suppressing backlinks to DPL output) which is really hard. But I think there will be a moment where my head is free again ... Gero 20:06, 18 September 2007 (CEST)

Hey Gero ... about Wgraph?

I was using Wgraph as a convenience thing, and to test the limits of what is possible. The Test graph is a dependency graph for the 'BioConductor' project for the statistical analysis of microarray data. I really like aiSee, so Wgraph is very nice for me. I made the dependency graph for a friend, and I thought that it would be nice to get a picture.

To answer your question, I didn't try it on a local machine, as I haven't got round to installing the extension locally. However, I see that it is now working... after a fact... I find that when editing a particular Wgraph page that *had* a working graph, after making edits that give a non-functional graph, the old working graph is still shown, giving the false impression that the previous edits worked.

Hrm... seems not working any more! I renamed the Test graph page to;

Test graph - BioConductor package dependancies, where I see no image.

BTW, a Wgraph in a page containing ('s breaks.


Here is an image generated with graphviz for reference...

Biocpackages readable.small.png


Thanks for the great software. I read your profile on MediaWiki... sounds interesting!

I am currently working on two wiki projects that may be of interest to you because they contain (unstructured) structured data;

--Dmb 20:33, 26 September 2007 (CEST)

Do you work in research? Your projects look quite interesting ..
I made some tests with your sample data and discovered (as I had already suspected) that the graph generator on the webserver hits some technical limit if you use the full test sample. I changed the script. Now the output files are explicitly erased before graph generation starts, so you should at least no longer be fooled by old output. But there is still no error message (apart from an empty graph) in such cases at the moment.
When you use 2/3 of the sample data everything works fine. I played around a little with attraction, repulsion and gravity; the result looks quite nice Test graph 2. The output is png and svg, the svg looks much better as it supports 4 or 5 levels of zooming. The text characters are represented as polygons. This is good for zooming but makes the file big (~4MB).
I don´t understand your remark on parenthesis crashing a Wgraph. Could you give an example?
Gero 00:26, 27 September 2007 (CEST)

Uncategorised articles question

Hi Gero, I can't seem to get uncategorised articles to list anymore, I've added the extra database view, but it seems to have stopped working at some point. If I just do {{#dpl:category=}} shouldn't that list them? it doesn't return any content on this wiki either, am I missing something obvious here?

Also if you're interested, the new version of SimpleForms uses MediaWiki's native ajax functions and no longer requires mootools. --Nad 23:36, 12 October 2007 (CEST)

Thanks for bringing this up. The extended view needed for uncategorised articles is not installed in the dpldemo wiki. I once tested it in my local wiki and it worked. But I have never checked since then. I will give it a look ...
I had problems with mootools so I will try your latest version. As you may have seen I have developed a "pattern" of a MW page containing a SimpleForm calling itself via the 'Call' extension. Maybe I can use Ajax here instead. Althouh I am quite happy with the way it works right now..
Is there a way to create a form which will put the contents of the form elements (selections from combo boxes, contents of fields and text areas) into a single piece of text (possibly using a template) which then is stored as a new article? I see occasions where I would like to offer a form to the user which he just fills in and thereby cerates a new article in some stanbdardized format. See for example the way I try to handle Bug Reports.
--Gero 08:37, 13 October 2007 (CEST)
Yes that can be done, but it currently involves very cumbersome syntax with a lot of JS. But the next version has a new feature which makes integrating forms with templates very simple, I'll let you know when I have a working example ready. --Nad 14:14, 13 October 2007 (CEST)
Fine. Regarding articles without categories: It still works on my local wiki. You must add a pipe symbol to your command:
<dpl>
  category=|
</dpl>

Gero 21:35, 14 October 2007 (CEST)

Can you see if the dpl query as a parser function works please? I think that may be the issue, for some reason;
# tag works
<DPL>
namespace=Template|
category=|
</DPL>
# parser function fails
{{#dpl:namespace=Template|category=|}}

the tag query works but the parser function fails, for example in one table; 

{| 
| TAG || PARSER
|-
|<DPL>
namespace=Template|
category=|
</DPL>
|{{#dpl:namespace=Template|category=|}}
|}

--Zven 21:53, 14 October 2007 (CEST)

You ran into a typical problem of wiki syntax! The pipe after "category=" is understood as a parameter separator by the wiki engine. you must escape the pipe character using {{!}}.
Zven 22:28, 14 October 2007 (CEST)
Doh, thanks for the reminder, both nad and I forgot about that >< . This worked without the <nowiki> tags;
{| 
| TAG || PARSER
|-
|<DPL>
namespace=Template|
category=|
</DPL>
|{{#dpl:namespace=Template|category={{!}}}}
|}

--Zven 22:28, 14 October 2007 (CEST)

Excellent, well I'm glad that's working then - I didn't even realise we needed a pipe, let alone that it needed to be escaped :-/ --Nad 03:06, 15 October 2007 (CEST)

SImple Forms caching problem

The problem appears to be a caching issue - it's only happening when action=render, as can be seen from this request which shows in the returned content that it's being returned from the parser cache which is wrong. I've done a patch which ensures the cache is disabled (even though it should be anyway since it returns dynamic content?!) but check it out with the latest code (0.4.3) and it may have solved the problem. --Nad 08:23, 22 October 2007 (CEST)

Thanks for the quick response. 0.43 still seems to behave as before Test Simple Forms. I cleared my browser cache and tried with several browsers but as you suspected the cause lies on the server side. Is there a debug switch I could activate? Gero 08:51, 22 October 2007 (CEST)
Strange it's still returning it from the parser cache - I'll have another look and see if I can reproduce the problem locally so I can fix it quicker. Regarding the other issue of not being able to put a form inside another parser-function, that's a known bug which I'll get fixed as soon as I get enough time - unfortunately I've been having to focus on boring old money-earning :-( --Nad 23:09, 22 October 2007 (CEST)

New User Questions

Hello and thank you for such a powerful extension.

When I use the following, everything works fine: 

<DPL>
  category=WRG_Members
  format=,[[%PAGE%|%TITLE%]], - ,
  count=20
  ordermethod=size
  order=descending
</DPL>

However, when I change the ordermethod to "lastedit", I receive the following error:

The DPL extension (version 1.5.0) produced a SQL statement which lead to a Database error. The reason may be an internal error of DPL or an error which you made, especially when using DPL options like titleregexp. Query text is: SELECT DISTINCT `wrg_page`.page_namespace as page_namespace, `wrg_page`.page_title as page_title, rev_user, rev_user_text, rev_timestamp FROM `wrg_revision` AS rev, `wrg_page` INNER JOIN `wrg_categorylinks` AS cl0 ON `wrg_page`.page_id=cl0.cl_from AND (cl0.cl_to='WRG_Members') WHERE 1=1 AND `wrg_page`.page_is_redirect=0 AND `wrg_page`.page_id=rev.rev_page AND rev.rev_timestamp=( SELECT MAX(rev_aux.rev_timestamp) FROM `wrg_revision` AS rev_aux WHERE rev_aux.rev_page=rev.rev_page ) ORDER BY rev_timestamp DESC LIMIT 20 Error message is: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT MAX(rev_aux.rev_timestamp) FROM `wrg_revision` AS rev_au (localhost)

What am I doing wrong? Thank you!

- Tdoyle 16:35, 23 October 2007 (CEST)

Answer

The query looks o.k. and it works here in this wiki (using ordermethod=lastedit and replacing WRG-Members by 'Fictitious country'):

Extension:DynamicPageList (DPL), version 3.2.1: Warning: No parameter option supplied for ' '. (Missing '=')

Nigunda Test - Somango - Nigunda - DPL Example 007 main page 1 -

Adding 'debug=3' shows the DPL statement. It looks exactly like yours apart from the table prefix you are obviously using. You could try that SQL statement directly in your mysql interpreter or in mysqladmin. You can then strip down the statement until you see why MySQL complains. I suspect that you use an older version of MySQL which has trouble with the syntax used by DPL ...

Gero 18:42, 23 October 2007 (CEST)
Retrieved from "http://followthescore.org/dpldemo/index.php?title=User_talk:Gero&oldid=7720"