[404] Three rich text resource pages at mozilla.org/editor

RESOLVED FIXED

Status

www.mozilla.org
General
--
major
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: Terry R., Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
From here:
https://developer.mozilla.org/en/Rich-Text_Editing_in_Mozilla

at the bottom, under Resources, the three links:

mozilla.org's rich-text editing Specification
http://mozilla.org/editor/midas-spec.html

mozilla.org's rich-text editing Demo
http://mozilla.org/editor/midasdemo/

Converting an app using document.designMode from IE to Mozilla at mozilla.org
http://www.mozilla.org/editor/ie2midas.html

are 404
Editor content was moved in bug 453506.

Ehsan, aside from fixing the links on MDN, are there any redirects that need to be set up here?
(In reply to Terry R. from comment #0)
> mozilla.org's rich-text editing Demo
> http://mozilla.org/editor/midasdemo/

According to bug 453506 comment 10 this should be a redirect to:

http://www-archive.mozilla.org/editor/midasdemo/

That isn't happening.

Promoting to major as this is a big test bed for us and is referenced in various bugs etc.
Severity: normal → major

Comment 3

6 years ago
CC'ing James Long who knows how the current redirect system works.
The only redirect I see is this URL:

http://www.mozilla.org/editor/midasdemo/securityprefs.html

To add redirects, simply add the source and target URLs to the org-urls-301.txt file: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/org-urls-301.txt?view=markup

Updated

6 years ago
Duplicate of this bug: 738550

Comment 6

6 years ago
All of the www.m.o links that used to exist for midas demo need to be redirected to www-archive.m.o.
(Assignee)

Updated

6 years ago
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org

Updated

5 years ago
Blocks: 879544
Looks like the redirects have been setup at some point.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.