If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

provide Web-tech blog account access to Gen Kanai to clear out spam & close comments

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
7 years ago
3 years ago

People

(Reporter: gen, Assigned: fox2mike)

Tracking

Details

(URL)

(Reporter)

Description

7 years ago
If provided an account to this blog, I will clear out the spam, close comments and then file a separate blog to move this blog to static files.
Assignee: nobody → server-ops
Component: Other → Server Operations
Product: Websites → mozilla.org
QA Contact: other → mrz
(Assignee)

Comment 1

7 years ago
Gen,

You can login to https://developer.mozilla.org/web-tech/wp-admin/ with your LDAP credentials. And you should be able to remove spam comments etc.

Comment back here when it's good to be removed.
Assignee: server-ops → shyam
(Reporter)

Comment 2

7 years ago
Hey Shyam, thanks but I think my privileges are not set correctly.  I can log in and see the admin screen but do not have the buttons/links for deleting spam, etc. Can you double check the settings on my account?
(Assignee)

Comment 3

7 years ago
Gen,

You have new access credentials in your inbox, please use those, should help.

Thanks!
(Reporter)

Comment 4

7 years ago
Shyam, please double-check but I believe I have cleared out all the comment spam and have closed both comments and trackbacks on all posts.  If you can confirm, please close this bug.

If I need to file a separate bug to move this blog to static files (so we do not have to update it further) please advise.  Thank you.
(In reply to comment #4)
> If I need to file a separate bug to move this blog to static files (so we do
> not have to update it further) please advise.  Thank you.

Uh, why? This blog is still being used.
(Reporter)

Comment 6

7 years ago
(In reply to comment #5)
> (In reply to comment #4)
> > If I need to file a separate bug to move this blog to static files (so we do
> > not have to update it further) please advise.  Thank you.
> 
> Uh, why? This blog is still being used.

We had a discussion about moving all future web-tech content to the Hacks blog (having two is redundant.)  In this discussion we also decided to kill off the MDC Webwatch blog which is now gone.
(In reply to comment #6)
> We had a discussion about moving all future web-tech content to the Hacks blog
> (having two is redundant.)  In this discussion we also decided to kill off the
> MDC Webwatch blog which is now gone.

Has this been announced anywhere? web-tech was used less than a month ago by Waldo...
(Reporter)

Comment 8

7 years ago
(In reply to comment #7)
> (In reply to comment #6)
> > We had a discussion about moving all future web-tech content to the Hacks blog
> > (having two is redundant.)  In this discussion we also decided to kill off the
> > MDC Webwatch blog which is now gone.
> 
> Has this been announced anywhere? web-tech was used less than a month ago by
> Waldo...

Very true.  Not sure it has been announced anywhere per se.  Let me ping someone...

Updated

7 years ago
Whiteboard: [on gen, needs notification]
(In reply to comment #7)
> Has this been announced anywhere? web-tech was used less than a month ago by
> Waldo...

... which precisely shows the problem. That was the first update on that blog in almost a year, as opposed to Hacks which is updated more frequently. We should be reducing the number of channels that people need to think about subscribing to and contributing to.

The content will be preserved on Hacks. No need for an announcement, just a redirect, which will be handled separately from this bug when the content is moved over, I suspect.
For the record, that was no timely post: it was some sort of glitch in which several yearish-old posts were reposted.
(Assignee)

Comment 11

7 years ago
Please re-open when you lads decide what you'd like to do with this.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
Shyam: see comment 4; if you can confirm, then this bug is RESO FIXED not INCOMPLETE.

Gen: please go ahead and file the bug to do the static redirects. Reed's concern isn't really valid, we don't need to announce this formally.
(Assignee)

Comment 13

7 years ago
(In reply to comment #12)
> Shyam: see comment 4; if you can confirm, then this bug is RESO FIXED not
> INCOMPLETE.

Yikes, my bad. Thanks Mike.

Gen, Took a look around, seems alright.
Resolution: INCOMPLETE → FIXED
(Assignee)

Updated

7 years ago
Whiteboard: [on gen, needs notification]
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.