Forum Replies Created
-
Posts
-
thanks, have added my vote. that’s one part of it i think.
we are basically trying to find the best way to specify events that occur every day over a set number of days. they should in an ideal world be specified as ‘recurring’ events, as each ‘day’ is discrete e.g. you can go ice-skating any day during december, it’s not a single event spanning several days. BUT if we do this we end up with loads of events in the back-end UI and our category slider then contains loads of ‘replicates’. key thing is how these type of events appear in the widget calendar list and category sliders.
i agree it’s a tricky one to get heads around, but at the moment i don’t have a solution for my client.
at the moment i think we need to stick with using “single event spanning multiple days” to avoid replication in our “featured events” slider which is a more significant problem. and if we do that then we need to have some way to customise the widget mini-list under the sidebar calendar to avoid our currently confusing: “11 November 4pm – 24 December 6pm”. any thoughts/suggestions on how to customise this? i’m looking at https://theeventscalendar.com/function-category/events/ and i’ve tried editing the single-event template to use alternatives to tribe_events_event_schedule_details(); like tribe_get_start_date(); but this frustrating echoes the TIME as well… (ideally the calendar mini-list dates shown should (dynamically) relate to the DAY clicked on rather than the entire span of the event. this demonstrates the complexity of the problem!)
as i say, going round in circles…in terms of the mini-list ordering/prioritisation under the widget calendar, it would be ideal to prioritise (put at the top) events that START on the specific day clicked on, followed by recurring events that are “in the middle of a run” as it were. is there any way to do that conditionally?
(this might sound ‘edge-case’ but i think it’s quite fundamental to user-focused design and useability if you are trying to manage LOTS of events)Hi george, does v4.3 address the duplication issue when using ‘preview’? i realise i jumped in on greg’s original thread here and it now seems this is a separate issue, but just wondered whether you were able to acknowledge that using ‘preview’ does have issues in terms of unwanted venue and organisation replication?
thanks
chrishi, thanks for the reply. i’ve updated to the latest event calendar plugins (inc. ‘pro’) – still getting this issue.
a bit of further information. if i switch to twenty15 then the tag archive pages work correctly. so i’ve also written to the theme developer about this issue. but i’m not sure why the tag archive pages wouldn’t work. i note they DO work (using my required theme) when the tags are created via POSTS, it’s tags created via EVENTS where the tag archive pages don’t work.this question is still relevant: ARE all tags shared between tribe_events CPTs and standard WP posts? (i’m confused about this as my content person has been doing content not me). the tag list under POSTS seems to be the same as the tag list under EVENTS – are they interchangable? i note if i delete a tag in the ‘event’ tag list then it also disappears from the ‘post’ tag list. is this expected behaviour with ‘the events calendar’?
thanks
thanks george, yes i tested the theory after talking to my client. Using ‘Preview’ does indeed lead to (potentially large numbers of) duplicate venues without the editor realising until later when they look at the venues list.
further to this, i believe the ‘merge replicates’ button (in settings) only works if the replicate venues are identical. So if a content editor uses Preview several times whilst updating venue fields on an Event then they may end up with (for instance) 6 replicate venues, and the ‘merge replicates’ button may remove 3 of these but leave the other 3 if they vary a bit.
it seems to me that work needs to be done to stop venues/organisers being replicated on each ‘Preview’ click. i guess the initial ‘Preview’ call would require a venue/organiser to be created, but subsequent ‘Previews’ need the venue/organiser records to be checked and updated if necessary rather than generating a new one each time.
(i note in a couple of other threads about this issue WPML is mentioned. i think this is a red herring, WPML is not in use on our site)
Further to this, in General settings, the ‘Merge replicate venues’ button reduced our venues from 112 to 62, but the button then disappeared.
Good news, there is a functions.php code snippet in this thread which makes sure the dedupe button remains in settings (rather than disappearing after using it once):Am still testing, checking things at this end, it’s a moving target right now… but more and more I think the ‘Preview’ glitch is key here
please can i offer an insight into this issue. i’ve set up a site for a content owner and they have come across this rather major “duplicating venues” issue. with a bit of discussion i was able to work out that it’s actually caused by the content editor using wordpress’s “PREVIEW” functionality.
so… they create a new event, start entering information for the venue, and IF THEY CLICK ‘Preview’ in the top right panel (rather than ‘save draft’ or the main ‘publish’ button) THEN it creates a venue at this point. because they have not saved the EVENT yet, they then may click ‘preview’ a few more times whilst setting up the event. and, BANG, they’ve (unintentionally and in the background) created several replicate ‘venues’ (event though they haven’t saved the event itself yet!).
Also, I used the ‘merge venue/organiser’ button in the event settings to help dedupe existing venue replicates, but it disappears after running this once.
I think this is quite a big issue with the duplicate venues, and i’ve seen several forum posts about it, but no one has mentioned the REASON for it – i believe it’s to do with content people using “Preview” (something that very few developers/admin people ever use!)
