Template talk:Cargo weapons poe2

Symbols in (page)name
Just noticed (as of January 3, 2019) that the List of soulbound items (Deadfire) displays e.g. The Weyc's Wand (which has its name written out inside the infobox) as "The Weyc& # 39 ;s Wand" (had to break up the code to show it). This isn't the case on List of soulbound items. One difference between Template:Cargo weapons and Template:Cargo weapons poe2 is that the latter has an additional "_pageName=pageName, " inserted before "name" for the fields of the Cargo query. But if I hide this, no name at all is shown, instead a missing parameter … --  -- You talkin' to me? -- cCContributions -- 14:09, 3 January 2019 (UTC)


 * The use of both pageName and name is for the ability to use a label  in the constructed table. You may have noticed I've been changing   in the name field of some items to the plain text form. I've been doing this specifically for pages that have an apostrophe in them (or any special symbol). This is because cargo doesn't properly escape symbols that have to be resolved/expanded out from a template within a field, resulting in   - the HTML code for an apostrophe - being stored in cargo instead of the regular text.


 * Now, you might look at the page of The Weyc's Wand and see that the name is stored in plain text there. Well, this ties back to another big issue with soulbound items not being updated in cargo correctly (I will add something to the noticeboard later about this). You'll have to take my word for it when I say that that particular item (among others) is still storing it's name field as . If you take any other, non-soulbound item with an apostrophe and change the name field to Pagename nd, you'll find that the cargo table will store it like above, therefore propagating to any queries that may retrieve the name field, resulting in symbols on the other end. Ultimately, this is an issue with cargo and not this template in particular. A circumvention would be to pass only the pageName through to the row template, and then do the de-disambiguation outside of cargo (and therefore only making use of the pageName). Sadly issues with Cargo like this are the reason is why we can't have nice things. Macklin (talk) 15:06, 3 January 2019 (UTC)


 * But you're working fine on that last thing! :)
 * Is it because you used "amp" in your coding of the code? When I tried ) is to break it by substituting the ampersand character literal with the ampersand character HTML pattern  - as seen when editing this page. Kind of funny if you think about it.
 * I actually tested  a while ago, don't remember if it worked or not. It would make sense in this case, but I don't really want to bother with it if I'm honest. Anyway, I've made the changes I mentioned above - just have to save them. And the other soulbound thing is nothing special, really just me complaining that stuff doesn't work. :D Macklin (talk) 15:42, 3 January 2019 (UTC)