Closed Bug 588968 Opened 14 years ago Closed 14 years ago

Blog.Mozilla.com archives have a 404 - Not Found problem

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sprior, Assigned: oremj)

References

()

Details

Every time I try to access an archive month on the Mozilla.com blog it comes up with a "404 Not found sign" 

Also, it only goes back to September 2009. Can we access the archives prior to September 2009?
Assignee: nobody → jslater
It's not just archives, it's any entry; over to IT, who set up/maintains the blog.
Assignee: jslater → server-ops
Component: www.mozilla.com → Server Operations
OS: Mac OS X → All
Product: Websites → mozilla.org
QA Contact: www-mozilla-com → mrz
Hardware: x86 → All
Version: unspecified → other
Severity: normal → critical
Assignee: server-ops → jeremy.orem+bugs
Just had to resave permalinks. I think this is some sort of wordpress bug.

Archives past sep 2009 are available (http://blog.mozilla.com/blog/2008/09/) the list just isn't that long. I don't know if that is an option or if you need to get the theme developer to make the list longer.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Um, yeah, all pages except the home page and the search result page are now 404.
And http://blog.mozilla.com/feed/
http://www.google.com/search?q=site%3Ablog.mozilla.com%2Fblog
etc.

Need to fix this prior to the Beta 4 blog post.
Blocks: 586300
Status: REOPENED → NEW
We're launching at noon, so getting this fixed asap would be much appreciated.
Looking at this now.
Seems to be working now.
Status: NEW → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Ran an automated link-checker on the site: http://validator.w3.org/checklink/checklink?uri=http%3A%2F%2Fblog.mozilla.com&hide_type=all&depth=&check=Check.  Passed.

Verified FIXED -- hopefully it stays that way :-)
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.