Module talk:Portal-inline

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

July 2020[edit]

At Template:God the image is on the previous line of the display name. This leaves an image with no context.

I suggest adding a Nbsp to the module.

Change:

root = root .. string.format('[[File:%s|class=noviewer|%s]] [[Portal:%s|%s]]', getImageName{ portals[1] }, args['size'], portals[1], displayName)

to

root = root .. string.format('[[File:%s|class=noviewer|%s]] [[Portal:%s|%s]]', getImageName{ portals[1] }, args['size'], portals[1], displayName)

Unfortunately I couldn't testcase this change in the sandbox as I struggled to figure out how to do this. Your help is appreciated, comrade waddie96 (talk) 17:23, 16 July 2020 (UTC)[reply]

 DoneJonesey95 (talk) 17:37, 16 July 2020 (UTC)[reply]
Thank you Jonesey95, comrade waddie96 (talk) 12:23, 17 July 2020 (UTC)[reply]

Template-protected edit request on 3 June 2022[edit]

I'm not sure exactly why, but when an image border is specified in Module:Portal/images, it passes through to {{portal}} but not to {{portal-inline}}. I'm only talking about the border around the portal image itself, not the whole template. I noticed this regarding Afghanistan. A border is specified around the white flag of Afghanistan at Module:Portal/images/a, but only appears on the former template, not the latter. ― Tartan357 Talk 23:07, 3 June 2022 (UTC)[reply]

{{portal|Afghanistan}}
{{portal-inline|Afghanistan}}       flag Afghanistan portal
There was a subtle bug where the border, alt, and link data were being stripped from Module:Portal/images before being returned to Module:Portal-inline. I hope this wasn't intentional. I made a simple change to stop the stripping. If an image border is specified in the database, then now gets used by {{Portal-inline}}. As a side effect, |alt= and |link= arguments to the image are now also set to whatever is specified in the database. These are mostly empty. I think this is a good thing, but if other editors object, we can try to fix. — hike395 (talk) 05:09, 4 June 2022 (UTC)[reply]