- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
Difference between revisions of "User talk:Loci"
(suggestions) |
(→Variations: new section) |
||
Line 44: | Line 44: | ||
::Thank you. While I don't see any significant problems in the code, I do see several paths that could lead #df_raw to return without the raws. You suggested above that the job queue is running on a separate server. Are the two config variables $wgDFRawEnableDisk and $wgDFRawPath setup correctly on this server? You might also try setting the correct values in DFRawFunctions.php directly, in case the global config values aren't being applied when the job queue is run. Whichever user is running to process the job queue needs to have read permissions to the raws directory and all files and subdirectories inside. That user may also need directory-list/execute permissions on those directories as well. --[[User:Loci|Loci]] 17:11, 14 February 2013 (UTC) | ::Thank you. While I don't see any significant problems in the code, I do see several paths that could lead #df_raw to return without the raws. You suggested above that the job queue is running on a separate server. Are the two config variables $wgDFRawEnableDisk and $wgDFRawPath setup correctly on this server? You might also try setting the correct values in DFRawFunctions.php directly, in case the global config values aren't being applied when the job queue is run. Whichever user is running to process the job queue needs to have read permissions to the raws directory and all files and subdirectories inside. That user may also need directory-list/execute permissions on those directories as well. --[[User:Loci|Loci]] 17:11, 14 February 2013 (UTC) | ||
+ | |||
+ | == Variations == | ||
+ | |||
+ | Thanks for fixing up the issues with namespaces and large/gigantic variations (although I must admit, "Tis" is pretty interesting). I tried adding spaces to [[:Template:Creature/basename]], but I'm unsure if #mreplace is aware of spaces. It looks like the variations don't show up on [[DF2012:Giant mantis]] (although I neglected to see if they did before, but they probably didn't, since Giant mantis man and Giant giant mantis don't exist). The link is still incorrect on [[:Template:Creature/variation links]], however. Also, I created [[:Template:Creature/exists]] as a potential replacement for #ifexists (which is "expensive" - the examples at [[:Template:Creature/variation links]] list an expensive function count of 68/100). A DFRaw function should do the trick, but I have yet to find a working solution. The problem I ran into previously was how the raws of base creatures contain no references to variations. I suppose, as a workaround, we could have a script build a cache-type template (probably run outside of the wiki and generating template code), but it would likely break easily with updates and take up a lot of space for a template. --{{User:Lethosor/sig}} 22:55, 5 March 2013 (UTC) |
Revision as of 22:55, 5 March 2013
I've been seeing your edits on the recent changes page for a while now. Good job. :-) Emufarmers 08:22, 6 December 2012 (UTC)
Thanks for the information regarding creating new pages. I have removed my question from where I posted it and will add a Wiki Editing section to the FAQ. 13thEssence 00:30, 5 February 2013 (UTC)
Creature Type Pages
Are those supposed to be stub articles, or did you mean to create them as categories? --Quietust 22:28, 19 December 2012 (UTC)
- Mainly I created them as stub articles so I would have somewhere to link the "interesting" attributes in the creature info box. That way the info box can just say "No Stun" with a link to more information if the user desires, but without cluttering up the info box with excessive common knowledge. While I also considered adding these tags as categories to the proper creature pages, I haven't put in the time to make that all work yet. --Loci 22:35, 19 December 2012 (UTC)
- Eh, I tried to set up categories for the various "interesting" attributes, but the creature pages would display the categories without actually being assigned to the categories. Presumably it was a problem with transclusion depth, or formatting, or something. Someone more familiar with the system could probably get it to work, but I didn't feel like spending any more time on the problem so I removed the categories. --Loci 12:39, 20 December 2012 (UTC)
- That's because you were just inserting page links - if you wanted to put them in categories, you should've used [[Category:DF2012:whatever]] rather than just [[whatever]]. --Quietust 13:52, 20 December 2012 (UTC)
- Eh, I tried to set up categories for the various "interesting" attributes, but the creature pages would display the categories without actually being assigned to the categories. Presumably it was a problem with transclusion depth, or formatting, or something. Someone more familiar with the system could probably get it to work, but I didn't feel like spending any more time on the problem so I removed the categories. --Loci 12:39, 20 December 2012 (UTC)
- Not quite. I actually had added the categories using the {{Category|foo}} template, but removed them because they didn't work. Your links aren't working for me, either. When I click on Category:DF2012:Flying, for instance, I get "This category currently contains no pages or media." If, however, I add the category template {{Category|Flying}} to a creature page directly, the creature shows up on the category page. However, I certainly don't want to modify each and every creature page individually, so any workable solution has to be based on a template transcluding data from the creature /raws. If the creature pages won't register in the categories, I'd rather have the links to the "stub articles" than links to non-functional categories. --Loci 14:24, 20 December 2012 (UTC)
- Using {{Category|foo}} will include it in the category and {{Catlink|foo}} will make an actual link appear on the page - if you want both to happen, then you need to use both of those (see {{attrib proc}} which I just recently modified). --Quietust 14:50, 20 December 2012 (UTC)
- Not quite. I actually had added the categories using the {{Category|foo}} template, but removed them because they didn't work. Your links aren't working for me, either. When I click on Category:DF2012:Flying, for instance, I get "This category currently contains no pages or media." If, however, I add the category template {{Category|Flying}} to a creature page directly, the creature shows up on the category page. However, I certainly don't want to modify each and every creature page individually, so any workable solution has to be based on a template transcluding data from the creature /raws. If the creature pages won't register in the categories, I'd rather have the links to the "stub articles" than links to non-functional categories. --Loci 14:24, 20 December 2012 (UTC)
- If you click on Category:DF2012:Flying, you will find that the majority of creatures with flying are *not* currently included. This is exactly the same problem I ran into with my revision 179580, which looks remarkably similar to your revsion 179609. In short, the creature pages show the category links, but aren't actually added to the category until the creature page is edited directly (the three flying creatures currently listed in the category have all been edited since your change). That means the categories won't be complete until *every* creature page with an ability has been edited (or the category lists are administratively regenerated), which is why I chose to revert the categories and just link to an ability page. --Loci 23:15, 1 January 2013 (UTC)
- Well, it was empty... then when I edited Giant bat it was added to the category page (even though I didn't edit the creatureinfo box). I only added a sentence about how much fun giant bats are to see what would happen. Strange that just editing a page would add it to a category... --Lethosor (talk) 02:47, 13 February 2013 (UTC)
- Yep; that's exactly the problem I ran into. For a technical explanation: whenever a template is edited, the wiki software queues up jobs to automatically "regenerate" all the pages that include that template. As those jobs are processed, the pages should pick up new categories from the template. Unfortunately, the wiki software is not handling this specific case correctly--it appears that the raws are not being transcluded correctly during the regeneration, leading the conditional logic to conclude that no creature has the [FLIER] tag. When users edit the creature pages, though, the categories are regenerated correctly because the raws are transcluded correctly. I'm still looking for a solution to resolve the automatic regeneration problem, but since it only happens in the server's back-end processing it's hard to pin down. --Loci 08:47, 13 February 2013 (UTC)
- Wow, I just noticed you said pretty much exactly what I said in the post before. Anyway, I noticed Template:Creaturelookup/0 is using "/raw" as the path to raws. Maybe the wiki software isn't resolving this path correctly (which could be hard to track down, like you said in the section below). --Lethosor (talk) 21:04, 13 February 2013 (UTC)
Regenerating cached categories
I will reset the caches this weekend. --Briess 09:48, 6 January 2013 (UTC)
- Thanks! --Loci 16:02, 6 January 2013 (UTC)
- It appears that the pages still aren't being categorized--the jobs are likely stuck in the Job Queue (currently 730 jobs waiting). Manually running the queue will hopefully put everything in the proper categories. --Loci 21:35, 7 January 2013 (UTC)
- I simply forgot to clear the appropriate caches. The full job queue is run on a scripting server every 30 seconds, that estimate is always wrong. --Briess 21:19, 10 January 2013 (UTC)
- For context, a single page rebuild creates about 100 jobs in the queue, so the expected number of jobs for this reset should be in the 10k-100k range. --Briess 21:20, 10 January 2013 (UTC)
Just an update - clearing the cache failed because of some silly issues with the way mediawiki creates jobs. We will need to null edit every page in order to get things working properly again. I will probably set up a bot to do this for us. --Briess 05:48, 11 January 2013 (UTC)
- That, sadly, does not sound like a very workable solution. When I changed the formatting in one of the templates, all the categories were emptied again. So all the creature pages would probably have to be null-edited again after every change to any template on the creature pages. Unless the bot can be fully automated, the categories are practically guaranteed to be incomplete. In light of these problems it would perhaps be best to scrap the categories entirely. --Loci 19:03, 25 January 2013 (UTC)
- Let's not do that yet. I'm planning on upgrading mediawiki again shortly, and I believe there are fixes to this issue in newer versions of the software. --Briess 01:26, 26 January 2013 (UTC)
I did some experimentation on this problem; the automatic regeneration is running, but it appears that the creature raws are not being transcluded correctly during the regeneration, which prevents detection of the necessary tags. I believe the #df_raw function is not correctly returning the raws when executed from the context of the job queue process--is that something you could take a look at? Alternately, is this code available somewhere I could take a look at it? Unfortunately, since this is probably DFwiki-specific code, I doubt a Mediawiki update will fix it. --Loci 09:12, 13 February 2013 (UTC)
- Thank you. While I don't see any significant problems in the code, I do see several paths that could lead #df_raw to return without the raws. You suggested above that the job queue is running on a separate server. Are the two config variables $wgDFRawEnableDisk and $wgDFRawPath setup correctly on this server? You might also try setting the correct values in DFRawFunctions.php directly, in case the global config values aren't being applied when the job queue is run. Whichever user is running to process the job queue needs to have read permissions to the raws directory and all files and subdirectories inside. That user may also need directory-list/execute permissions on those directories as well. --Loci 17:11, 14 February 2013 (UTC)
Variations
Thanks for fixing up the issues with namespaces and large/gigantic variations (although I must admit, "Tis" is pretty interesting). I tried adding spaces to Template:Creature/basename, but I'm unsure if #mreplace is aware of spaces. It looks like the variations don't show up on DF2012:Giant mantis (although I neglected to see if they did before, but they probably didn't, since Giant mantis man and Giant giant mantis don't exist). The link is still incorrect on Template:Creature/variation links, however. Also, I created Template:Creature/exists as a potential replacement for #ifexists (which is "expensive" - the examples at Template:Creature/variation links list an expensive function count of 68/100). A DFRaw function should do the trick, but I have yet to find a working solution. The problem I ran into previously was how the raws of base creatures contain no references to variations. I suppose, as a workaround, we could have a script build a cache-type template (probably run outside of the wiki and generating template code), but it would likely break easily with updates and take up a lot of space for a template. --Lethosor (talk) 22:55, 5 March 2013 (UTC)