search

gregsadetsky / nycnoise

https://nyc-noise.com
15 stars 0 forks source link

Make sure that sitemap includes past (and future) months from db #225

Closed gregsadetsky closed 4 months ago

gregsadetsky commented 4 months ago

I.e. 2023-12 and further months that are not static pages, but actually populated from db

gregsadetsky commented 4 months ago

just confirmed they don't i.e. 2023-12 is not in there, 2024-01 isn't there either etc.

group all events by yyyy/mm (truncdate?) and add those urls to sitemap?

nycnoise commented 4 months ago

this is one of the things i've been trying to figure out / thinking thru with archive... that would rule!!!

gregsadetsky commented 4 months ago

sorry what do you mean? the sitemap is just this page which is really only picked up by google/bots. were you thinking of something else?

nycnoise commented 4 months ago

i was thinking that if this happens for the sitemap, it would also work for the "past" pages... is that... maybe?

gregsadetsky commented 4 months ago

Yeah no good point - the "past" page was imported as a static page and isn't dynamic. It's only changed if you edited it.

The past page is complicated because it includes links to months before we transitioned the site - and those page-months (sorry this is confusing) are also static pages...

Let's talk about it more. But tldr - that past page you linked to is not being kept up to date by django. You should be able to edit it though in the admin as a static page