Events List Widget – Recurring Event problem

[wpsitter]

Since the upgrade, “recurring events” message appears after title, date, time on the Events List Widget (theme: Genesis Streamline). No customization at our end:

Care Bus
May 30 @ 7:00 pm – 8:30 pm
|Recurring Event (See all)
Every week on Tuesday and Friday until December 30, 2014

Your Recovery Journey
June 2 @ 3:00 pm – 5:00 pm
|Recurring Event (See all)
Every week on Monday until July 7, 2014

[Brook]

Howdy wpsitter,

That is indeed a new feature we added to the list widget. Do you not enjoy the new functionality? You can of course change the look of this widget by using our themer’s guide. Or, if you are interested in a quick fix adding the following CSS would hide that field.

.tribe-events-adv-list-widget div.recurringinfo { display: none; }

Does that make sense? Do you have any feedback for us regarding this new feature? Please let me know. Cheers!

– Brook

[wpsitter]

It would be neat if the choice to include “recurring events” was integrated into the widget, as our recurring events are so frequent that it just gets annoying to see the prompt.
Thanks for the tips.

[dchaney]

I find the Recurring Event (See All) as pretty useless. Since the content of each recurring event is identical except for dates, the display is redundant.

[dchaney]

I’m using twenty-ten theme. Where would I best insert the css line mentioned above to remove the Recurring Event message? Thanks.

[dchaney]

I got it. I created a tribe-events-pro.css file with the code and created a tribe-events/pro folder in my theme. I then uploaded the new file to the new folder. Much cleaner look in the upcoming events widget!

[Brook]

I am glad you got it solved dchaney. Thanks for sharing your solution.

I can definitely see where you guys are coming from. The biggest reason for the See All link is so that people can catch a different time for the same event, if the current one does not work. But, if you do not want that link to be visible I can understand why.

Would you mind making this a suggestion on our user voice page? Perhaps something along the lines of “An option to disable the  Recurring Events (See All) Link in widgets”.

– Brook

[Debra Gallek]

I agree, this feature is not needed. Especially this part: recurring 11 times

[Susan Goodman]

I am using the Architect theme. I tried what dchaney did but it did not work. Where can I place that code…in which css file? I tried it in the Architect theme stylesheet but it did not work. Please help.
For now I limited the upcoming events list to display one event.
My client’s page is http://hudsonpride.org

[Brook]

Thank you for your feedback everyone. I have brought this matter up to the team, and we want to go ahead and implement an option in an upcoming release that disables this link. Even still, it never hurts to voice you support for this feature request that the OP submitted. That will definitely assist us in prioritizing this feature request.

Susan, the CSS I posted will work with some themes but not all. You will need to make sure that it is not getting overridden by another more specific rule in your theme. Sadly, this requires a fair bit of CSS knowhow. You should however be able to insert that CSS in any of the CSS files you mentioned. If you need more assistance with this please open a new topic so that your issue gets the attention it deserves, and detail the problem there along with a link to your website. While we do not ordinarily provide anything but generic CSS and rely on you to adapt it to your site, we might be able to make an exception for you 🙂 .

Instead of simply hiding this link, you can fully remove it from the HTML source as well. This can be accomplished by following this guide.

Since the original poster’s issue has now been resolved this topic marked for archiving to avoid his inbox getting spammed with others problem. If you need any further assistance please open a new topic. Thanks everyone!

– Brook

[Leah]

Hi there,

I just wanted to drop in and update you on the status of this issue. We are working on a fix, but we were not able to include it in our upcoming release (3.7). Correcting this problem is still important to us and we hope to have a fix done for a future maintenance release. We will do our best to keep you updated here on our progress. Thank you for your patience and understanding while we work on this.

Best,
Leah

[Author]

Posts