Possible bug - missing images on page names with apostrophes | Fandom

Pusillanimous·5/14/2018 in Portability Bugs

Possible bug - missing images on page names with apostrophes

Hi all! We just updated our main infobox to portable markup site-wide over on the Eternal Card Game Wiki. I've noticing a strange quirk, I'm not sure if its a bug or just something I'm missing.

I set up the infobox title and main image to use the page's name by default, unless an alternative title or image is specified in the template parameters. Here's the markup:

  <title source="title">
    <default>{{PAGENAME}}</default>
  </title>
  <image source="image">
    <default>{{{title|{{PAGENAME}}}}}.png</default>
  </image>

For most pages, the update appears perfectly fine.

The issue is on pages with an apostrophe (') in the title — for some reason the image only appears if the page's name is written out in the ""title" parameter (or the file name in the "image" parameter). Writing "{{PAGENAME}}.png" in the "image" parameter also results in a missing image.

Is there some weird interaction between {{PAGENAME}}, apostrophes, and portable infoboxes?

Also, I assume it shouldn't affect this issue but we also added some new CSS for the infobox update.

(Edited by Pusillanimous)

0

FishTank·5/14/2018

It's not necessarily a weird interaction or bug. in the image call, you're pointing to a file page name, so you are likely better off with {{PAGENAMEE}} than {{PAGENAME}}. Note the extra E, which produces an encoded value (and should smooth out the apostrophe issue).

(Edited by FishTank)

0

Pusillanimous·5/14/2018

Thanks, that did the trick!! Glad it was a gap in my knowledge rather than a bug.

Weird thing though, with the original (non-portable) infobox {{PAGENAME}} worked fine to display the image on those same pages. For some reason only the updated infobox needs the extra E. I'm guessing the old infoboxes process the magic word before calling the image while the new one does the opposite.

(Edited by Pusillanimous)

0

FishTank·5/14/2018

Image-rendering links are interpreted differently and sanitized in a different way inside Portable Infoboxes to present them in an optimal format. So that's not entirely surprising that the internal call would need the proper (from the server's perspective) page name format.

(Edited by FishTank)

0

Pusillanimous·5/14/2018

Thanks for the explanation too! We have some old pages with a manual "image={{PAGENAME}}.png" parameter that need cleaning up, but I'm glad this was a non-issue going forward :)

(Edited by Pusillanimous)

What do you think?