Help talk:Subpages/Archive 2

Previous page history was archived for backup purposes at Help talk:Subpages/LQT Archive 1 on 2015-07-10.

Currently when I browse a great-grand child page, the title gets excessively long, e.g. "A large archive/Big data/Data of the abandoned ones/Data block #1". I want to hide the parent pages, leaving only the name "Data block #1" because the BreadCrumbs extension already shows where the page is. Is this already implemented somewhere or do I have to hack?

I am looking for the very same thing, have you by chance found a solution?

I had to modify MediaWiki's source code to create this behavior.

Could you please outline the steps you took? Thank you in advance

On page load, change the title text to include only what is behind the last slash. The hard part is finding where to insert the code.

this question is 5 years old but here is the answer.

{{DISPLAYTITLE:{{SUBPAGENAME}}}}

Help:Magic words - MediaWiki

We read

Breadcrumb links will appear automatically at the top of the subpage, linking to each parent page that exists.

That's great. It's easy to go to the parent.

But if you are on the parent, then it's super hard to figure out even if there are any children!

Wait. I found the answer... OK, I'll edit the page.

Wait. I might mess up the page. Somebody else please edit it to say:

We see with breadcrumbs it is easy to find the parent.

But finding the children is also not too hard.

1. In the side panel, click "Page information".
2. Then you will see "Number of subpages of this page". Click it.

Is it possible to affect how the breadcrumb line (links to parent pages) look like?

I.e., is it possible to define text that would be displayed in breadcrumbs instead of default page title?

I noticed that using {{DISPLAYTITLE}} does not affect the text used in breadcrumbs.

Thanks.

I wanna know that as well

I have a template Template:Example that contains

{{/subpage}}

and a corresponding Template:Example/subpage. When Template:Example gets transcluded into a document, however, it appears to try to transclude Document in question/subpage (which doesn't exist) rather than Template:Example/subpage. Where is this behavior documented? I can't find anything in any of the links on this page, or on any google results.

I ran into the same problem, it's as if Topic:Uuen4em4k7ji6q01 is used internally when expanding the subpage path.

Is there a way to show all pages in the main namespace such that pages with subpages render with an expansion triangle so i exoands show their subpages when clicked?

Using a 1.35.0 Bitnami image for development, and adding to LocalSettings.php

$wgNamespacesWithSubpages[NS_MAIN] = true;

does not seem to work - no breadcrumbs, just interpreting pages with a slash as a page. I'm not sure how to diagnose the issue. Done this before in other installs with no issues.

Ideas welcome.

Hi all, The text speaks of

"big solidus" (U+29F8), which results in Foo⧸ba ....

but as the character is not visible in the current display font, I only see the default square image with 29F8 inside. It should be good here to include an image of what this character represents rather than using its unicode value. Thanks.

Christian Wia (talk) 19:39, 29 June 2019 (UTC)

There's presently no coverage of rename semantics. If the root page is renamed, do the subpages comes along for the ride, or has the user created a big work project for himself or herself? If the second case, does the software warn the user that something bad is about to happen? ~~~~

Yes that was missing. I've added a brief mention. I think there's probably more could be said about that.

Hi,

I have a template with a very long name and a few subpages, something like Template:Template_with_very_very_very_long_title, Template:Template_with_very_very_very_long_title/sub1 and Template:Template_with_very_very_very_long_title/sub2.

Because of the long title, it gets a little cumbersome to transclude the template and its subpages (it is hard to remember the exact phrasing of the long title, etc), so I would like to abbreviate the template using a redirect. I created the new abbreviated Template:Long with, simply:

#REDIRECT [[Template:Template_with_very_very_very_long_title]]

Transcluding the template is thus much easier, by simply typing {{Long}}.

The problem, however, is that template subpages do not benefit from the abbreviation, so {{Long/sub1}} and {{Long/sub2}} don't work, unless I explicitly create these pages and manually redirect them to the subpages of the original template.

This is a bit odd to me, specially since one could create a Template:Long/sub1 with different content from Template:Template_with_very_very_very_long_title/sub1 .

Is this the expected behaviour of subpages?

Any thoughts will be greatly appreciated...

I would expect it. Pagenames are not hierarchical filesystem objects, but are instead independent database records.

The slash / chars only mimics a hierarchical filesystem. We can create subpage a/b/c before we create a/b, and we can back and also create a/b after we create a/b/c.

The tabs on a page or breadcrumbs on a subpage only mimic a software object that is a single internal entity with pointers to all its pages. For example, move a pagename, and the talk page is not moved, but must be moved independently.

The redirect only mimics an alias, and appears to be an internal pointer. In fact the redirect is an independent page, as subpages are, as they all are.

In the section 'Where it works' is a lot of information on using alternative slashes. I believe this is unnecessary information, as I have never seen people using these strategies to work around the problem of slashes.

I was the editor who added that information, and although I recall having a particular use case in mind, I forgot what it was and can't figure out from my edits to mediawiki.org on that day (12 May 2011). I know I talked to Brion about this, possibly on IRC, and it might be worth digging the IRC logs to find out what was my main motivation, as it might justify keeping the information for others who share the same needs. In any case, it doesn't seem terribly important, so feel free to remove the information about alternative slashes; this thread and the history of the page should be enough to get one started should it be necessary to unearth the info again. Cheers!