![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 | Archive 5 |
![]() | Please dream up new features, and post threads for them below... |
For accessibility, for example. — The Transhumanist 03:11, 28 May 2018 (UTC)
When purging, you get this page, rather than an actual purge: https://en.wikipedia.org/?title=Portal:Sacramento,_California&action=purge
Is there any way we can make purge links purge directly, without the confirmation page? — The Transhumanist 00:41, 6 June 2018 (UTC)
@ Cesdeva, Evad37, Certes, AfroThundr3007730, Wpgbrown, Waggers, Nihonjoe, Finnusertop, and Greatedits1:
The {{ portal}} template seems dated and unappealing.
Once the revamping of portals is complete, it might be nice to upgrade the links leading to them, as a way to announce the new and improved portal system. True, this is a long ways off, but now is the time to start thinking about the presentation of the system for when the upgrade is complete. Toward this end, here are some questions...
What are the applications of {{ PortalButton}}? What can they be used for?
What is the feasibility of implementing {{ PortalButton}} for all portals?
Could Module:Portal and Module:Portal/images be expanded/adapted to handle Portalbuttons?
Cesdeva, I'm especially interested in what you envisioned, and what other potential applications you foresee for these.
The idea is to drive traffic to the portals. Thoughts? — The Transhumanist 21:40, 16 June 2018 (UTC)
photographs myself already and have been working on some SVG's. The standard image alt= already works fine, and no-one said anything about not conforming to policy on contrast. There's always a lot of hot air being blown when new design features appear and it's all fairly weightless naysaying. Perhaps that is why the portal space is in, and will remain in, such a state. I'll leave you guys to keep polishing your turds. Cesdeva (talk) 15:13, 17 June 2018 (UTC)
Evad37 wrote above: "I think minor improvements to the existing templates, or some new way of using the existing icons, would be a better way to go."
@ Certes, Evad37, Nihonjoe, and Wpgbrown:
During the conversion of portal introduction sections from using static excerpts and subpages, I noticed that picture support of the lead section in articles seems to be migrating to each article's infobox, rendering many leads otherwise pictureless.
The main ramification for portals is that {{
Transclude lead excerpt}} and {{
Transclude random excerpt}} present bare prose without picture support when used to present excerpts from articles supported by infobox pictures, rendering the files=
parameter useless for those articles.
It would be really cool if these templates and their corresponding lua module could be enhanced so that the files=
parameter recognizes pictures at the top of the article's infobox. Thoughts? —
The Transhumanist
03:11, 17 June 2018 (UTC)
The gharial (Gavialis gangeticus), also known as gavial or fish-eating crocodile, is a crocodilian in the family Gavialidae and among the longest of all living crocodilians. Mature females are 2.6 to 4.5 m (8 ft 6 in to 14 ft 9 in) long, and males 3 to 6 m (9 ft 10 in to 19 ft 8 in). Adult males have a distinct boss at the end of the snout, which resembles an earthenware pot known as a ghara, hence the name "gharial". The gharial is well adapted to catching fish because of its long, narrow snout and 110 sharp, interlocking teeth.
The gharial probably evolved in the northern Indian subcontinent. Fossil gharial remains were excavated in Pliocene deposits in the Sivalik Hills and the Narmada River valley. It currently inhabits rivers in the plains of the northern part of the Indian subcontinent. It is the most thoroughly aquatic crocodilian, and leaves the water only for basking and building nests on moist sandbanks. Adults mate at the end of the cold season. Females congregate in spring to dig nests, in which they lay 20–95 eggs. They guard the nests and the young, which hatch before the onset of the monsoon. The hatchlings stay and forage in shallow water during their first year, but move to sites with deeper water as they grow. ( Full article...)
Snakes are elongated, limbless reptiles of the suborder Serpentes ( /sɜːrˈpɛntiːz/). Like all other squamates, snakes are ectothermic, amniote vertebrates covered in overlapping scales. Many species of snakes have skulls with several more joints than their lizard ancestors, enabling them to swallow prey much larger than their heads ( cranial kinesis). To accommodate their narrow bodies, snakes' paired organs (such as kidneys) appear one in front of the other instead of side by side, and most have only one functional lung. Some species retain a pelvic girdle with a pair of vestigial claws on either side of the cloaca. Lizards have independently evolved elongate bodies without limbs or with greatly reduced limbs at least twenty-five times via convergent evolution, leading to many lineages of legless lizards. These resemble snakes, but several common groups of legless lizards have eyelids and external ears, which snakes lack, although this rule is not universal (see Amphisbaenia, Dibamidae, and Pygopodidae).
Living snakes are found on every continent except Antarctica, and on most smaller land masses; exceptions include some large islands, such as Ireland, Iceland, Greenland, and the islands of New Zealand, as well as many small islands of the Atlantic and central Pacific oceans. Additionally, sea snakes are widespread throughout the Indian and Pacific oceans. Around thirty families are currently recognized, comprising about 520 genera and about 3,900 species. They range in size from the tiny, 10.4 cm-long (4.1 in) Barbados threadsnake to the reticulated python of 6.95 meters (22.8 ft) in length. The fossil species Titanoboa cerrejonensis was 12.8 meters (42 ft) long. Snakes are thought to have evolved from either burrowing or aquatic lizards, perhaps during the Jurassic period, with the earliest known fossils dating to between 143 and 167 Ma ago. The diversity of modern snakes appeared during the Paleocene epoch ( c. 66 to 56 Ma ago, after the Cretaceous–Paleogene extinction event). The oldest preserved descriptions of snakes can be found in the Brooklyn Papyrus. ( Full article...)
|weird_image_parameter_name = imagename.png
(I can fix those). With
Snake, the image we're after is inside <imagemap>...</imagemap>
tags within an infobox template parameter. I'm leaving that one to the experts!
Waggers
TALK
09:35, 18 June 2018 (UTC)
I've heard that Wikipedia forks augment WP's content in various ways. Are you aware of any? Perhaps we could implement something similar or better. — The Transhumanist 08:41, 17 June 2018 (UTC)
Is this possible? — The Transhumanist 06:14, 20 June 2018 (UTC)
See User:Evad37/sandbox/portal for a possible implementation. It doesn't look quite right in some skins, but I think that should be fixable once TemplateStyles is available. - Evad37 [ talk 03:17, 21 June 2018 (UTC)
Can a section be done in such a way that it is one thing for mobile viewers, and something else for non-mobile viewers?
For example, can Picture slideshow sections be presented as Selected picture sections for mobile viewers? Otherwise, portals with picture slideshows are essentially broken to a majority of our viewers. Thoughts? — The Transhumanist 01:44,? 30 June 2018 (UTC)
nomobile
, but I don't think there's any equivalent for hiding things on desktop only. -
Evad37 [
talk
15:35, 9 July 2018 (UTC)
This would be similar to {{ Transclude list item excerpt}}, but instead of gathering list items, it would gather thumbnail pictures (thumbnails, because those have captions). Then it would pick one at random and display it, adjusted to fit the width of the section it is in (like the picture size is adjusted in {{ Random slideshow}}. This one, however is not intended to be a slideshow, but is for powering "Selected picture" sections. — The Transhumanist 09:19, 15 July 2018 (UTC)
![]() | General portal design discussions go here. |
Short on time, so briefly and bluntly: Is it possible to implement the ability to edit each "section" of the portal within the current one page portal model. If not, it may not be a good direction to continue in because I would actually argue that having a subpages for each section makes it easier to edit and manage the portal. Personally, I've never seen a problem with having 10 or so subpages for each portal. If being able to easily discern how many portals there are is the perceived issue, a category (e.g. Category:Main portal page) could be created along with a bot to place it on every portal page that is not a subpage (i.e. titles without a slash). — Godsy ( TALK CONT) 05:36, 7 June 2018 (UTC)
We should track these. By "one-page portal", I mean one that has no subpages of is own, not even header or footer subpages. — The Transhumanist 19:28, 7 June 2018 (UTC)
{{
portal maintenance status|subpages=single}}
at the top of the portal. -
Evad37 [
talk
00:42, 20 June 2018 (UTC){{
portal maintenance status|date=June 2018|subpages=single}}
so they're all tracked now. — AfroThundr (
u ·
t ·
c)
12:40, 15 June 2018 (UTC)
Quite a few portals use a banner image in the introduction or above it. By this I mean a wide panorama style image. Sometimes it includes an image of text, other times it is just for decorative purposes. There are technical problems with most of them.
If it does already, I have consistently failed to find either an example or an explanation of how to do it.
Is this a thing anyone here knows how to fix? · · · Peter (Southwood) (talk): 07:36, 6 July 2018 (UTC)
img
element, where you could then set width:100%
or whatever you like (see
this answer). That would require TemplateStyles though, as it can't currently be done inline. — AfroThundr (
u ·
t ·
c)
12:01, 6 July 2018 (UTC){{
Transclude linked excerpt|data page}}
on the page where the random article is to appear. If you can link a concrete example of a portal that should do this, then I'm willing to have a go at setting it up as a model.
Certes (
talk)
10:41, 3 June 2018 (UTC)
Is there any way of using a bot to take the list of DYKs from a project (ie JL-Bot recognized content listing output) and turn it into a wiki-coded text output with the DYKs (recent ones are now stored on the article's talk page). This would be a great help for small/sluggish projects where the new automated template doesn't produce much, if any, recent output, but the project has lots of old DYKs. I've previously done them myself by going to the talk page and cutting & pasting, but it's very time-consuming. Espresso Addict ( talk) 13:24, 8 July 2018 (UTC)
![]() | For discussion on template development, issues, etc. |
I have created some new flags, which in my view should be added to all portals as a kind of classification system.
If the portal has a peculiar layout or is an example of a design incompatible with the latest updates, tag it with {{ Non-standard portal flag}}, to avoid introducing errors, project bots and AWB users should skip pages with this flag.
Any portal with one or more active maintainers should be tagged with {{ Maintained portal flag}}, those maintainers should be responsible for deploying any updates, therefore project bots and AWB users should skip pages with this flag.
Portals which are not maintained, or where the maintainers want all the latest updates automatically, can be tagged with {{ Portal flag}}, project bots and AWB users should make sure to keep these portals up to date and free from errors.
All these flags are optional, but will make things much easier for everyone working on the project. I can add any additional features to these flags if needed. JLJ001 ( talk) 10:15, 29 May 2018 (UTC)
{{Portal flag|maintained=y|standard=y|wpport-autoedit=y|subpages=y|subpage-keep=y}}
wpport-autoedit
parameter above was for flagging if auto editing was allowed. —
AfroThundr (
t•
c)
13:42, 29 May 2018 (UTC)
subpages=y|subpage-keep=y
then. Parameters are cheap. Updated the example above. —
AfroThundr (
t•
c)
15:17, 29 May 2018 (UTC)@ JLJ001: what is the flag icon at the top of the page that {{ Maintained portal flag}} generates supposed to link to? At present it just links to a non-existent page "The page to link to. This is where you will be taken when clicking the icon" , which obviously takes you to the wiki page inviting you to start the non-existent article. Perhaps you could fix this? I'm reluctant to deploy this template until it's working 100% Cactus.man ✍ 17:19, 29 May 2018 (UTC)
Portal talk:{{PAGENAME}}
. (the talk page of whatever portal page it's on).
JLJ001 (
talk)
17:25, 29 May 2018 (UTC)Portal talk:{{BASEPAGENAME}}
so it will automatically link to the main talk page if used on first level subpages. However, this only goes one level down for second or third level supages. For Example:
Portal:Opera/Selected audio/20 will link to
Portal talk:Opera/Selected audio. There is nothing I can do about this, if talk page consolidation beyond that is needed, redirects could be used.
JLJ001 (
talk)
17:38, 29 May 2018 (UTC)unique=n && maintained=n
(free game for auto-editing)unique=y && maintained=n
(edit with care)unique=y && maintained=y
(don't touch)unique=n && maintained=y
(probably don't touch)I don't know why, but there is some bug were the portal template will affect the reflist template and stop the reflist from splitting into columns. One example is Newcastle United F.C., can someone good with templates have a look thanks. Govvy ( talk) 17:15, 31 May 2018 (UTC)
Can you subst: a template which in turn has subst: in it? How? — The Transhumanist 08:45, 5 June 2018 (UTC)
{{outer template|{{shim|{{inner template1|param=foo}}{{inner template2|param=bar}}...|shimparam=baz}}|outerparam=quux}}
shimparam
could be used to pass certain values from the inner templates as well (regex maybe?), if that's possible.<includeonly>...</includeonly>
tags. The only downside is that standard transclusion no longer works correctly (but that limitation can probably be overcome if necessary). See
[3],
User:Evad37/X1,
User:Evad37/X2 for examples. -
Evad37 [
talk
11:28, 5 June 2018 (UTC)Two of our maintenance flag templates, {{ maintained portal flag}} and {{ non-standard portal flag}}, were posted to WP:TFD. Concerns were raised about the validity of maintenance flag templates on Portal pages, specifically the visual flag indicator. These concerns were raised before, and I think we should iron these out before doing much more with these flags.
Previously discussed in #New Markers (which started in #We should use flags), was the need for a visual indicator to users during AWB maintenance runs that signified to the editor that a page met certain criteria that required special care when editing, such as being actively maintained, or using significantly unique markup and design. Currently the use of these flags is a bit inconsistent: They were intended to be placed on the root portal page, not necessarily every subpage in the tree (see Portal:Opera).
It should be noted that these flags add the portals in question to tracking categories. I'll also note that these types of statuses can also be recorded with the {{
portal flag talk}} template (still a work in progress), or added as additional parameters to {{
WikiProject Portals}}, the same way the |historical=
flag is done. Ideally we'd only need one template to record all of these statuses, in whichever namespace they should reside.
We currently track three different statuses for portals, with another planned:
These are the questions I want to start with:
Please post your thoughts and comments in the discussion section below.
Barring technical restrictions, the ideal end state would look like this:
This is now the current state of affairs:
@ The Transhumanist, Cesdeva, Evad37, Wpgbrown, Pbsouthwood, Certes, and Waggers: Pinging the usual players, input from everyone is welcome and appreciated. — AfroThundr ( u · t · c) 13:43, 6 June 2018 (UTC)
I've added an idea of where I think we should end up. I believe we should consolidate the flags into a single template, or one per namespace if a template is required for both. I think this would provide the best balance between allowing for portal maintenance flags while keeping our footprint in portal space small. That said, there may be things I haven't considered yet, hence the survey. I may need to revise this as the questions get answered. — AfroThundr ( u · t · c) 14:15, 6 June 2018 (UTC)
|maintained=yes
or any other value to turn on the "is maintained" note). This should make it easier for the module (which looks at the raw unexpanded wikitext of the portal page) to determine which notes apply. -
Evad37 [
talk
04:29, 8 June 2018 (UTC)
@ Evad37: First off, thanks for building that module. I have a couple questions and comments.
Just a few thoughts I had, I'll probably have more questions later. Thanks again. — AfroThundr ( u · t · c) 04:09, 8 June 2018 (UTC)
historical
is. It shouldn't be a problem since the portals will have to be manually triaged anyway. The editor can just set the flag manually, once they're done. Speaking of which, how much work would it be to make the template also detect {{
historical}} on the corresponding main page, and automatically set historical=y
for those too? And another thing: the other flags should have a parameter that can be set manually if {{
portal flag}} can't be used for some reason. Local values would override detected ones, or absent ones (although, maybe the template should display an error if it has conflicting values). — AfroThundr (
u ·
t ·
c)
14:49, 8 June 2018 (UTC)
|embed=
parameter to the template might make more sense, so as not to use up Lua time on portal pages – some of the other portal automation modules can take up a fair chunk of the allotted Lua processing time. -
Evad37 [
talk
07:14, 11 June 2018 (UTC)Issue raised in the TFD:
How is
tagging something as maintained is misleading since when it becomes unmaintained, the nonexistent maintainer doesn't remove itaddressable by editing? — JJMC89 ( T· C) 23:04, 8 June 2018 (UTC)
- The template just needs a
|date=
parameter, automatically filled in by AnomieBOT, and a process for removal, such as a portal_talk page message after some reasonable amount of time (e.g. six months), requesting that the maintainer update the date if they're still active, and automatic removal of the maintained status a short time later (e.g. one month) if not updated. - Evad37 [ talk 00:40, 9 June 2018 (UTC)- Or even skip the talk page message, as long as removal is done without a bot flag, and with a very clear edit summary. - Evad37 [ talk 00:44, 9 June 2018 (UTC)
No point making a bot request till other issues (TFD, merging) get resolved. But does six months sound about right for the timeframe? Can we do without a talk page message? - Evad37 [ talk 00:52, 9 June 2018 (UTC)
|date=
. In terms of the "fresh" status, the main reason I suggested a longer timeframe was to avoid annoying portal maintainers too often – a couple, or a few, edits a year seems reasonable, to show a sustained interest. And I don't think the "stale" period needs to be as long as 90 days – around four weeks should be enough, since its really just a grace period between the flags being valid and invalid. I think removal should require an actual edit (by bot, awb, or manually), rather than just template logic, so that it actually shows up on watchlists and page histories. We don't really extra "stale" or "outdated" categories, since the portals will already be in dated maintenance subcategories. -
Evad37 [
talk
07:01, 11 June 2018 (UTC)
I've started working on {{ Portal maintenance status}}, as a proposed merged template. Instead of a top-icon flag, it uses a hidden-by-default message box, which those working on portal maintenance can display with custom css. @ AfroThundr3007730: Did you want to add something for subpages to the template? - Evad37 [ talk 02:46, 9 June 2018 (UTC)
subpages=( (0|untriaged|<empty>) | (1|triaged) | (2|single[page]) )
This flag would be set when a portal has been pruned of unnecessary subpages ("unnecessary" being subjective) and any portals tagged with this template without that flag set would be added to
Category:Portals with untriaged subpages, and it would also populate
Category:Single-page portals, as appropriate. The intent, of course, is not to wage war on subpages so much as reduce their number to a manageable level, as has been discussed elsewhere on this page. Single page portals should have this set automatically, if possible. singlepage
flag, which could also be useful, and would populate another tracking category, that overrides the subpages flag. Just thinking out loud here.subpages
to the template. Now we just need to update the module to provide parity in the WikiProject banner. Also, can we make the template expose the date it was last updated, kind of like {{
refimprove}} and friends? I also made {{
portal flag}} into a redirect to {{
portal maintenance status}}. — AfroThundr (
u ·
t ·
c)
13:18, 9 June 2018 (UTC)
I think the new template and module are now ready to be used, and I've updated my TFD !votes accordingly, but because of the bureaucracy of the TFDs we shouldn't be making widespread replacements. - Evad37 [ talk 00:48, 11 June 2018 (UTC)
Templates are rarely orphaned—that is, removed from pages that transclude them—before the discussion is closed.- Evad37 [ talk 06:39, 11 June 2018 (UTC)
@ The Transhumanist and Pbsouthwood: As I was organizing portals for the Society and Social sciences section of Portal:Contents, I stumbled on a couple of portals that are throwing errors: Portal:Monarchy and Portal:Military of Pakistan. It seems that, after you replaced the /box-footer subpage with {{ Box-footer}}, a few portals still need to have the subpage. The error is caused by {{ Random portal component}} and {{ Random portal component with nominate}} because the error appears only in the boxes where those templates are used. I have figured out that the Lua module for those templates tries to find the /box-footer subpage to make the template, but that doesn't explain why portals like Portal:History do not throw errors with the same template and module when you have deleted the /box-footer subpage there as well. Greatedits1 ( I hope so | If not, let me know) 01:55, 7 June 2018 (UTC)
I noticed that pics in a portal's slideshow do not show up in Media Viewer. Do you have any idea why? Just curious.
Also, clicking on a picture in the slideshow goes to the file page, rather than the Media Viewer. It's a mystery to me. Could you clue me in? :) — The Transhumanist 09:21, 17 June 2018 (UTC)
Portals that the {{ Transclude lead excerpt}} template isn't catching the pictures in...
Resolved issues
|
---|
In Portal:Geneva, the template isn't picking up the pics from the infobox in the lead of Geneva. I'll keep posting 'em as I come across 'em. ;) — The Transhumanist 06:12, 12 July 2018 (UTC)
{{ Transclude lead excerpt}} isn't picking up the map image from the infobox in Geography of Canada. — The Transhumanist 06:43, 12 July 2018 (UTC)
This one isn't picking up the flag, seal, and location map from the infobox. — The Transhumanist 06:48, 12 July 2018 (UTC)
This one picks up the flag, but not the seal or locator map. — The Transhumanist 06:53, 12 July 2018 (UTC)
Same here. (Shows flag, but nothing else). — The Transhumanist 06:55, 12 July 2018 (UTC)
Their portraits don't show up. — The Transhumanist 06:57, 12 July 2018 (UTC)
Most of the pictures don't show up. — The Transhumanist 07:00, 12 July 2018 (UTC)
No pictures show up. — The Transhumanist 07:03, 12 July 2018 (UTC)
|
Flag, seal, and location map not show up. — The Transhumanist 06:50, 12 July 2018 (UTC)
The picture shows up at the end of the intro, rather than starting at the top. — The Transhumanist 07:20, 12 July 2018 (UTC)
Here's the excerpt:
"Is a ____ of the". Words have disappeared from the definition. — The Transhumanist 19:30, 16 July 2018 (UTC)
'''Bohol''' is a {{PH wikidata|settlement_text}}
. {{
PH wikidata}} gets wikidata for the current page. In the article, the current page is
Bohol which has wikidata. In the portal, the current page is
Portal:Bohol which quite correctly doesn't have wikidata. All the potential fixes that I can think of rely on MediaWiki features that don't exist.
Certes (
talk)
22:29, 16 July 2018 (UTC)
The image in the infobox doesn't show up. — The Transhumanist 06:55, 18 July 2018 (UTC)
@ Certes and Evad37: The coat of arms from the infobox doesn't show up, even though the other 2 images do. — The Transhumanist 07:08, 18 July 2018 (UTC)
This is a cool template.
As an experiment, I created or rebooted the following portals using the corresponding outlines as a base. (Reboots are marked with an asterisk).
I ran into a few issues...
When a list item is a section link, the template shows the lead of the page rather than the section. This is awkward when the section desired is on the root article, thereby duplicating the lead that is at the top of the portal.
For example, in the Environment section of the Outline of Dresden is the link [[Dresden#Climate|Climate of Dresden]]. When that is displayed in the "Selected environment article" of Portal:Dresden, it comes up as Dresden rather than the Climate section of Dresden. Which is awkward, because that is the same lead that is at the top of the portal. The same thing happens in the Sports section.
One thing I really like is that the template gets all the links from the subsections as well. This works in most cases, but there are some in which I'd only want the root part of the section.
For example, Outlines have an Economy and infrastructure section. One of the subsectons is transportation, which usually dominates the section. For portals where I would like both and Economy section and a Transportation section, the Economy section would cover the same articles as the Transportation section. If I had just an Economy section, most of the articles that showed up would be about transportation.
My assessment of the template is that it is awesome. When there are standard list sections to access, like with outlines, you can pop out a portal based on them from between 15 to 25 minutes per portal. I'm sure we can get this time down even lower...
The most time consuming part of building the portals above was compiling the image list in the pictures section. I essentially copied and converted the file links from the corresponding outlines, retaining their captions.
This has given me an idea for another template, {{ Transclude random thumbnail from page}}, which would extract file thumbs instead of list items. It could be used to fetch a picture for a "Selected picture" section without the need for a compiled list of file arguments. (It wouldn't be a slide show). It could also have a section parameter like the one {{ Transclude list item excerpt}} has. A transclusion template like this could save a portal builder/maintainer lots of time. — The Transhumanist 14:58, 13 July 2018 (UTC)
I'm thinking the template should be converted to use our {{ Box-header color}} variant, so that going forward, we don't make more instances of {{ box-header}} that we have to clean up later. Plus, it would make every new portal from now on have an auto-generated color scheme, instead of the same one. Thoughts? — AfroThundr ( u · t · c) 18:26, 18 July 2018 (UTC)
|months=120
, which I've noticed resulted in Lua timeouts on several occasions (the sandbox being one). I've reduced it to a year, unless we can figure out how to prevent that (or the portal maintainer can tweak it manually anyway). — AfroThundr (
u ·
t ·
c)
23:40, 19 July 2018 (UTC)
![]() | For discussion on WikiProject categories and portal categorization in general. |
Can category trees be induced to display in columns? · · · Peter (Southwood) (talk): 07:24, 8 June 2018 (UTC)
![]() | Exactly what it says on the tin. Post your specific technical issues here. |
@ The Transhumanist: According to this edit made to the Portal talk:Biography page, you enabled a recognized content listing on the main talk page. Was that intentional? At the moment JL-Bot has added 1.5 megabytes of text listing all of those pages. I've reverted the bot and the config. The Wikipedia:WikiProject Biography#Recognized content page just redirects to Category:FA-Class biography articles, so I guess they aren't using that bot. I was wondering why that page refused to load in AWB, and now I know it doesn't like pages over 1500k. — AfroThundr ( u · t · c) 17:12, 2 June 2018 (UTC)
I have an issue - the toys portal has two selected pictures missing , How can we fix that ? Kpgjhpjm ( talk) 03:20, 5 June 2018 (UTC)
I am having a bit of trouble adding a name to the Formula 1 drivers list . Can anybody help ? Kpgjhpjm ( talk) 11:57, 5 June 2018 (UTC)
[[Category:Ferrari Formula One drivers]]
near the bottom. The list in the "Selected Topics" box is
transcluded from
Portal:Ferrari/Topics. It can be changed by editing that subpage. Hope that helps,
Certes (
talk)
12:55, 5 June 2018 (UTC)@ Certes: Can you go to the portal and fix it . Actually you only have to add a dot between the bracket , but I do not have such a symbol . Kpgjhpjm ( talk) 15:02, 5 June 2018 (UTC)
Hi all, thanks for your great work. Have tried to implement some of your changes onto the anatomy portal, however having some difficulty working with some sections and would value some help if possible:
On our way to a one page portal! -- Tom (LT) ( talk) 01:09, 8 June 2018 (UTC)
(Copied from User talk:Pbsouthwood, as it may have general relevance)
Hi Pbsouthwood, could you please undelete Portal:Poland/box-footer? It's still needed. Thanks — Kpalion (talk) 15:42, 9 June 2018 (UTC)
Can anyone track down where the template is being called from? · · · Peter (Southwood) (talk): 04:57, 10 June 2018 (UTC)
frame:expandTemplate(title='subpage',args={i})
See Wikipedia:Village_pump_(technical)#Wikiproject_front_page_displaying_bizarrely
The deletion of Portal:Cornwall/box-footer affected the front page layout of Wikipedia:WikiProject Cornwall as it was transcluding some portal boxes. I think this was another of those calls from within a transcluded template which called a module which called a subpage. This may happen elsewhere too, please keep a lookout for similar usage when listing for deletion.
Does anyone know how to check if this will happen? Cheers, · · · Peter (Southwood) (talk): 15:26, 13 June 2018 (UTC)
{{Box-footer}}
should fix the problem. Some clean up is to be expected on mass deletions of this sort. Just report broken pages here, and we'll gladly and promptly fix them. —
The Transhumanist
21:29, 15 June 2018 (UTC)@ Certes: A sidebar navigation box is mysteriously showing up in the intro section. — The Transhumanist 21:21, 15 June 2018 (UTC)
Making any kind of change to the article to make it work properly in the portal is an indication of bad code design. {{3x|p}}ery ( talk) 18:28, 28 June 2018 (UTC)
Pleasanton is a village
{{convert|5|mi|km}}
from Famousville.
Pleasanton is a village.
{{Villagebox|name=Pleasanton|duckpond=yes}}
It is near Famousville.
Someone please close Wikipedia:Miscellany for deletion/Portal:Cenozoic. The nominator has withdrawn his nomination. Thank you. — The Transhumanist 11:04, 17 June 2018 (UTC)
Someone please close Wikipedia:Miscellany for deletion/Portal:Tamil civilization (2nd nomination). The nominator has withdrawn his nomination. Thank you. — The Transhumanist 02:03, 18 June 2018 (UTC)
In the Associated Wikimedia section, is it possible to link Wikisource to a category, rather than a search? Wikisource has a Category:Mesoamerica that is much more useful than the results returned by a search on the word "Mesoamerica". Thanks, Simon Burchell ( talk) 08:52, 18 June 2018 (UTC)
Hi Transhumanist: I've been watching with interest as the Birds Portal undergoes its metamorphosis. You "portal folks" are doing a nice job! One question though; why have you cut the lead article (from "Bird") down from the full four paragraphs to two? I see that your automatic template allows for all four paragraphs to be shown... MeegsC ( talk) 09:20, 21 June 2018 (UTC)
<div style="height:XXXpx">...</div>
tags, where XXX
is the size in px. I'm not sure how to prevent the flickering, but setting a static box size is probably not a great idea. The images pulled by the random slideshow aren't all the same size. Unless you set the static size to that of the largest picture, you could end up with truncated images, and even with that you'd have too much whitespace in the box for smaller images. Allowing the box to dynamically resize presents the best results once the page is fully loaded. Now if we could perhaps solve the loading issue with the gallery before the slideshow is ready, the flickering and unstable load behavior would go away. — AfroThundr (
u ·
t ·
c)
00:20, 22 June 2018 (UTC)
Somehow the latest issue of the newsletter is turning off the TOC on whatever page it is posted on. — The Transhumanist 11:34, 16 June 2018 (UTC)
@
Evad37 and
Certes: So {{
Random portal component}}, which depends on
Module:Random portal component, is currently setup to pull the /box-header
subpage for the header and {{
box-footer}} for the footer on portal pages. Although the documentation states that it also uses the /box-footer
subpage, I haven't found any evidence it actually does this, so the docs may be outdated. My question is, how difficult would it be to add a parameter to the module to pass a template name in place of the subpage? As an example: the 'Did You Know?' section of
Portal:Amphibians, until I made the subpage a redirect to {{
Box-header/13}}, pulled a portal-specific box header that no longer matched with the rest of the page. If the above parameter was added, something like {{
Random portal component|headertemplate=Box-Header/13|...}}
would make that section match with the rest of the portal, and obsolete another subpage. Would one of you template wizards be interested in adding this capability? — AfroThundr (
u ·
t ·
c)
07:33, 17 June 2018 (UTC)
If that is not feasible, a list of all orphan pages in portal space would suffice.
I look forward to your reply. — The Transhumanist 12:45, 17 June 2018 (UTC)
/
in the page title and the other doesn't). Then you'd compare each of the 140k entries in the subpage list to see if it has a prefix match against an entry in the top-level list. If it does, drop it, if it doesn't, add it to an orphan list. If I had some time, I could throw that together later. Or maybe there is a fancy wiki tool available to do this, and the python method is unnecessary. On-wiki, I'm not sure how to do that; maybe with
WP:PetScan or something similar? I imagine any of those tools would choke on a 150k entry page query. — AfroThundr (
u ·
t ·
c)
12:27, 18 June 2018 (UTC)Is there any way to make a template that can perform a function analogous to {{
Transclude list item excerpt}}
and {{
Transclude linked excerpt}}
, but selecting an article randomly from within a category? That way a category such as
Category:FA-Class_MCB_articles could be cycled through.
T.Shafee(Evo&Evo)
talk
08:54, 28 June 2018 (UTC)
{{
Transclude list item excerpt}}
. The bot tends to run once per weekend.
Certes (
talk)
10:08, 28 June 2018 (UTC)
{{ Random quotation}} does not work correctly. It randomises both quotation and author, so gets them mixed up, and uses double chevron style quote marks expressly deprecated by MoS. I could not work out how to fix it yet. It also applies a style that should be optional not default. I don't know if this is a thing we should try to fix or just create a better alternative. It is getting a bit late here, so do not intend to do anything more about it tonight. · · · Peter (Southwood) (talk): 19:20, 30 June 2018 (UTC)
|same=yes
to force the random number to be the same.
Wpgbrown
talk |
contribs
21:29, 30 June 2018 (UTC)![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 | Archive 5 |
![]() | Please dream up new features, and post threads for them below... |
For accessibility, for example. — The Transhumanist 03:11, 28 May 2018 (UTC)
When purging, you get this page, rather than an actual purge: https://en.wikipedia.org/?title=Portal:Sacramento,_California&action=purge
Is there any way we can make purge links purge directly, without the confirmation page? — The Transhumanist 00:41, 6 June 2018 (UTC)
@ Cesdeva, Evad37, Certes, AfroThundr3007730, Wpgbrown, Waggers, Nihonjoe, Finnusertop, and Greatedits1:
The {{ portal}} template seems dated and unappealing.
Once the revamping of portals is complete, it might be nice to upgrade the links leading to them, as a way to announce the new and improved portal system. True, this is a long ways off, but now is the time to start thinking about the presentation of the system for when the upgrade is complete. Toward this end, here are some questions...
What are the applications of {{ PortalButton}}? What can they be used for?
What is the feasibility of implementing {{ PortalButton}} for all portals?
Could Module:Portal and Module:Portal/images be expanded/adapted to handle Portalbuttons?
Cesdeva, I'm especially interested in what you envisioned, and what other potential applications you foresee for these.
The idea is to drive traffic to the portals. Thoughts? — The Transhumanist 21:40, 16 June 2018 (UTC)
photographs myself already and have been working on some SVG's. The standard image alt= already works fine, and no-one said anything about not conforming to policy on contrast. There's always a lot of hot air being blown when new design features appear and it's all fairly weightless naysaying. Perhaps that is why the portal space is in, and will remain in, such a state. I'll leave you guys to keep polishing your turds. Cesdeva (talk) 15:13, 17 June 2018 (UTC)
Evad37 wrote above: "I think minor improvements to the existing templates, or some new way of using the existing icons, would be a better way to go."
@ Certes, Evad37, Nihonjoe, and Wpgbrown:
During the conversion of portal introduction sections from using static excerpts and subpages, I noticed that picture support of the lead section in articles seems to be migrating to each article's infobox, rendering many leads otherwise pictureless.
The main ramification for portals is that {{
Transclude lead excerpt}} and {{
Transclude random excerpt}} present bare prose without picture support when used to present excerpts from articles supported by infobox pictures, rendering the files=
parameter useless for those articles.
It would be really cool if these templates and their corresponding lua module could be enhanced so that the files=
parameter recognizes pictures at the top of the article's infobox. Thoughts? —
The Transhumanist
03:11, 17 June 2018 (UTC)
The gharial (Gavialis gangeticus), also known as gavial or fish-eating crocodile, is a crocodilian in the family Gavialidae and among the longest of all living crocodilians. Mature females are 2.6 to 4.5 m (8 ft 6 in to 14 ft 9 in) long, and males 3 to 6 m (9 ft 10 in to 19 ft 8 in). Adult males have a distinct boss at the end of the snout, which resembles an earthenware pot known as a ghara, hence the name "gharial". The gharial is well adapted to catching fish because of its long, narrow snout and 110 sharp, interlocking teeth.
The gharial probably evolved in the northern Indian subcontinent. Fossil gharial remains were excavated in Pliocene deposits in the Sivalik Hills and the Narmada River valley. It currently inhabits rivers in the plains of the northern part of the Indian subcontinent. It is the most thoroughly aquatic crocodilian, and leaves the water only for basking and building nests on moist sandbanks. Adults mate at the end of the cold season. Females congregate in spring to dig nests, in which they lay 20–95 eggs. They guard the nests and the young, which hatch before the onset of the monsoon. The hatchlings stay and forage in shallow water during their first year, but move to sites with deeper water as they grow. ( Full article...)
Snakes are elongated, limbless reptiles of the suborder Serpentes ( /sɜːrˈpɛntiːz/). Like all other squamates, snakes are ectothermic, amniote vertebrates covered in overlapping scales. Many species of snakes have skulls with several more joints than their lizard ancestors, enabling them to swallow prey much larger than their heads ( cranial kinesis). To accommodate their narrow bodies, snakes' paired organs (such as kidneys) appear one in front of the other instead of side by side, and most have only one functional lung. Some species retain a pelvic girdle with a pair of vestigial claws on either side of the cloaca. Lizards have independently evolved elongate bodies without limbs or with greatly reduced limbs at least twenty-five times via convergent evolution, leading to many lineages of legless lizards. These resemble snakes, but several common groups of legless lizards have eyelids and external ears, which snakes lack, although this rule is not universal (see Amphisbaenia, Dibamidae, and Pygopodidae).
Living snakes are found on every continent except Antarctica, and on most smaller land masses; exceptions include some large islands, such as Ireland, Iceland, Greenland, and the islands of New Zealand, as well as many small islands of the Atlantic and central Pacific oceans. Additionally, sea snakes are widespread throughout the Indian and Pacific oceans. Around thirty families are currently recognized, comprising about 520 genera and about 3,900 species. They range in size from the tiny, 10.4 cm-long (4.1 in) Barbados threadsnake to the reticulated python of 6.95 meters (22.8 ft) in length. The fossil species Titanoboa cerrejonensis was 12.8 meters (42 ft) long. Snakes are thought to have evolved from either burrowing or aquatic lizards, perhaps during the Jurassic period, with the earliest known fossils dating to between 143 and 167 Ma ago. The diversity of modern snakes appeared during the Paleocene epoch ( c. 66 to 56 Ma ago, after the Cretaceous–Paleogene extinction event). The oldest preserved descriptions of snakes can be found in the Brooklyn Papyrus. ( Full article...)
|weird_image_parameter_name = imagename.png
(I can fix those). With
Snake, the image we're after is inside <imagemap>...</imagemap>
tags within an infobox template parameter. I'm leaving that one to the experts!
Waggers
TALK
09:35, 18 June 2018 (UTC)
I've heard that Wikipedia forks augment WP's content in various ways. Are you aware of any? Perhaps we could implement something similar or better. — The Transhumanist 08:41, 17 June 2018 (UTC)
Is this possible? — The Transhumanist 06:14, 20 June 2018 (UTC)
See User:Evad37/sandbox/portal for a possible implementation. It doesn't look quite right in some skins, but I think that should be fixable once TemplateStyles is available. - Evad37 [ talk 03:17, 21 June 2018 (UTC)
Can a section be done in such a way that it is one thing for mobile viewers, and something else for non-mobile viewers?
For example, can Picture slideshow sections be presented as Selected picture sections for mobile viewers? Otherwise, portals with picture slideshows are essentially broken to a majority of our viewers. Thoughts? — The Transhumanist 01:44,? 30 June 2018 (UTC)
nomobile
, but I don't think there's any equivalent for hiding things on desktop only. -
Evad37 [
talk
15:35, 9 July 2018 (UTC)
This would be similar to {{ Transclude list item excerpt}}, but instead of gathering list items, it would gather thumbnail pictures (thumbnails, because those have captions). Then it would pick one at random and display it, adjusted to fit the width of the section it is in (like the picture size is adjusted in {{ Random slideshow}}. This one, however is not intended to be a slideshow, but is for powering "Selected picture" sections. — The Transhumanist 09:19, 15 July 2018 (UTC)
![]() | General portal design discussions go here. |
Short on time, so briefly and bluntly: Is it possible to implement the ability to edit each "section" of the portal within the current one page portal model. If not, it may not be a good direction to continue in because I would actually argue that having a subpages for each section makes it easier to edit and manage the portal. Personally, I've never seen a problem with having 10 or so subpages for each portal. If being able to easily discern how many portals there are is the perceived issue, a category (e.g. Category:Main portal page) could be created along with a bot to place it on every portal page that is not a subpage (i.e. titles without a slash). — Godsy ( TALK CONT) 05:36, 7 June 2018 (UTC)
We should track these. By "one-page portal", I mean one that has no subpages of is own, not even header or footer subpages. — The Transhumanist 19:28, 7 June 2018 (UTC)
{{
portal maintenance status|subpages=single}}
at the top of the portal. -
Evad37 [
talk
00:42, 20 June 2018 (UTC){{
portal maintenance status|date=June 2018|subpages=single}}
so they're all tracked now. — AfroThundr (
u ·
t ·
c)
12:40, 15 June 2018 (UTC)
Quite a few portals use a banner image in the introduction or above it. By this I mean a wide panorama style image. Sometimes it includes an image of text, other times it is just for decorative purposes. There are technical problems with most of them.
If it does already, I have consistently failed to find either an example or an explanation of how to do it.
Is this a thing anyone here knows how to fix? · · · Peter (Southwood) (talk): 07:36, 6 July 2018 (UTC)
img
element, where you could then set width:100%
or whatever you like (see
this answer). That would require TemplateStyles though, as it can't currently be done inline. — AfroThundr (
u ·
t ·
c)
12:01, 6 July 2018 (UTC){{
Transclude linked excerpt|data page}}
on the page where the random article is to appear. If you can link a concrete example of a portal that should do this, then I'm willing to have a go at setting it up as a model.
Certes (
talk)
10:41, 3 June 2018 (UTC)
Is there any way of using a bot to take the list of DYKs from a project (ie JL-Bot recognized content listing output) and turn it into a wiki-coded text output with the DYKs (recent ones are now stored on the article's talk page). This would be a great help for small/sluggish projects where the new automated template doesn't produce much, if any, recent output, but the project has lots of old DYKs. I've previously done them myself by going to the talk page and cutting & pasting, but it's very time-consuming. Espresso Addict ( talk) 13:24, 8 July 2018 (UTC)
![]() | For discussion on template development, issues, etc. |
I have created some new flags, which in my view should be added to all portals as a kind of classification system.
If the portal has a peculiar layout or is an example of a design incompatible with the latest updates, tag it with {{ Non-standard portal flag}}, to avoid introducing errors, project bots and AWB users should skip pages with this flag.
Any portal with one or more active maintainers should be tagged with {{ Maintained portal flag}}, those maintainers should be responsible for deploying any updates, therefore project bots and AWB users should skip pages with this flag.
Portals which are not maintained, or where the maintainers want all the latest updates automatically, can be tagged with {{ Portal flag}}, project bots and AWB users should make sure to keep these portals up to date and free from errors.
All these flags are optional, but will make things much easier for everyone working on the project. I can add any additional features to these flags if needed. JLJ001 ( talk) 10:15, 29 May 2018 (UTC)
{{Portal flag|maintained=y|standard=y|wpport-autoedit=y|subpages=y|subpage-keep=y}}
wpport-autoedit
parameter above was for flagging if auto editing was allowed. —
AfroThundr (
t•
c)
13:42, 29 May 2018 (UTC)
subpages=y|subpage-keep=y
then. Parameters are cheap. Updated the example above. —
AfroThundr (
t•
c)
15:17, 29 May 2018 (UTC)@ JLJ001: what is the flag icon at the top of the page that {{ Maintained portal flag}} generates supposed to link to? At present it just links to a non-existent page "The page to link to. This is where you will be taken when clicking the icon" , which obviously takes you to the wiki page inviting you to start the non-existent article. Perhaps you could fix this? I'm reluctant to deploy this template until it's working 100% Cactus.man ✍ 17:19, 29 May 2018 (UTC)
Portal talk:{{PAGENAME}}
. (the talk page of whatever portal page it's on).
JLJ001 (
talk)
17:25, 29 May 2018 (UTC)Portal talk:{{BASEPAGENAME}}
so it will automatically link to the main talk page if used on first level subpages. However, this only goes one level down for second or third level supages. For Example:
Portal:Opera/Selected audio/20 will link to
Portal talk:Opera/Selected audio. There is nothing I can do about this, if talk page consolidation beyond that is needed, redirects could be used.
JLJ001 (
talk)
17:38, 29 May 2018 (UTC)unique=n && maintained=n
(free game for auto-editing)unique=y && maintained=n
(edit with care)unique=y && maintained=y
(don't touch)unique=n && maintained=y
(probably don't touch)I don't know why, but there is some bug were the portal template will affect the reflist template and stop the reflist from splitting into columns. One example is Newcastle United F.C., can someone good with templates have a look thanks. Govvy ( talk) 17:15, 31 May 2018 (UTC)
Can you subst: a template which in turn has subst: in it? How? — The Transhumanist 08:45, 5 June 2018 (UTC)
{{outer template|{{shim|{{inner template1|param=foo}}{{inner template2|param=bar}}...|shimparam=baz}}|outerparam=quux}}
shimparam
could be used to pass certain values from the inner templates as well (regex maybe?), if that's possible.<includeonly>...</includeonly>
tags. The only downside is that standard transclusion no longer works correctly (but that limitation can probably be overcome if necessary). See
[3],
User:Evad37/X1,
User:Evad37/X2 for examples. -
Evad37 [
talk
11:28, 5 June 2018 (UTC)Two of our maintenance flag templates, {{ maintained portal flag}} and {{ non-standard portal flag}}, were posted to WP:TFD. Concerns were raised about the validity of maintenance flag templates on Portal pages, specifically the visual flag indicator. These concerns were raised before, and I think we should iron these out before doing much more with these flags.
Previously discussed in #New Markers (which started in #We should use flags), was the need for a visual indicator to users during AWB maintenance runs that signified to the editor that a page met certain criteria that required special care when editing, such as being actively maintained, or using significantly unique markup and design. Currently the use of these flags is a bit inconsistent: They were intended to be placed on the root portal page, not necessarily every subpage in the tree (see Portal:Opera).
It should be noted that these flags add the portals in question to tracking categories. I'll also note that these types of statuses can also be recorded with the {{
portal flag talk}} template (still a work in progress), or added as additional parameters to {{
WikiProject Portals}}, the same way the |historical=
flag is done. Ideally we'd only need one template to record all of these statuses, in whichever namespace they should reside.
We currently track three different statuses for portals, with another planned:
These are the questions I want to start with:
Please post your thoughts and comments in the discussion section below.
Barring technical restrictions, the ideal end state would look like this:
This is now the current state of affairs:
@ The Transhumanist, Cesdeva, Evad37, Wpgbrown, Pbsouthwood, Certes, and Waggers: Pinging the usual players, input from everyone is welcome and appreciated. — AfroThundr ( u · t · c) 13:43, 6 June 2018 (UTC)
I've added an idea of where I think we should end up. I believe we should consolidate the flags into a single template, or one per namespace if a template is required for both. I think this would provide the best balance between allowing for portal maintenance flags while keeping our footprint in portal space small. That said, there may be things I haven't considered yet, hence the survey. I may need to revise this as the questions get answered. — AfroThundr ( u · t · c) 14:15, 6 June 2018 (UTC)
|maintained=yes
or any other value to turn on the "is maintained" note). This should make it easier for the module (which looks at the raw unexpanded wikitext of the portal page) to determine which notes apply. -
Evad37 [
talk
04:29, 8 June 2018 (UTC)
@ Evad37: First off, thanks for building that module. I have a couple questions and comments.
Just a few thoughts I had, I'll probably have more questions later. Thanks again. — AfroThundr ( u · t · c) 04:09, 8 June 2018 (UTC)
historical
is. It shouldn't be a problem since the portals will have to be manually triaged anyway. The editor can just set the flag manually, once they're done. Speaking of which, how much work would it be to make the template also detect {{
historical}} on the corresponding main page, and automatically set historical=y
for those too? And another thing: the other flags should have a parameter that can be set manually if {{
portal flag}} can't be used for some reason. Local values would override detected ones, or absent ones (although, maybe the template should display an error if it has conflicting values). — AfroThundr (
u ·
t ·
c)
14:49, 8 June 2018 (UTC)
|embed=
parameter to the template might make more sense, so as not to use up Lua time on portal pages – some of the other portal automation modules can take up a fair chunk of the allotted Lua processing time. -
Evad37 [
talk
07:14, 11 June 2018 (UTC)Issue raised in the TFD:
How is
tagging something as maintained is misleading since when it becomes unmaintained, the nonexistent maintainer doesn't remove itaddressable by editing? — JJMC89 ( T· C) 23:04, 8 June 2018 (UTC)
- The template just needs a
|date=
parameter, automatically filled in by AnomieBOT, and a process for removal, such as a portal_talk page message after some reasonable amount of time (e.g. six months), requesting that the maintainer update the date if they're still active, and automatic removal of the maintained status a short time later (e.g. one month) if not updated. - Evad37 [ talk 00:40, 9 June 2018 (UTC)- Or even skip the talk page message, as long as removal is done without a bot flag, and with a very clear edit summary. - Evad37 [ talk 00:44, 9 June 2018 (UTC)
No point making a bot request till other issues (TFD, merging) get resolved. But does six months sound about right for the timeframe? Can we do without a talk page message? - Evad37 [ talk 00:52, 9 June 2018 (UTC)
|date=
. In terms of the "fresh" status, the main reason I suggested a longer timeframe was to avoid annoying portal maintainers too often – a couple, or a few, edits a year seems reasonable, to show a sustained interest. And I don't think the "stale" period needs to be as long as 90 days – around four weeks should be enough, since its really just a grace period between the flags being valid and invalid. I think removal should require an actual edit (by bot, awb, or manually), rather than just template logic, so that it actually shows up on watchlists and page histories. We don't really extra "stale" or "outdated" categories, since the portals will already be in dated maintenance subcategories. -
Evad37 [
talk
07:01, 11 June 2018 (UTC)
I've started working on {{ Portal maintenance status}}, as a proposed merged template. Instead of a top-icon flag, it uses a hidden-by-default message box, which those working on portal maintenance can display with custom css. @ AfroThundr3007730: Did you want to add something for subpages to the template? - Evad37 [ talk 02:46, 9 June 2018 (UTC)
subpages=( (0|untriaged|<empty>) | (1|triaged) | (2|single[page]) )
This flag would be set when a portal has been pruned of unnecessary subpages ("unnecessary" being subjective) and any portals tagged with this template without that flag set would be added to
Category:Portals with untriaged subpages, and it would also populate
Category:Single-page portals, as appropriate. The intent, of course, is not to wage war on subpages so much as reduce their number to a manageable level, as has been discussed elsewhere on this page. Single page portals should have this set automatically, if possible. singlepage
flag, which could also be useful, and would populate another tracking category, that overrides the subpages flag. Just thinking out loud here.subpages
to the template. Now we just need to update the module to provide parity in the WikiProject banner. Also, can we make the template expose the date it was last updated, kind of like {{
refimprove}} and friends? I also made {{
portal flag}} into a redirect to {{
portal maintenance status}}. — AfroThundr (
u ·
t ·
c)
13:18, 9 June 2018 (UTC)
I think the new template and module are now ready to be used, and I've updated my TFD !votes accordingly, but because of the bureaucracy of the TFDs we shouldn't be making widespread replacements. - Evad37 [ talk 00:48, 11 June 2018 (UTC)
Templates are rarely orphaned—that is, removed from pages that transclude them—before the discussion is closed.- Evad37 [ talk 06:39, 11 June 2018 (UTC)
@ The Transhumanist and Pbsouthwood: As I was organizing portals for the Society and Social sciences section of Portal:Contents, I stumbled on a couple of portals that are throwing errors: Portal:Monarchy and Portal:Military of Pakistan. It seems that, after you replaced the /box-footer subpage with {{ Box-footer}}, a few portals still need to have the subpage. The error is caused by {{ Random portal component}} and {{ Random portal component with nominate}} because the error appears only in the boxes where those templates are used. I have figured out that the Lua module for those templates tries to find the /box-footer subpage to make the template, but that doesn't explain why portals like Portal:History do not throw errors with the same template and module when you have deleted the /box-footer subpage there as well. Greatedits1 ( I hope so | If not, let me know) 01:55, 7 June 2018 (UTC)
I noticed that pics in a portal's slideshow do not show up in Media Viewer. Do you have any idea why? Just curious.
Also, clicking on a picture in the slideshow goes to the file page, rather than the Media Viewer. It's a mystery to me. Could you clue me in? :) — The Transhumanist 09:21, 17 June 2018 (UTC)
Portals that the {{ Transclude lead excerpt}} template isn't catching the pictures in...
Resolved issues
|
---|
In Portal:Geneva, the template isn't picking up the pics from the infobox in the lead of Geneva. I'll keep posting 'em as I come across 'em. ;) — The Transhumanist 06:12, 12 July 2018 (UTC)
{{ Transclude lead excerpt}} isn't picking up the map image from the infobox in Geography of Canada. — The Transhumanist 06:43, 12 July 2018 (UTC)
This one isn't picking up the flag, seal, and location map from the infobox. — The Transhumanist 06:48, 12 July 2018 (UTC)
This one picks up the flag, but not the seal or locator map. — The Transhumanist 06:53, 12 July 2018 (UTC)
Same here. (Shows flag, but nothing else). — The Transhumanist 06:55, 12 July 2018 (UTC)
Their portraits don't show up. — The Transhumanist 06:57, 12 July 2018 (UTC)
Most of the pictures don't show up. — The Transhumanist 07:00, 12 July 2018 (UTC)
No pictures show up. — The Transhumanist 07:03, 12 July 2018 (UTC)
|
Flag, seal, and location map not show up. — The Transhumanist 06:50, 12 July 2018 (UTC)
The picture shows up at the end of the intro, rather than starting at the top. — The Transhumanist 07:20, 12 July 2018 (UTC)
Here's the excerpt:
"Is a ____ of the". Words have disappeared from the definition. — The Transhumanist 19:30, 16 July 2018 (UTC)
'''Bohol''' is a {{PH wikidata|settlement_text}}
. {{
PH wikidata}} gets wikidata for the current page. In the article, the current page is
Bohol which has wikidata. In the portal, the current page is
Portal:Bohol which quite correctly doesn't have wikidata. All the potential fixes that I can think of rely on MediaWiki features that don't exist.
Certes (
talk)
22:29, 16 July 2018 (UTC)
The image in the infobox doesn't show up. — The Transhumanist 06:55, 18 July 2018 (UTC)
@ Certes and Evad37: The coat of arms from the infobox doesn't show up, even though the other 2 images do. — The Transhumanist 07:08, 18 July 2018 (UTC)
This is a cool template.
As an experiment, I created or rebooted the following portals using the corresponding outlines as a base. (Reboots are marked with an asterisk).
I ran into a few issues...
When a list item is a section link, the template shows the lead of the page rather than the section. This is awkward when the section desired is on the root article, thereby duplicating the lead that is at the top of the portal.
For example, in the Environment section of the Outline of Dresden is the link [[Dresden#Climate|Climate of Dresden]]. When that is displayed in the "Selected environment article" of Portal:Dresden, it comes up as Dresden rather than the Climate section of Dresden. Which is awkward, because that is the same lead that is at the top of the portal. The same thing happens in the Sports section.
One thing I really like is that the template gets all the links from the subsections as well. This works in most cases, but there are some in which I'd only want the root part of the section.
For example, Outlines have an Economy and infrastructure section. One of the subsectons is transportation, which usually dominates the section. For portals where I would like both and Economy section and a Transportation section, the Economy section would cover the same articles as the Transportation section. If I had just an Economy section, most of the articles that showed up would be about transportation.
My assessment of the template is that it is awesome. When there are standard list sections to access, like with outlines, you can pop out a portal based on them from between 15 to 25 minutes per portal. I'm sure we can get this time down even lower...
The most time consuming part of building the portals above was compiling the image list in the pictures section. I essentially copied and converted the file links from the corresponding outlines, retaining their captions.
This has given me an idea for another template, {{ Transclude random thumbnail from page}}, which would extract file thumbs instead of list items. It could be used to fetch a picture for a "Selected picture" section without the need for a compiled list of file arguments. (It wouldn't be a slide show). It could also have a section parameter like the one {{ Transclude list item excerpt}} has. A transclusion template like this could save a portal builder/maintainer lots of time. — The Transhumanist 14:58, 13 July 2018 (UTC)
I'm thinking the template should be converted to use our {{ Box-header color}} variant, so that going forward, we don't make more instances of {{ box-header}} that we have to clean up later. Plus, it would make every new portal from now on have an auto-generated color scheme, instead of the same one. Thoughts? — AfroThundr ( u · t · c) 18:26, 18 July 2018 (UTC)
|months=120
, which I've noticed resulted in Lua timeouts on several occasions (the sandbox being one). I've reduced it to a year, unless we can figure out how to prevent that (or the portal maintainer can tweak it manually anyway). — AfroThundr (
u ·
t ·
c)
23:40, 19 July 2018 (UTC)
![]() | For discussion on WikiProject categories and portal categorization in general. |
Can category trees be induced to display in columns? · · · Peter (Southwood) (talk): 07:24, 8 June 2018 (UTC)
![]() | Exactly what it says on the tin. Post your specific technical issues here. |
@ The Transhumanist: According to this edit made to the Portal talk:Biography page, you enabled a recognized content listing on the main talk page. Was that intentional? At the moment JL-Bot has added 1.5 megabytes of text listing all of those pages. I've reverted the bot and the config. The Wikipedia:WikiProject Biography#Recognized content page just redirects to Category:FA-Class biography articles, so I guess they aren't using that bot. I was wondering why that page refused to load in AWB, and now I know it doesn't like pages over 1500k. — AfroThundr ( u · t · c) 17:12, 2 June 2018 (UTC)
I have an issue - the toys portal has two selected pictures missing , How can we fix that ? Kpgjhpjm ( talk) 03:20, 5 June 2018 (UTC)
I am having a bit of trouble adding a name to the Formula 1 drivers list . Can anybody help ? Kpgjhpjm ( talk) 11:57, 5 June 2018 (UTC)
[[Category:Ferrari Formula One drivers]]
near the bottom. The list in the "Selected Topics" box is
transcluded from
Portal:Ferrari/Topics. It can be changed by editing that subpage. Hope that helps,
Certes (
talk)
12:55, 5 June 2018 (UTC)@ Certes: Can you go to the portal and fix it . Actually you only have to add a dot between the bracket , but I do not have such a symbol . Kpgjhpjm ( talk) 15:02, 5 June 2018 (UTC)
Hi all, thanks for your great work. Have tried to implement some of your changes onto the anatomy portal, however having some difficulty working with some sections and would value some help if possible:
On our way to a one page portal! -- Tom (LT) ( talk) 01:09, 8 June 2018 (UTC)
(Copied from User talk:Pbsouthwood, as it may have general relevance)
Hi Pbsouthwood, could you please undelete Portal:Poland/box-footer? It's still needed. Thanks — Kpalion (talk) 15:42, 9 June 2018 (UTC)
Can anyone track down where the template is being called from? · · · Peter (Southwood) (talk): 04:57, 10 June 2018 (UTC)
frame:expandTemplate(title='subpage',args={i})
See Wikipedia:Village_pump_(technical)#Wikiproject_front_page_displaying_bizarrely
The deletion of Portal:Cornwall/box-footer affected the front page layout of Wikipedia:WikiProject Cornwall as it was transcluding some portal boxes. I think this was another of those calls from within a transcluded template which called a module which called a subpage. This may happen elsewhere too, please keep a lookout for similar usage when listing for deletion.
Does anyone know how to check if this will happen? Cheers, · · · Peter (Southwood) (talk): 15:26, 13 June 2018 (UTC)
{{Box-footer}}
should fix the problem. Some clean up is to be expected on mass deletions of this sort. Just report broken pages here, and we'll gladly and promptly fix them. —
The Transhumanist
21:29, 15 June 2018 (UTC)@ Certes: A sidebar navigation box is mysteriously showing up in the intro section. — The Transhumanist 21:21, 15 June 2018 (UTC)
Making any kind of change to the article to make it work properly in the portal is an indication of bad code design. {{3x|p}}ery ( talk) 18:28, 28 June 2018 (UTC)
Pleasanton is a village
{{convert|5|mi|km}}
from Famousville.
Pleasanton is a village.
{{Villagebox|name=Pleasanton|duckpond=yes}}
It is near Famousville.
Someone please close Wikipedia:Miscellany for deletion/Portal:Cenozoic. The nominator has withdrawn his nomination. Thank you. — The Transhumanist 11:04, 17 June 2018 (UTC)
Someone please close Wikipedia:Miscellany for deletion/Portal:Tamil civilization (2nd nomination). The nominator has withdrawn his nomination. Thank you. — The Transhumanist 02:03, 18 June 2018 (UTC)
In the Associated Wikimedia section, is it possible to link Wikisource to a category, rather than a search? Wikisource has a Category:Mesoamerica that is much more useful than the results returned by a search on the word "Mesoamerica". Thanks, Simon Burchell ( talk) 08:52, 18 June 2018 (UTC)
Hi Transhumanist: I've been watching with interest as the Birds Portal undergoes its metamorphosis. You "portal folks" are doing a nice job! One question though; why have you cut the lead article (from "Bird") down from the full four paragraphs to two? I see that your automatic template allows for all four paragraphs to be shown... MeegsC ( talk) 09:20, 21 June 2018 (UTC)
<div style="height:XXXpx">...</div>
tags, where XXX
is the size in px. I'm not sure how to prevent the flickering, but setting a static box size is probably not a great idea. The images pulled by the random slideshow aren't all the same size. Unless you set the static size to that of the largest picture, you could end up with truncated images, and even with that you'd have too much whitespace in the box for smaller images. Allowing the box to dynamically resize presents the best results once the page is fully loaded. Now if we could perhaps solve the loading issue with the gallery before the slideshow is ready, the flickering and unstable load behavior would go away. — AfroThundr (
u ·
t ·
c)
00:20, 22 June 2018 (UTC)
Somehow the latest issue of the newsletter is turning off the TOC on whatever page it is posted on. — The Transhumanist 11:34, 16 June 2018 (UTC)
@
Evad37 and
Certes: So {{
Random portal component}}, which depends on
Module:Random portal component, is currently setup to pull the /box-header
subpage for the header and {{
box-footer}} for the footer on portal pages. Although the documentation states that it also uses the /box-footer
subpage, I haven't found any evidence it actually does this, so the docs may be outdated. My question is, how difficult would it be to add a parameter to the module to pass a template name in place of the subpage? As an example: the 'Did You Know?' section of
Portal:Amphibians, until I made the subpage a redirect to {{
Box-header/13}}, pulled a portal-specific box header that no longer matched with the rest of the page. If the above parameter was added, something like {{
Random portal component|headertemplate=Box-Header/13|...}}
would make that section match with the rest of the portal, and obsolete another subpage. Would one of you template wizards be interested in adding this capability? — AfroThundr (
u ·
t ·
c)
07:33, 17 June 2018 (UTC)
If that is not feasible, a list of all orphan pages in portal space would suffice.
I look forward to your reply. — The Transhumanist 12:45, 17 June 2018 (UTC)
/
in the page title and the other doesn't). Then you'd compare each of the 140k entries in the subpage list to see if it has a prefix match against an entry in the top-level list. If it does, drop it, if it doesn't, add it to an orphan list. If I had some time, I could throw that together later. Or maybe there is a fancy wiki tool available to do this, and the python method is unnecessary. On-wiki, I'm not sure how to do that; maybe with
WP:PetScan or something similar? I imagine any of those tools would choke on a 150k entry page query. — AfroThundr (
u ·
t ·
c)
12:27, 18 June 2018 (UTC)Is there any way to make a template that can perform a function analogous to {{
Transclude list item excerpt}}
and {{
Transclude linked excerpt}}
, but selecting an article randomly from within a category? That way a category such as
Category:FA-Class_MCB_articles could be cycled through.
T.Shafee(Evo&Evo)
talk
08:54, 28 June 2018 (UTC)
{{
Transclude list item excerpt}}
. The bot tends to run once per weekend.
Certes (
talk)
10:08, 28 June 2018 (UTC)
{{ Random quotation}} does not work correctly. It randomises both quotation and author, so gets them mixed up, and uses double chevron style quote marks expressly deprecated by MoS. I could not work out how to fix it yet. It also applies a style that should be optional not default. I don't know if this is a thing we should try to fix or just create a better alternative. It is getting a bit late here, so do not intend to do anything more about it tonight. · · · Peter (Southwood) (talk): 19:20, 30 June 2018 (UTC)
|same=yes
to force the random number to be the same.
Wpgbrown
talk |
contribs
21:29, 30 June 2018 (UTC)