User talk:Leviathan 89

Welcome
Hi, welcome to Community Central! Thanks for your edit to the User blog comment:Ohmyn0/What's Going on with Chat/@comment-Leviathan 89-20110505214018 page.

If you're looking for help and have questions about Wikia, you are encouraged to visit the community help forums here for help and advice. —MtaÄ (help forum | blog)

wow!
wow!..you got pretty active here as well:)

DPL help (copied)
Hi! Since you told me I can ask you to set up a DPL here I am! So.. I'm trying to make a template for admins which will list the pages candidates for deletion and the users requested to be banned... for example:  category = Candidates for deletion include = {Delete}:reason:1 format = {| class="wikitable"¶!User!!Reason for deletion,¶|-¶|%TITLE%||,,¶|}  This should produce a simple table with a list of pages candidates for deletion with why they should be deleted. The problem is that the reason can be provided as either a free parameter and as the "reason=" parameter. So if they're both present (in different templates) they will be put in two different colums, while I want both of them in "reason for deletion". Is there a way to use a logical OR like :reasonOR1? Or to force the call in the table like this?
 * -¶|%TITLE%||#REASON# #1#,,¶|}

Also, a doubt about the "replaceintitle" parameter, if I want to replace a subpage like /sub/ how can I do that? Because if I use  the first "/" won't be replaced. And are there jolly characters?


 * The way I see the query syntax you posted, the included parameters will both be in one column in the table, since you didn't divide them in any way. It would easier for me to verify that, if I had a 'live' example to test on. However, instead of passing the parameters directly i.e. "{Delete}:reason:1" you can produce a surrogate template (Template:Delete dpl) which will output anything you wish, including parser functions, allowing you to decide which parameters should be in the result.


 * As for the slash issue; Perl regular expressions allow the use of pipe symbols as delimiters so   might work, although I'm not entirely sure if dpl will support that. — Sovq 22:10, July 14, 2011 (UTC)

That syntax will produce something like this, sorry it's in Italian... How is the code with the surrogate template? Ah and another thing: about the include parameter, how can I include like the first 100 characters of a page without template and images? Because I tried using "includemaxlength" but it included also templates and images... I want only plain text.


 * The problem with the queries is that for some reason the delete template keeps adding a pipe symbol somewhere to the parameters. The fifth dpl query on the page you linked shows these pipes. It should be :


 * Discussioni utente:Leviathan 89test
 * Utente:Leviathan 89/SandboxTEST, non rimuovere.
 * instead of what it is now. These pipes obviously modify the table output. Best way to solve it would be finding the source of these excess symbols and removing them. Another around that is to use the mentioned surrogate template, as shown in the first dpl query on the page. A third way would be to use the html table syntax as shown on the second dpl query (and deal with the pipes with a #replace function or something).


 * As for the second issue - you might try with the reset parameter (best trying both syntaxes: and  ). But I can't guarantee you'll get satisfying results. — Sovq 07:20, July 15, 2011 (UTC)

I made some tests and I found a solution: it seems that the extra pipes are produced only if the parameter are listed in succession like  (which it isn't normal, is it?), the simplest solution is to give the parameters separately like   which work fine with both html and wikitable. I don't know why there is this problem, since normally you list the parameter like that, and it seems this problem is common with other template... about the replaceintitle, is there a jolly charachter? Like |/*| to replace every subpage name? 12:35, July 15, 2011 (UTC)


 * Oh yeah, I guess that was the easiest solution. But keep in mind that the output is still not "clean" and the pipes might cause problems in the future. As for the wildcards:  should do it. — Sovq 14:04, July 15, 2011 (UTC)

Thank you, I hope this pipes problem is only a little code mistake and not a major error... we'll see in the future. If you have time, read this Forum:Unknown problem (I updated it), if you know something tell me. Thank you again.