10

The new blog design looks great! But it's left behind a feature that was really useful for navigating through old content: the archive/ date-based browsing page(s).

The old blog design had date-based archive pages; e.g. https://stackoverflow.blog/2023/ used to lead to a nice display of all blogs posted so far in the year 2023:

Screenshot of blog pre-2023 redesign, on the "yearly archives" page for the year 2023

There were even monthly and daily versions!

But now, links to the archive pages lead to a 404, and there doesn't appear to be any way to browse in any date-conscious means at all. Only the newest posts under a given tag are visible, and no sort options are available.

Has the feature been relocated somewhere that I've missed? If not, can we have it back please? It was especially useful for tracking down old posts where I know the time frame but not other details.

The "Show more" button at the bottom of those tag pages (e.g.) also appears to be broken; clicking it generates a console error and shows a spinner that spins forever. (Since fixed)

Improve this question
8
  • 6
    "Show more" should be working now!
    – David Longworth Staff
    Commented Aug 30, 2023 at 16:01
  • Yes, it broke a lot of links.
    – This_is_NOT_a_forum
    Commented Jan 5 at 18:35
  • @Slate nitpicking perhaps, but I think status-planned should be reserved for things that are, well, actually planned to be done. Here, obviously, that was not the case. Don't know what you can do now, but perhaps cleaning the two remaining requests with that tag that aren't likely to be actually done (over three years in the past, both) would be a good idea. Thanks.
    – Shadow Wizard
    Commented Aug 29 at 14:26
  • 1
    @Shadow Not a nitpick at all. I explicitly state that's what status-planned for in a recent post :) Do you have links to the other posts you're thinking of?
    – Slate StaffMod
    Commented Aug 29 at 16:26
  • @Slate one, and two. On closer look both are tricky, but still, don't think it's good to have them appear as planned for so many years. The first one got answer saying that something else was done, kind of workaround that does solve the main issue, but that's not what has been asked - the profile settings do not mention any cookie preferences. Second also tricky as it depends on the Stacks Editor. [cont.]
    – Shadow Wizard
    Commented Aug 29 at 17:31
  • [cont] Stacks Editor is planned to be rolled as default to all the network, by this solving the second request, but.... it can take several more years. What to do? Not sure myself.
    – Shadow Wizard
    Commented Aug 29 at 17:33
  • 1
    @Shadow One step ahead of you. These two are already on my shortlist to pursue. Those two will be slower to update because I don't want to move them without understanding the chain of responsibility better. Cookies because it's a legal / privacy issue (I won't generally touch that topic without a 2nd CM + legal), and Stacks Editor because it affects everything and is somewhat sensitive.
    – Slate StaffMod
    Commented Aug 29 at 17:49
  • @Slate edge cases, so yeah - fair. :-)
    – Shadow Wizard
    Commented Aug 29 at 18:38

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .