Closed Bug 380348 Opened 19 years ago Closed 17 years ago

Create new RDF-based title-override mechanism

Categories

(developer.mozilla.org Graveyard :: General, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: sheppy, Unassigned)

Details

Since we're not using RDF for our upcoming breadcrumb system, we should look at leveraging that to implement title-override. This new title-override should also be able to override the main article title, not just the one in the breadcrumbs. Adding a template of the form {{titleOverride|new title here}} should insert an RDF entry for the page; then, when rendering pages, we should check for that entry and use it for the page title and breadcrumbs as applicable.
> Since we're not using RDF for our upcoming breadcrumb system Since we _are_ using RDF... got me confused for a bit.
(In reply to comment #0) > Since we're not using RDF for our upcoming breadcrumb system "now using"? > Adding a template of the form {{titleOverride|new title here}} should insert an > RDF entry for the page; then, when rendering pages, we should check for that > entry and use it for the page title and breadcrumbs as applicable. We need to take care that we don't end up with the ghost-override problem we had before, where removing the TO indicator doesn't remove the TO entry in the database. I don't know how the RDF arc management works; removing the TO arc at the very beginning of the save process would likely work. (As long as the TO template is processed at save time, and not just parse time, that is!)
Oops. That was supposed to be "now using," yes. The RDF gets updated automatically any time you save an edit to a page (this is done already), so if you remove a T-O, saving the page will remove the RDF from the database.
Severity: normal → major
Invalid now that we're on Deki.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Component: Deki Infrastructure → Other
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.