1. Using the image uploader, add an image to <https://support-stage.mozilla.org/en-US/kb/How+to+contribute>. 2. Go to <https://support-stage.mozilla.org/tiki-admin.php?locale=en-US&page=gal>, and under "Exterminator" click [Remove]. (This was added in bug 449440) 3. Wait a while (an hour or two). Image is no longer there. This is what I think caused bug 487947. Notes: * How+to+contribute page is assigned to mozgn.css and is in the "How to Contribute" category. * to use the image uploader, you need to unassign the theme and move it to another category (Live Chat). See bug 485665.
Wow this broke the SFD pages when I wasn't looking. Way to freak me out for 10 minutes. I'm going to bump the severity of this because we can't rely on external servers to host images for How to Contribute pages, that's really not a good workaround at all.
Severity: normal → major
Why was the severity bumped? Why are we using the Exterminator feature at all?
We use the exterminator to remove images uploaded by spammers.
Assignee: nobody → paul.craciunoiu
Target Milestone: --- → 1.3
I think bug 485665 may have fixed this. I set https://support-stage.mozilla.org/en-US/kb/How+to+contribute back to mozgn.css and tried the steps in comment 0. So far the image is still there. Of course, now that we might be using mozgn2.css for the How to contribute page, the patch from bug 485665 needs to be applied to mozgn2.css. :-)
(In reply to comment #4) > Of course, now that we might be using mozgn2.css for the How to contribute > page, the patch from bug 485665 needs to be applied to mozgn2.css. :-) mozgn uses the same editpage template as mozad. To fix this for mozgn2 would require a one-line patch to create a link to use the same editpage template. We can turn this bug around and make it about that, or file a separate one.
I've filed bug 505994.
Thanks Chris! Is this bug fixed, then?
I'd like to verify on prod ... just in case. Do we know how the image exterminator works?
This looks good on prod. Resolving FIXED as a result of bug 505994.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Target Milestone: 1.3 → 1.2.1
You need to log in before you can comment on or make changes to this bug.