event permalink structure

[Anonymous]

Hi. It seems that with recent updates, the structure of event permalinks has changed. It used to be /prefix/id/slug, where “prefix” is the set prefix, “id” a number and “slug” the string created from the event’s title. Now it seems to have changed to /prefix/slug, which means that slugs may need to be extended with a hyphen and a disambiguating number if a new event with the same slug is created. I think I prefer the old system, because many applications will feature events that are repeated with the same title (either systematic repeats that might be modelled as a recurring event in EME, or sporadic repeats that would be created by copying the old one). Is there any way for us to control how event permalinks are structured? Perhaps it might even be made possible if we could use placeholders such as parts of the event date, but also an increasing number so we could recreate the old style.

[Franky]

EME takes this duplicate-issue into account (as does wordpress) and adds a number if the slug already exists. Nothing needs to be done from your end.

[Anonymous]

Yes, I know, but I don’t like the URLs that arise as a result. I found the earlier version, where the ID would be prefixed and separated with a slash, better. It would be even better if I could configure the strategy via placeholders (and use parts of the event’s date and slashes). Currently, I can’t even use slashes when I manually edit the generated permalink, they are silently deleted.

[Franky]

The old way was not acceptable for others … the new method will stay in place now. Since I need to know how to parse the permalinks, own settings would cause too much trouble. So currently it is what it is.

[Author]

Posts