• I had to revert from 3.0 to using version 2.0.11 because two things stopped working:

    1. Trying to sort my events by start_date DESC wasn’t working (I had entry 6, then 7, then 5, instead of 7, then 6, then 5).
    2. tribe_get_start_date was showing today’s date instead of the start date on the event.

    Reverting back to 2.0.11 fixed both these issues.

Viewing 1 replies (of 1 total)
  • Hey cheshire137. Rob from Modern Tribe here; I wanted to reply to your review to both thank you for taking the time to write it, and to apologize on behalf of the poor experience you faced.

    I’m hoping that these issues you reported here – the latter of which I’m quite sure we’ve already patched in a subsequent dot-release – will be worked out in the coming weeks. Whenever a major new lifecycle of a product begins, there are bound to be bugs and we appreciate anyone who both adopted early + reported what they saw. You should know that we’re focusing the next few weeks on a large, bug-centric release that should be out as soon as it’s fully QA’d, and will address a number of the integration issues we didn’t account for in our pre-release testing.

    Similarly, because I want to try and make up for the inconvenience: if when you do revisit the plugin you’d be interested in using the PRO release, I’d be happy to offer you a free license (as well as the deeper level of support that accompanies it) if you were game. Email me (rob /a/ tri.be) referencing this if so and I’ll get you what you need.

    Otherwise, thanks again for your patience and support on this. If we can help as you continue using 2.0.11, let us know – and if you eventually find yourself willing to apply the upgrade and find it better meets your needs, I’m hoping we can bring you back into the fold and improve our review in your eyes from there. Thanks again for your support.

Viewing 1 replies (of 1 total)
  • The topic ‘I don't recommend upgrading’ is closed to new replies.