Talk:Extension Matrix

DynamicPageList
This page is actually a good idea.

It would be a lot easier and more up to date, if we had Extension:DynamicPageList installed, because then the table could be automatically generated.

--GunterS 01:08, 4 March 2007 (UTC)


 * DynamicPageList can extract, mangle and reformat template parameters? -- Duesentrieb ⇌ 11:36, 4 March 2007 (UTC)
 * In fact in can. You basically define a new template with the variable names you would like to extract from the extension template. Here is a quick example, you are invited to mess with it. --GunterS 19:08, 4 March 2007 (UTC)
 * Hm, interesting. Looks a bit cryptic, I'll have to dig in a bit to see if it's really flexible enough. Can it escape inter-language-links, image-links and templates, so they don't screw up the layout? -- Duesentrieb ⇌ 13:05, 6 March 2007 (UTC)

Hi, my name is Gero (aka Algorithmix) and I invested quite some time into DPL because I felt that something like DPL would help to get more structure and transparency into the wiki world.

If I can be of any help, feel free to ask me on the dpldemo website. Indeed DPL looks a bit cryptic at a first glance. But it is really powerful and if somebody comes up with suggestions for a syntax which is better to read, write and understand I would be pleased. The features "under the hood" are all there, I think. Image escaping for instance, can be switched on and off - as there are applications conceivable where you want to see the image and others where you want to see a link to the image. Your point about interwiki links is not clear to me. What´s your concern?

--Algorithmix 20:03, 6 March 2007 (UTC)


 * foo must be escaped to fr:foo . Also, template expansion should be optional (or ideially, only allowed for specific templates). As to the format: I simply used MediaWiki's template engine for Extension:News - wouldn't that work here, too? For extracting the values, especially, if they can appear in any order, i'm not sure what the best thing would be. perhaps a name and then a regexpression? So the name could be used as a parameter name in the template? Or is it already like that? I have to admin, I didn't look too deeply into DPL. -- Duesentrieb ⇌ 21:55, 6 March 2007 (UTC)


 * Nicely done Dues - looks great! --Jimbojw 22:27, 6 March 2007 (UTC)


 * The access to template arguments works as follows: Let us assume you have an article about a country named Agadonia which uses a template called "country" with parameters a,b,c,d. Agadonia can place named parameters in any order, unnamed parameters must of course respect order. Now in your DPL query you select articles which use "Template:country" and you point to a different template, say "country.dpl" which gets called INSTEAD of the original template by the DPL engine. It is completely up to you to write Template:country.dpl in a way that it produces the output you wish. "Country.dpl" gets all parameters which Agadonia used in its call of "country" in the original sequence PLUS two extra parameters which tell "country.dpl" about the article name. DPL only processes the template call, the rest of the article is ignored. But you can define several templates and you can use the described "template faking mechanism" several times in the same DPL query. --Algorithmix 15:01, 8 March 2007 (UTC)

Warning: Failed to fetch?
Hey Duesentrieb - This comment appeared in the article text after the last update: &lt;!-- WARNING: failed to fetch Extension:MetaKeywordsTag --&gt; Did I do something wrong in Extension:MetaKeywordsTag? Thanks in advance. --Jimbojw 15:43, 14 March 2007 (UTC)

Pulling in weird stuff
Hey Dues - you may want to take a look at the bot. It's pulling in weird stuff for Extension:PHPBB/Users_Integration. --Jimbojw 19:43, 29 March 2007 (UTC)


 * Thanks for the info - actually, it's not pulling in weird stuff, it's swallowing part of the matix table into a &lt;nowiki&gt; section... will try to fix it. -- Duesentrieb ⇌ 21:58, 29 March 2007 (UTC)


 * Fixed. -- Duesentrieb ⇌ 21:58, 29 March 2007 (UTC)

please add the sortable class to the table
Then we can sort by field, you may have to go to single line table but that would be good also as we can see more extensions per page that way. Also how do get more of the extenstions moved to the correct site so they will show up in herer? like gnuplot.

Very nice page and idea! --Exprexxo 13:59, 28 April 2007 (UTC)

Failed to parse
Several extension pages are throwing error messages, but have nothing visibly wrong with them. What is going on? Titoxd (?!?) 07:12, 4 May 2007 (UTC)
 * I noticed the Extension:Poem was failing so I checked out the transcluded Template:Extension within the article and noticed the &lt;nowiki&gt; tags. I suspected these were the problem so made the following difference to remove the &lt;nowiki&gt; tags. After doing this the next time DuesenBot made an edit it was fixed. --Zven 09:36, 6 May 2007 (UTC)
 * The Extension:Google_Maps (and associated extensions) are probably all failing because they transclude Template:Google Maps Extension Info as a set of defaults for the Template:Extension within the articles, i.e. two layers of transclusion, but this needs to be checked --Zven 09:43, 6 May 2007 (UTC)
 * It is probably the spaces in Image names, I have made the following edit to Template:Google Maps Extension Info to see if parsing is fixed for Extension:Google Maps and associated extensions --Zven

sub-pages.
Hi Duesentrieb. Would it be possible to exclude all sub-pages from this list. All extensions should always have a main page at Extension:ExtensionName. Sub-pages will contain extra information or non-English versions of the page. Sometimes (particularly in the case of translations) it may be desirable to include Template:Extension on one of these sub-pages, which currently causes that extension to appear twice in the list. For example, take a look at my CrudeProtection extension - it is currently appearing twice, once in English, once in French... --HappyDog 01:23, 21 May 2007 (UTC)
 * I'll see what i can do... -- Duesentrieb ⇌ 22:35, 21 May 2007 (UTC)

Extension category
Hi duesentrieb. I have been trying to categorize all of the extensions. Would it be possible to add a column for the categories they use, within the category. I'd imagine that might make things messy though if you couldn't exclude and i'm not sure what would happen if an extension fell under 2 categories. See what you think. Bouncingmolar 02:41, 24 June 2007 (UTC)


 * Note: that the extensions that have been converted to use the Template:Extension categorized no longer show up on the Extension matrix list. Please fix if at all possible.  Michael Daly 22:15, 10 July 2007 (UTC)


 * Template:Extension categorized is a forked template and it's not meant for use. Extension infopages should use Template:Extension. If you see somewhere a page that uses template:extension categorized, be bold and replace it with template:extension, i.e. remove the word categorized -- Sayuri 08:50, 11 July 2007 (UTC)


 * This has now been taken care of. -- Sayuri 10:18, 11 July 2007 (UTC)

Scrolling
Anyone know why this page has so much horizontal scrolling? My monitor is 1680 wide and it still can't fit it all in. Is it just me? 76.98.65.131 05:30, 31 August 2007 (UTC)
 * It is not just you, to establish the width set you would need to look in <table class="xm-table"... --Zven 02:29, 4 September 2007 (UTC)

The width is not defined by the style. The problem is this: if on some extension page there's a long url in one of the fields, or a lot of text in the version field, etc, the respective column has to grow to accommodate that. There'S no solution to this except to look through the matrix, find the entries that cause the wide columns, and edit the extension's pages to fix them.

Hm... maybe one could try to use overflow:auto with the table cells. But I have no idea how this would interact with the overall table layout. If you feel like it, play with it. -- Duesentrieb ⇌ 10:42, 4 September 2007 (UTC)
 * Ah see, thanks for the explanation.  --Zven 19:45, 4 September 2007 (UTC)
 * It is definately situations where there is a long url as a large chunk of text will have spaces. My example derived from Wikipedia:Help:Table seems to control large text fields as long as there are spaces, it seems that if there is no spaces then all control is lost e.g. 600px width table example;


 * Wrapping failure caused by long URI so Version field fails as well
 * Shorter url and the Version field works

--Zven 21:56, 4 September 2007 (UTC)

Is it really necessary to have the URLs spelled out in their entirety here? How about using a  approach at least on the long ones? Could the bot discriminate? Or, alternatively, a CSS setting that allows browsers to hide excess characters, such as  along with truncate or scolling, e.g.? --Purodha Blissenbach 14:58, 9 September 2007 (UTC)

I've got it: User:Pronoiac/Extension_Matrix_scrolling is a demonstration. It looks like most of the fields don't have wrapping on. Replacing long urls might help too, but they're secondary. - Pronoiac 00:23, 27 February 2008 (UTC)

type vs. type1, type2, etc.
Template:Extension recommends using type1, type2, etc. when more than one type applies. Extension Matrix lists only the "type" value. Would it be possible to inlcude type1, type2, etc. when they are present? Svemir Brkic 02:02, 4 November 2007 (UTC)


 * fixed -- Duesentrieb ⇌ 11:32, 12 December 2007 (UTC)

Warning message
When I access this page now I get the following warning message appearing;

disclaimer
... The provisions of the general disclaimer are maintained. warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql-text12/mediawikiwiki) closed! reopening. - warning: external store db connection (sql- ... Is this warning related to the latest MediaWiki build? --Zven 22:50, 11 December 2007 (UTC)


 * No, the warning is related to a slightly broken setup on the server which runs the bot which updates this page. Should get better soon. Sorry for the mess. -- Duesentrieb ⇌ 01:30, 12 December 2007 (UTC)

Matrix Working?
Hello Duesentrieb, I have entered my extension Extension:WordPress_Comments on Dec 18 - it still has not shown up in the Extension Matrix. Is there some moderation which goes on or is there another problem? Regards, --Supertick 04:52, 21 December 2007 (UTC)

Is this working?
I am not sure if this matrix is working any more. There are several error messages like this one:

Also it is February 12th and there are no edits since January listed. That seems very very very unlikely.

My guess is that the bot that makes this page as had a problem. --Vaccano 17:14, 12 February 2008 (UTC)


 * Boerni: Is by me too, my Extension is DeezerSong Boerni 17:44, 12 February 2008 (UTC)

Two Rows per Entry
If all of the data were for a particular extension were presented in a single row, making it much easier to export to a spreadsheet. The two-rows-per-entry way it's presented now is not very effective for non-human parsing.

From Wikipedia's "Comparison" pages: class="sortable wikitable" style="width: auto; text-align: center; font-size: smaller" Siokaos 16:43, 14 February 2008 (UTC)