Forum:DynamicePageList

From Star Wars: The Old Republic Wiki
Jump to: navigation, search

Forum index > DynamicePageList

Hi all, Is it possible to install this extension on this wiki: http://www.mediawiki.org/wiki/Extension:Intersection ? I used a lot on LOTRO Wiki. It allow to build simple list based on multiple categories (With AND, OR, NOT operator). It would ease a lot that kind of pages: http://www.wikiswtor.com/Codex and should avoid manual edit/update each time we get new content. Keep me update ;) Zophar 09:25, 28 February 2012 (UTC)

I guess I don't understand the advantage for smaller lists or specific content lists. In the case of the page you linked to, we'd still have to manually arrange and format the links, wouldn't we? And wouldn't we have to manually update the function every time something about the process changed as well? Perhaps an example of its use from LOTRO Wiki would help to understand its usefulness? -- Heaven's Agent 14:32, 28 February 2012 (UTC)
Currently I have no good exemple on LOTRO... Well we used it to sort stub article in a certain categories (missing image, missing related article, ...). Maybe i did not well explain (I speak french...). Anyway thae this page: http://www.wikiswtor.com/Codex/Galactic_Republic. In this page we have all codex attributed to Republic codex categories and there are also part of other categories (Bestiary, Lore, Locations, ...). With category intersection you could simply give tag like that:

Extension:DynamicPageList (DPL), version 3.3.2: Warning: Unknown parameter '::category' was ignored. Help: available parameters: addauthor, addcategories, addcontribution, addeditdate, addexternallink, addfirstcategorydate, addlasteditor, addpagecounter, addpagesize, addpagetoucheddate, adduser, allowcachedresults, allrevisionsbefore, allrevisionssince, articlecategory, cacheperiod, categoriesminmax, category, categorymatch, categoryregexp, columns, count, createdby, debug, distinct, dominantsection, eliminate, escapelinks, execandexit, firstrevisionsince, fixcategory, format, headingcount, headingmode, hiddencategories, hitemattr, hlistattr, ignorecase, imagecontainer, imageused, include, includematch, includematchparsed, includemaxlength, includenotmatch, includenotmatchparsed, includepage, includesubpages, includetrim, inlinetext, itemattr, lastmodifiedby, lastrevisionbefore, linksfrom, linksto, linkstoexternal, listattr, listseparators, maxrevisions, minoredits, minrevisions, mode, modifiedby, multisecseparators, namespace, noresultsfooter, noresultsheader, notcategory, notcategorymatch, notcategoryregexp, notcreatedby, notlastmodifiedby, notlinksfrom, notlinksto, notmodifiedby, notnamespace, nottitlematch, nottitleregexp, notuses, offset, oneresultfooter, oneresultheader, openreferences, order, ordercollation, ordermethod, qualitypages, randomcount, redirects, replaceintitle, reset, resultsfooter, resultsheader, rowcolformat, rows, rowsize, scroll, secseparators, showcurid, shownamespace, skipthispage, stablepages, suppresserrors, table, tablerow, tablesortcol, title, titlegt, titlelt, titlematch, titlemaxlength, titleregexp, usedby, userdateformat, uses.


Extension:DynamicPageList (DPL), version 3.3.2: Warning: Unknown parameter '::category' was ignored. Help: available parameters: addauthor, addcategories, addcontribution, addeditdate, addexternallink, addfirstcategorydate, addlasteditor, addpagecounter, addpagesize, addpagetoucheddate, adduser, allowcachedresults, allrevisionsbefore, allrevisionssince, articlecategory, cacheperiod, categoriesminmax, category, categorymatch, categoryregexp, columns, count, createdby, debug, distinct, dominantsection, eliminate, escapelinks, execandexit, firstrevisionsince, fixcategory, format, headingcount, headingmode, hiddencategories, hitemattr, hlistattr, ignorecase, imagecontainer, imageused, include, includematch, includematchparsed, includemaxlength, includenotmatch, includenotmatchparsed, includepage, includesubpages, includetrim, inlinetext, itemattr, lastmodifiedby, lastrevisionbefore, linksfrom, linksto, linkstoexternal, listattr, listseparators, maxrevisions, minoredits, minrevisions, mode, modifiedby, multisecseparators, namespace, noresultsfooter, noresultsheader, notcategory, notcategorymatch, notcategoryregexp, notcreatedby, notlastmodifiedby, notlinksfrom, notlinksto, notmodifiedby, notnamespace, nottitlematch, nottitleregexp, notuses, offset, oneresultfooter, oneresultheader, openreferences, order, ordercollation, ordermethod, qualitypages, randomcount, redirects, replaceintitle, reset, resultsfooter, resultsheader, rowcolformat, rows, rowsize, scroll, secseparators, showcurid, shownamespace, skipthispage, stablepages, suppresserrors, table, tablerow, tablesortcol, title, titlegt, titlelt, titlematch, titlemaxlength, titleregexp, usedby, userdateformat, uses.


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


Extension:DynamicPageList (DPL), version 3.3.2: Error: You need to include at least one category, or specify a namespace!


Extension:DynamicPageList (DPL), version 3.3.2: Error: No results!

And get a nice formatted list of all codex for the republic in the bestiary section. Then use another tag for Lore and Locations... No need to browse each categories to update this page, it's dynamicaly updated. Zophar 14:40, 28 February 2012 (UTC)
Dynamic Page List is a powerful extension, the version most often used is the 3rd party one due to it's expanded features, however, it isn't allowed on Curse wikis due to the security risks it poses. This extension is also very resource heavy, creating a large load on the servers. I have submitted a request to our IT Team to see if they'd be willing to have the version you are asking for used on our network. I will let you know what they say.-- Wynthyst 19px talk 15:42, 28 February 2012 (UTC)
Before we could get much use of the extension we'd need to design a formal Manual of Style and category structure, both of which we currently lack; if our articles were all categorized uniformly we could use the extension in the manner described, but that simply is not the case. Our contributors add articles to categories based on what seems best at the article's creation, and in large part we haven't taken the time to decide which categories to maintain and which to discard.
As a quick aside, is it possible to alter the way the links appear? For practical purposes our codex articles take the form of subpages, but the parent identifier "Codex/" should not be present within the link lists themselves. We would want the list to display Satele Shan, not Codex/Satele Shan. -- Heaven's Agent 17:32, 28 February 2012 (UTC)
Well, establishing the category tree is something that should always be a priority (imo), so you might want to take a look at that. As for displaying only the subpage name in links, use {{SUBPAGENAME}} in your template. -- Wynthyst 19px talk 17:38, 28 February 2012 (UTC)
What I'm asking is if {{SUBPAGENAME}} can be used with the <DynamicPageList> extension. I've been doing some looking and in every instance I've seen it used the extension generates a list of article links that displays the article's entire name.
I would agree about the importance of establishing a proper category structure, but our past attempts have failed due to artificial limitations place upon us. Until these limitation can be eliminated or circumvented a single cohesive structure is unlikely to develop. For me, at least, I don't know where to start in regard to this task; the tools and processes I'm familiar with using in developing such a structure are prohibited here. -- Heaven's Agent 18:01, 28 February 2012 (UTC)
I'm not as familiar with this version of DPL as I am the third party one, but I know in that one, you tie your DPL call to templates. Those templates are built basically like any other, so use of magicwords would be possible. I would have to do a bit more study to learn exactly how this version of DPL functions before I could say for sure.
As for the category tree structure, just what tools do you need? I generally use a simple spreadsheet or organization chart to work out the category tree. I generally start with a root category (Category:Main), then branch it into Category:Star Wars: The Old Republic for all Game related stuff (races, classes, missions, codex, items, weapons, starships, etc.), and Category:Star-Wars-The-Old-Republic-Wiki for all wiki specific stuff (Templates, images, policies, community portal etc) and work out from there. Here, I would probably add a 3rd branch for Guilds and guild related content. Of course, that's just the way I do it. -- Wynthyst 19px talk 00:31, 2 March 2012 (UTC)
Well, in all honesty I'm personally unable to build a category structure without the use of subpage categorization. I suffer from a bit of a learning disability, and am unable to distinguish and navigate organizational structures of that complexity without breaking the structure up with things like a parent suffix. I literally cannot navigate most category structures, including the bits we currently have in place, more than three levels as a result; I have to construct models of sections of the structure on my wall for the articles I'm currently working on in order to keep the categories straight in my head. There's no way I could work toward building an entire structure of that nature.
I had initially been building a subpage-based category structure, something I was going to introduce to the community as it neared completion, when you dictated we would not use that method on this project at all. My attempts to get you to change your mind met with no results, Wyn, so I was forced to scrap my work. To be honest, the situation still irritates me. The fact that my effort came to nothing wouldn't be so upsetting, though, if something else had been instituted in its place. I had mentioned this at the time when initial progress was being made, but it stopped shortly after. Unfortunately no one has stepped forward to finish this task, and now we are left with no defined category structure when I had nearly finalized my work. It is still very much a sore spot with me, one that I am unable to forget because I am forced to face it every time I author an article. -- Heaven's Agent 04:41, 2 March 2012 (UTC)

Category structure[edit source]

Heaven, do you have your work in electronic format? If you want to share with me what structure you built out previously, I can help convert it not use subpages. If not, I'll continue working out a structure we can use. --Icon class jediknight.png Alianin T C 12:57, 2 March 2012 (UTC)

No, I scrapped it, primarily out of frustration. I tried to adapt it to a form that didn't use a subpage-based structure, but it didn't go well. It quickly became apparent that it would take just as long to convert the work as it took to define it in the first place, if not more. Even if I had somehow managed to complete the work, I wouldn't be able to understand the structure enough to explain, implement, or utilize it.
My mind takes in information too quickly for me to consciously process. I've been told it might be a type of dyslexia. The information in my working memory gets replaced before it can be processed and moved to my permanent memory. I equate it to standing at a railway crossing and attempting to read the graffiti on the freight cars as they go past: I can focus on a single aspect of one car, and by paying attention to it alone I can read the content before it is out of sight, but I can't recall its context. The cars surrounding it and its placement in the train are completely lost to me. If I try to see the bigger picture, everything's lost; the cars are reduced to a blur of information and I cannot gain any meaning whatsoever.
For some reason non-alphanumeric characters seem to slow the flow of information. The backslash in a subpage title acts as a speed bump, slowing the rate at which I perceive information to the point that I can understand and recall it later. Without this sort of control I quickly become overwhelmed. It's for this reason that I am literally unable to use a category structure like the one we are looking to implement, and as a result there is no way that I can help design it. -- Heaven's Agent 15:18, 2 March 2012 (UTC)