Closed
Bug 1203410
Opened 9 years ago
Closed 9 years ago
Page about custom properties inaccessible
Categories
(developer.mozilla.org Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: teoli, Unassigned)
Details
(Keywords: in-triage, Whiteboard: [specification][type:bug])
What did you do? ================ 1. I tried to rename the page Web/CSS/var-* to Web/CSS/--* , as the way to declare custom properties in CSS have been changed. I used the regular page move feature with Web/CSS/--%2A as the new slug. What happened? ============== The results is this (Web/CSS$children): { "locale": "en-US", "url": "/en-US/docs/Web/CSS/--%252A", "subpages": [ ], "slug": "Web/CSS/--%2A", "title": "Custom properties (--*)" }, The page is inaccessible with any of the slug: /en-US/docs/Web/CSS/--%252A and /en-US/docs/Web/CSS/--%2A The redirect page leads to a 404. Following the link in the Revision dashboard leads to a 404. What should have happened? ========================== Coherence. No data loss. Allow both - and * in slugs (they are valid, the page move feature is limited to trusted users) Is there anything else we should know? ====================================== Data is inaccessible right now.
Reporter | ||
Updated•9 years ago
|
Severity: normal → major
Comment 1•9 years ago
|
||
I'm curious how you were able to change the slug to --* (or apparently --%2A or --%252A)? When I try on my local box, the page move UI forces the new slug to be --_. If I create a *new* page with a --* slug, the new page UI changes the * to _, but I can over-write it in the slug input box and the page comes out fine: https://developer.mozilla.org/en-US/docs/User:groovecoder/--* So, it is/was a data corruption issue with the page move, and not a site-wide apache/htaccess/url issue. That being the case, I updated the slug value of the document in the database to be '--*', and I updated the REDIRECT href to the new value. So, https://developer.mozilla.org/en-US/docs/Web/CSS/var-* is properly redirecting now. I'm going to call this RESOLVED:FIXED unless you find other page moves with * characters that break in the same way.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Luke Crouch [:groovecoder] from comment #1) > I'm curious how you were able to change the slug to --* (or apparently --%2A > or --%252A)? When I try on my local box, the page move UI forces the new > slug to be --_. I put Web/CSS/--%2A in the page move slug field (as * was being converted to _). I didn't expected it to lead to a problem. > > That being the case, I updated the slug value of the document in the > database to be '--*', and I updated the REDIRECT href to the new value. So, > https://developer.mozilla.org/en-US/docs/Web/CSS/var-* is properly > redirecting now. Thanks perfect! > I'm going to call this RESOLVED:FIXED unless you find other page moves with > * characters that break in the same way. No, that's fine. That's really an unusual case, and I don't expect any more of these to happen (though we never know we specification bodies ;-) ) Many thanks!
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•