The Events Calendar 6.0.1

Hey @mputman007

Yikes! That’s not good.

I would recommend reaching out to the dev team behind The Events Calendar Shortcode & Templates Pro to let them know.

In other words, we don’t have much control over compatibility with third-party add-ons for The Events Calendar and I am sure that letting them know will be super useful to everyone using this.

Hang in there!
Geoff

No, it is not good, not at all. I have already reached out to the dev team behind The Events Calendar Shortcode & Templates Pro, but here’s the thing. The Events Calendar (and contributors) are always quick to point the finger at someone else. You DO have control over compatibility with third-party add-ons and customizations. All you have to do is work WITH add-on and web developers DURING the development cycle. You see us as competition. You should see us as business partners.

6.0.0 worked just fine with The Events Calendar Shortcode & Templates Pro plugin (also works with 2.9.3), but obviously, something changed between 6.0.0 and 6.0.1 with regard to the naming of the event title, since now it pulls that page name for all events. We’re digging into their plugin to try to fix it. You could be “super useful” if you could tell us with constants in functions changed between 6.0.0 and 6.0.1.

This happens a lot, so much so that there are several knowledge base and troubleshooting posts (https://theeventscalendar.com/knowledgebase/k/custom-templates-custom-hooks-and-upgrading-to-tec-6-0/ and https://theeventscalendar.com/knowledgebase/k/calendar-page-shows-event-title/ to name two to them) located on The Events Calendar website regarding changes to function contant names that have caused customization and compatibility issues.

This is a poor practice (and probably not a micro “dot release”) to keep renaming constants in your plugin, especially if you are not going to put the specific information in the release notes. It almost ensures that web developers and third-party plugin developers will stop trying to chase nearly continuous compatibility issues to add the customization functionality that should already be included in the plugin. Especially so, for the price you are charging for the plugin.

So, why don’t you be “super useful” and try to work with the community buying your plugin instead of the all too often, shoulder shrug?

• This reply was modified 2 years, 1 month ago by mputman007.

Hi @mputman007
Thanks for your reply. I fully understand your frustration, something breaking after an update is definitely not good. As you can imagine, it is also not our intention to break things with updates.

I created an internal bug ticket for this, and I have added your case to it. Thanks for all the details, I will definitely pass it along to our devs.

Our team will assess the severity of this problem in relation to other open bug reports. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. This means that at this point we are unable to give you an estimate of when the issue is going to be fixed.

If you have any further information that may affect the prioritization or help our development team solve this bug, please share it with us.

As soon as we release a fix for this issue we will post an update here in the thread.

Appreciate your patience. If you do have other concerns or issues you need help with, please create another support topic as indicated in the www.remarpro.com support guidelines.

Cheers,
Andras

________________________
Internal Bug Ticket Reference:
BTRIA-1413