You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since it would be nice to have the detail view of all events in the XML sitemap of a page, an example configuration for tx_seo would be appreciated. I.E. in the extension manual or in an optional TS-Template.
If found the following issue on stackoverflow, but it doesn't work correctly, because the timestamp parameter is missing (or simply set to 0)
what do you mean with "doesn't work correctly"? I remember that post as I have tested and answered it.
Setting the timestamp to 0 activates an internal fallback process of events2. In that case events2 tries to find the next date, if not found it tries to find the last possible date, if that is not found, too, it displays the event start date of the event record. And yes, setting timestamp to 0 will result in 01011970_0000 in URI.
Well, I think I would expect every date of an event to have exactly one URL. Furthermore, an URL with a 01011970_0000 in it is not an URL I would like google to index.
Maybe a RecordsXmlSitemapDataProvider would help to find the first Date (timestamp) of an event?
Since it would be nice to have the detail view of all events in the XML sitemap of a page, an example configuration for tx_seo would be appreciated. I.E. in the extension manual or in an optional TS-Template.
If found the following issue on stackoverflow, but it doesn't work correctly, because the timestamp parameter is missing (or simply set to 0)
https://stackoverflow.com/questions/71444533/sitemap-for-events2
The text was updated successfully, but these errors were encountered: