Daniel Fuchs
Forum Replies Created
-
You’re right, it was in my theme, more specifically in my passing of parameters to TinyMCE in
the ‘tiny_mce_before_init’ filter. Sorry for the fuss.I’ve just seen the very same error message at the bottom of the normal page editor. Seems to be a WordPress problem.
I can see the problem with existing links, and there might be other pitfalls, like when you change the date of an event but have already published links to it … although that’s probably not a very frequent scenario.
But maybe if you added this as an option in the ‘Customize slugs’ back-end section? That way site admins could opt in (and maybe get a little warning that existing links may break before they do so). Like WordPress does on its Settings -> Permalinks panel, but not as exhaustive. An option to add a yyyy/mm/dd slug component before the event name would be enough, in my opinion.
I also think that this depends a lot on the user. A professional event organiser will probably manipulate the slugs for event posts themselves to include as much SEO-relevant information as possible (including the date, maybe), but for a small NGO like mine with a lot of editors who lack that technical understanding, this is not feasible.
BTW, I appreciate that you can customize slugs. Makes it so much more localizable.
Thank you,
Daniel- This reply was modified 6 days, 2 hours ago by Daniel Fuchs.
Thank you Craig, that was what I needed.
I think it wouldn’t make sense to add events to a static menu, and I don’t use organizers, but pages for venues totally make sense to me. More so than category and tag archives.