Eugene Kyale

Hi @mrwweb

That’s correct! The ID attributes have not been removed from the HTML markup. We made sure to keep them intact to avoid disrupting any existing style customizations.

What we’ve done instead is adjust our targeting approach for specific selectors. This change is intended to ease the process of overriding styles without affecting previously implemented customizations.

We appreciate the feedback and value the importance of keeping our developer community informed. However, at this time, we’ve opted to make these improvements in an incremental manner and do not currently have plans for a specific communication regarding this change. That said, we’re constantly evaluating our communication strategies, and your feedback is invaluable in that process.

Rest assured, significant updates and changes will always be communicated in a timely manner. Our main priority is to ensure our platform remains user-friendly, adaptable, and accessible for all our users, including developers like yourself.

If you have any further questions or need more clarity, feel free to ask. We’re here to help!

Cheers,

Eugene.

Hi @mrwweb

Thank you for your inquiry regarding the recent update. I understand your need for further clarification and I’m here to provide it.

This particular update is focused on improving the customization experience for themers and developers. We have made changes to the CSS specificity in our code in order to facilitate easier overriding of our styles. The aim is to make our plugin more compatible and flexible with various themes and page builders, giving you more control over the appearance and style of your pages.

To put it in practical terms, previously, our styles were targeted using IDs (like #tribe-events-content), which have high specificity and can be challenging to override. Now, we are targeting classes instead (like .tribe-events-single), which have lower specificity. This change makes our styles easier to override.

To illustrate, if you wanted to customize the appearance of an element previously targeted with the ID #tribe-events-content, you might have had to use the same ID in your style sheet and even then, due to the cascade and specificity of CSS, your changes might not have been applied.

With this change, we have shifted our focus from targeting the ID to targeting the already existing class .tribe-events-single on the same element. So now, instead of having to override styles tied to the ID #tribe-events-content, you can use the .tribe-events-single class in your custom styles.

This should make it significantly easier for your custom styles to take precedence.

Let me know if you any additional questions.

Regards,

Eugene.

Hi @passedevant, I’m sorry that you’re experiencing this issue.

I’ve tried reproducing it using the plugin versions you specified without any luck.

Do you mind sharing the url to the page where the issue is occurring so I can have a look?

In the meantime, please perform a conflict test to try and identify the cause.

I look forward to hearing back from you!

Regards,

Eugene.

Hi @freddredirl I just took a look at the URL you shared and created a CSS snippet to fix the issue.

.fusion-body.single-tribe_events .tribe-events .tribe-events-c-subscribe-dropdown .tribe-events-c-subscribe-dropdown__content {
    position: relative;
    top: 0;
}

Please add that to your site and let me know how it goes.

Cheers,
Eugene.

Hi @anabellafp thanks for reaching out!

This is a tough one to troubleshoot without a visual reference.

Have you performed a conflict test to rule out any potential theme or plugin conflicts that might be at play?

Also, do you have a staging site where the issue is replicated and which you can share the credentials so I can do some troubleshooting?

Let us know how it goes.

Cheers,
Eugene.

Hi @esk11211 thanks for reaching out!

The link you shared above seems to be broken. Does this appear on every page on your site or only on event related pages?

Regards,
Eugene.

Hi @ryounisbbi

I’m happy to report that we’ve recently released an update to the Hubspot extension that fixes this issue.

Please head over to your site and make sure the extension is up to date. If your issue is still present, let us know and we’ll continue troubleshooting with you.

Thank you for your patience as we worked through this, and have a great rest of the week!

Regards,
Eugene.

@gianfry70it @kytmagic awesome! A permanent solution will be included in our upcoming release.

Thanks again for hanging in there.

Cheers,
Eugene.

Hi @gianfry70it and @kytmagic ,

Thank you very much for your patience on this issue. We have a solution which you can use in the meantime before we release a permanent fix on the 17th of March.

Here is a download link for a version of The Events Calendar which contains a solution. Please upload it to your site and let me know if the issue gets resolved on your end.

Please make a backup of your site before uploading the file or upload it to a staging environment first.

Let me know how it goes.

Cheers,
Eugene.

Thanks @philsbury got it, I’ll set the Remember length to something brief like 1 minute. It might not work exactly as I wish but its the next best thing. Thanks for the response, great plugin btw.

Hi @danaceks, there’s a setting labelled Events template under Events → Settings → Display. The template selected there is responsible for displaying the event pages.

By default its set to the Default Events Template (which does have sidebar support).

You can select any template that has sidebar support from the dropdown and it’ll appear on your event pages.

Hi @creatordesign, you can add a 15 minute interval by clicking on the “to” time field and tying in the time instead of using the select.

Cheers,?
—
Eugene.

There’s been no movement on this ticket for a while now, so I’m going to mark it as resolved.

If you still need assistance with this, please open a new ticket and we’ll be happy to help.

Cheers!

There’s been no movement on this ticket for a while now, so I’m going to mark it as resolved.

If you still need assistance with this, please open a new ticket and we’ll be happy to help.

Cheers!

There’s been no movement on this ticket for a while now, so I’m going to mark it as resolved.

If you still need assistance with this, please open a new ticket and we’ll be happy to help.

Cheers!