Help talk:Subpages

Jump to navigation Jump to search

About this board

@Toppole69


Any way to hide parent pages in the title?

5
Leduyquang03 (talkcontribs)

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?

DrShaman1 (talkcontribs)

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

Leduyquang03 (talkcontribs)

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

DrShaman1 (talkcontribs)

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

Leduyquang03 (talkcontribs)

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.

Reply to "Any way to hide parent pages in the title?"

undisplayable character "big solidus" ... big mistery

1
Wladek92 (talkcontribs)

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)

Reply to "undisplayable character "big solidus" ... big mistery"

Confused by behavior of relative paths with multiple levels of transclusion

1
108.4.137.201 (talkcontribs)

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.

Reply to "Confused by behavior of relative paths with multiple levels of transclusion"
MaxEnt (talkcontribs)

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? ~~~~

Harry Wood (talkcontribs)

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

Reply to "Rename semantics"
Rbirmann (talkcontribs)

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...

Cpiral (talkcontribs)

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.

Reply to "Redirects and Subpages"
John Vandenberg (talkcontribs)

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.

Waldyrious (talkcontribs)

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!

Reply to "Alternative slashes"

Can i use altenative for my topic//

1
Jonson seol (talkcontribs)

Can i use altenative for my topic//

Reply to "Can i use altenative for my topic//"
2001:4CA0:0:F222:9CBA:99AE:545C:CF7E (talkcontribs)

How can I remove the automatic breadcrumb when I create a Subpage? I already use a Breadcrumb extension and I wanna keep that one.

Reply to "Remove Breadcrumb"
Be..anyone (talkcontribs)

<whine> Importing known templates from en:w: or m: to smaller MediaWiki projects is an obvious plan, but sadly many templates now use the (in essence unnecessary) /doc subpage style of documentation. But subpages in the template namespace are not enabled in MW, therefore imported templates relying on {{BASEPAGENAME}} or {{SUBPAGENAME}} can fail in hard to debug ways on other MW installations until an admin figures out how to enable this feature manually for the template namespace. This MW default should be changed. </whine>

I still refuse to use my new commons account on en:w: or m: or mediazilla:, the reasons to destroy an old 2006 account are still valid wrt en:w:, and all the moved to mw: pages here certainly contributed to that decision. 89.204.153.161 16:08, 15 August 2011 (UTC) Text copied as is from meta. Be..anyone 17:09, 15 August 2011 (UTC)

John Vandenberg (talkcontribs)

This isnt the best spot to request changing the default settings of a config variable. Bugzilla: would be better. I didnt find any bugs about this exact issues. Requests for comment may also be useful.

Be..anyone (talkcontribs)

Somebody here decided to disable the feature, or didn't bother to enable it: It's not a bug, it's a feature.

[[Category:Users with intentionally unusable mediazilla: accounts]]

Reply to "Wrong MW defaults"
John Vandenberg (talkcontribs)

According to MediaWiki:Subpagesortkey-desc, it is possible to change the default sorting of subpages. I didnt see this documented here yet. I dont know enough about it to write that up.

Reply to "sortkey"