Closed Bug 604060 Opened 15 years ago Closed 15 years ago

Remove (at least a few key) PHP wiki pages

Categories

(support.mozilla.org :: Knowledge Base Software, task, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jsocol, Unassigned)

Details

At the very least, we should remove a few key Tiki/PHP scripts that people might confuse users. I'm thinking of things like: tiki-editpage.php tiki-page.php tiki-index.php tiki-listpages.php tiki-pagehistory.php tiki-rename_page.php tiki-removepage.php tiki-approve_staging_page.php tiki-edit_translation.php Any actions taken using these scripts would not affect the actual Knowledge Base, and could lead to confusion about why. (cf bug 584850 and the trickle of forum posts after 2.1 and 2.2.)
Guys (cc'ed), any thoughts on good redirect/fallback targets for these pages? My guess is that editpage and edit_translation are the ones most commonly bookmarked, so we probably want to send these people somewhere. Not sure, maybe a link to the contributor dashboard is good enough?
I doubt anyone would bookmark the editpage or the edit translation page as is since the URL would need a pagename in order to not give an error and bookmarking /specific/ edit or translation pages isn't useful at all. The contributor dashboard is fine as a fallback but even a page with a note that tells contributors to go to the start page and navigate again is fine.
What does tiki-page.php do? Anything that's probably linked to from the outside world should be mapped, but for the reasons Cheng cited I'd also be okay with breaking bookmarks for contributors, this is a new system, and at least it would alert people to the fact, if they mised all the other announcements ;)
tiki-page.php may actually be part of a non-wiki page feature we don't use. I just looked for "page" to generate the initial list.
These files have been inaccessible since r76400. Feel free to reopen or file new 1.5.7 bugs if there are specific redirects not handled.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.