This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20119 - use custom page title in generated see-also xrefs
Summary: use custom page title in generated see-also xrefs
Status: NEW
Alias: None
Product: webplatform.org
Classification: Unclassified
Component: infrastructure (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Doug Schepers
QA Contact: public-webplatform-bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-28 15:44 UTC by Mike Sierra
Modified: 2012-11-28 20:36 UTC (History)
2 users (show)

See Also:


Attachments

Description Mike Sierra 2012-11-28 15:44:19 UTC
See apis/css-regions/NamedFlow for example. The See Also section features two 'css-regions'. These are stub titles to pages under /apis and /tutorials. XRefs should reflect custom titles "CSS Regions API" and "Using CSS Regions to flow content through a layout."

That problem, plus the fact that the tutorial sorted last in a long list of See Also links, led me to add a manual link to the tutorial with a hard-coded title.
Comment 1 Alex Komoroske 2012-11-28 16:42:18 UTC
When I looked at that page, it looked (vaguely) right to me--the "Using CSS Regions to flow content through a layout" article is in the bottom section with the right title.

Sometimes SMW does some aggressive caching so after you first edit you don't see the right values, but a few hours later it looks right. Generally you can go to Tools > Refresh on those types of pages to manually force it to regenerate.
Comment 2 Mike Sierra 2012-11-28 16:52:13 UTC
You're probably seeing the one-off "Other articles" link that I added by hand. The category-generated "css-regions" link between "getNamedFlows" and "Other articles" should appear with the custom title.  The other "css-regions" link above "CSSRegionStyleRule" should appear as "CSS Regions API".  I appreciate the point about caching, but this never appears correctly.
Comment 3 Alex Komoroske 2012-11-28 16:59:03 UTC
I see what's going on. I need to update Template:See_Also_Section to select Page_Title in the query, and then Template:See_Also_Item to use that value if provided.

I'll do this later today, hopefully.
Comment 4 Mike Sierra 2012-11-28 17:07:25 UTC
No rush, just noting one of the many little things that should get done sooner or later. ;-)
Comment 5 David Kirstein (Frozenice) 2012-11-28 20:20:27 UTC
I changed those 2 templates, because I had them open as part of my investigation of #20120 anyway.

See_Also_Item now uses: [[{{{1}}}{{#if:{{{2|}}}|{{!}}{{{2|}}}|}}]]
(showing the full link instead of "Article" if no 2nd parameter gets passed)

And See_Also_Section now selects Page_Title instead of API_name.

I hope that's okay with you, Alex.

Looking at the "Related articles" section of apis/css-regions/NamedFlow, there are 2 articles without a Property:Page_title. Actually there are tons of articles that don't include Template:Page_Title, could be a task for the bot to fix that.

If the list now looks okay to you Mike, you can remove the additional link to the tutorial. :)
Comment 6 Mike Sierra 2012-11-28 20:36:10 UTC
Those 2 pages are legacy pages that I'll flag for removal. Thanks

Re the rest, I logged a bug #20121 requesting templates provide more contextual info in see-also lists about interface members.  I can hand-code each as a custom title, but ideally it should be auto-generated.  I have roughly zero idea of how much templates can accomplish.