[Barry]

No problem at all – I’ll close this thread since we can’t do much else right at this moment but do look out for a fix in a future release (realistically it probably won’t quite make the very next maintenance release, though).

Thanks again!

[Barry]

It’s not something we can reproduce; if you disable all other plugins and revert to a default, unmodified theme do you experience the same thing?

[Barry]

Hi Adam:

Again, essentially the same thing is happening as in the previous screencast and it all looks in order. In this instance you are editing Bible Study N4 (dated Aug 12) – but note that:

A) All other events named Bible Study N4 taking place later in the month already belong to a named venue – as before, that suggests that although they share the same name they are actually a different chain of events

B) Once you make the change and return to the list of events you seem to be highlighting with your mouse pointer the Bible Study N4 date taking place on Aug 5 (which is earlier than the one you edited). Again, selecting All Events really means that the change will apply to the current and all future instances – but not to past instances

Does that make more sense? Essentially it all seems to me to be operating as expected, though I can appreciate it may be a bit confusing.

[Barry]

Hi Ceci, it sounds as if perhaps your theme restricts featured image support to a select handful of post types rather than automatically granting it to all types.

Can you contact the theme author and ask if there is a clean way to add additional types that won’t interfere with their work? In this case, the type we want to add is ‘tribe_events’ (the post type name can also be accessed using TribeEvents::POSTTYPE – which you could mention, too).

[Barry]

I think there’s perhaps a little confusion here, but it basically all looks fine to me. That said, it’s difficult to quickly take in all the information we need from a screencast – but let me run through the way it looks to me:

• Initially we see the list of events – the event you go on to edit is dated Aug 20 and has an Unnamed Venue
• There are other events of the same name on Aug 27, Sep 3 and Sep 10 – however, since these already have an actual named venue that makes me think that they are in fact a quite separate chain of events which just happen to share the same name
• When you edit the event dated Aug 20 you change the venue and apply the change to all events
• You return to the list of events and the event on Aug 20 correctly shows as taking place at the named venue
• The other future events of the same name are, as above, either a completely separate chain or are anyway already marked as taking place at that same venue

Does that make more sense? If not it would be great if you could distil the problem down into a set of bullet points as, right now, it looks as though everything is functioning as expected.

Thanks!

[Barry]

Excellent!

[Barry]

Hi Adam: if you have a sequence of 10 recurring events and edit the 5th of those, change something and apply the update to All Events this really means that it will apply to the current and all future instances (ie, the 5th, 6th, 7th … through to the 10th event).

Is that what you were trying to highlight with the screencast?

[Barry]

OK – and have you tried deactivating all other plugins and reverting to a default, unmodified theme? If so, did that resolve this and did it allow you to figure out where the conflict lies?

[Barry]

Great – so regarding the links at the top of the page, did you remove all of those lines of code (there are basically two sets of the same thing, one closer to the top and one closer to the bottom of the template)?

[Barry]

Your theme’s functions.php – or that of your child theme if you’re using one – or else a custom plugin would probably be the most suitable homes for this 🙂

[Barry]

Excellent, look forward to seeing it – and good luck!

[Barry]

And to change the border (I mistakenly gave you an example that changes the background) you would simply change that to something like:

#tribe-events-photo-events .vevent.tribe-events-photo-event:hover { border: 4px dashed #650; }

[Barry]

Hi Aurelio – that should be possible with a small piece of CSS:

.tribe-events-photo-event:hover { background: #650; }

Please refer to our Themer’s Guide for instructions on putting this rule in place (if you’re not already familiar with the process).

Thanks!

[Barry]

Hi Adam, it sounds like you’re coming up against a known bug.

Can you review this fix and if it sounds like it fits your problem try applying it? We do intend to fix this in a future maintenance release so if you aren’t happy or have no success with the suggested fix do know that this will be resolved in due course.

Also, if the problem is in fact different in some way please just let me know with a description of what you are seeing and we’ll do our best to help 🙂

[Barry]

So these steps should help you to get rid of those links. For any other issues can I ask that you create new threads (one thread per issue)? Thanks!

[Author]

Posts