Forum Replies Created
-
Posts
-
Totally agree Geoff, WPML can be quite confusing. It’s just an anomaly, and I’m not at all surprised that one wasn’t captured! If there’s something that can be broken you can bet I’ll find it – it’s a special talent of mine.
Please feel free to close the ticket.Hey Andras
Sorry you are right! I was very quick to see a ‘bug’ because it worked sometimes, and didn’t work other times…
Plus I am moving to events calendar from another events software vendor that really doesn’t work with WPML very well. So I am hypersensitive to potential problems.
On this occasion though you are right: it was Mouse-Click-Copy-Paste error that caused my downfall, confused by it sometimes working swapping day to day and other times not at all.
Thanks then!Hi Geoff
Well, I checked this through and I think the instructions need to be modified slightly.
As far as I can see if you set up recurrence in Language1, then the date is appended to every instance of the event from the outset.
Consequently there is no ‘master’ event – only the earliest date in the series – and when you then follow the instructions to create the translated event then you have no opportunity to change the URL. OK, I use ‘duplicate’ rather than ‘overwrite’ – but they are essentially the same thing and following your instructions, with ‘overwrite’, the date is appended to the URL. There is no opportunity to edit the URL.
As things stand, then, the only way that I can see to modify this behavior through the control panel is a modified procedure:
1. create the event as a single event
2. create the translated event in language2 (3,4…) using duplicate or overwrite, and set the venue and organizer
3. go back to language1 and set it to be recurring
4. go back to language2 and create the recurrence rule
HOWEVER – caveat emptor – I have found now that with your method OR my method there is a major flaw since you have to manually set the venue and organizer on every instance of the recurring event – and that could be a huge task.
Now I can probably find a way of fixing this within the database if I am very careful, but it looks to me as though this area needs a bit of a rethink.
