Support » Plugin: The Events Calendar » Switching to New Theme – Permalink Generation

  • So old style I haven’t had this issue. Keep in mind this site is running WPML and 3 languages.

    But we are trying to update the style of the calendar to the new one and have run into nothing but issues. In a development environment I tried deactivating everything and reactivating and ran into this error message when attempting to reactivate PRO.

    Uncaught TypeError: Argument 1 passed to Tribe__Rewrite::remove_percent_placeholders() must be of the type array, bool given, called in /code/wp-includes/class-wp-hook.php on line 303 and defined in /code/wp-content/plugins/the-events-calendar/common/src/Tribe/Rewrite.php:177
    Stack trace:
    #0 /code/wp-includes/class-wp-hook.php(303): Tribe__Rewrite->remove_percent_placeholders(false)
    #1 /code/wp-includes/plugin.php(189): WP_Hook->apply_filters(false, Array)
    #2 /code/wp-includes/class-wp-rewrite.php(1462): apply_filters('rewrite_rules_a...', Array)
    #3 /code/wp-includes/class-wp-rewrite.php(1483): WP_Rewrite->rewrite_rules()
    #4 /code/wp-content/plugins/the-events-calendar/common/src/Tribe/Rewrite.php(900): WP_Rewrite->wp_rewrite_rules()
    #5 /code/wp-content/plugins/the-events-calendar/src/Tribe/Rewrite.php(618): Tribe__Rewrite->parse_request('/wp-admin/edit....', Array, false)
    #6 /code/wp-content/plugins/the-events-calendar/common/src/Tribe/Rewrite.php(1094): Tribe__Events__Rewrite->parse_wp-content/plugins/the-events-calendar/common/src/Tribe/Rewrite.php:177

    So I had to temporarily change the Rewrite.php function at line 177 to get it so I could get it to work at least a little bit. I put it back in the attempt to let the system work as it should.

    I had to do a wp-cli rewrite flush in order to get rid of a lot of the /(/?:list)/ permalink issues as doing a Settings Permalinks save did not do anything useful. I shouldn’t have to do the rewrite flush via the cli to get it to function even just this little bit.

    So there are times that it doesn’t completely change all of the (/?:instances) correctly, be it page|pagina. So while pagination on the Month view works, pagination on the list view works for spanish, while i was able to get french and english (default language) working fine.

    Also with this new update, we have the filters addon and its still showing the advertisement instead of allowing me to save anything on the filters tab. Checked the licensed tab and everything is green there.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter WP CMS Ninja

    (@billiardgreg)

    Sorry, meant to say pagination for list view doesn’t work on one of the languages. Just strange how inconsistent the permalinks are with this new calendar style.

    arcamedia

    (@arcamedia)

    I am having the same if not similar issue with my install of WPML and ECP. Even saw the filter bar issue until they fixed it in the last update (phew). When we switch to legacy view all is working for us when we do new style it has the permalink issue you are seeing and also even after flushing all caches and permalinks it starts working for a bit and then fails. Fails very quickly. We have reverted our site back to legacy view until Events or WPML fixes the issue. I think its Events plugin not WPML because switching views fixes issues completely. It has something to do with when switching to new so must be something in how they are sending string translations in language. Its important to note that our site works in english and it fails in language. It does not run perfectly in english but close to it. Hoping there is some fix for this soon. Did you find some work-around until there is?

    Plugin Support Jaime

    (@jaimemarchwinski)

    Hi @arcamedia @billiardgreg

    I’m so sorry to hear that you are experiencing this issue. We are aware of this issue and are working on a fix for it. We will notify you in this thread when a fix has become available.

    In the meantime, keep the user profile language as the site default or set it to the same as the site.

    For WPML, you should use the site default language.

    I hope that helps!

    Thanks,
    Jaime

    Ref: 3733

    Hi @jaimemarchwinski – any idea when a fix might be available? The work around you suggested does not seem to have any effect on our issue. I understand all too well that with development it’s never easy, but even a rough estimate would be appreciated as our clients keep asking. We would be very indebted if you could just give a rough target date so I can update/quell them. Thanks!

    Plugin Support Jaime

    (@jaimemarchwinski)

    Hi @arcamedia

    Unfortunately, we don’t have an ETA available at this time for this bug fix.

    I apologize for the inconvenience but we appreciate your patience and understanding!

    Thanks,
    Jaime

    Hi @jaimemarchwinski just checking in if any update on status? I assume there is no concern of you guys disabling legacy in an upcoming release b4 there is a fix in place?

    Plugin Support Jaime

    (@jaimemarchwinski)

    Hi @arcamedia

    Unfortunately, I don’t have an ETA on when this bug will be fixed. It looks like our developers haven’t yet put in an estimate, but I will update you when I have more information.

    Thanks for your understanding!

    Jaime

    @jaimemarchwinski sorry but I gotta ask….so they(developers) do acknowledge its in their court to fix this? right?…Not something we can do on our end besides your suggestions at beginning of this thread. I see @billiardgreg seemed to see the root cause or at least where issue lies in code. But would love to hear it from you (as in your developers). Just need to help the client to keep waiting they are not as easy going as me 🙁 lol thank you Jaime!

    Plugin Support Jaime

    (@jaimemarchwinski)

    Hi @arcamedia

    I totally understand your predicament. Our developers definitely understand that this is a bug and are aware that a fix is needed. Unfortunately, they haven’t yet begun work on this issue because there are some other high-priority bug fixes needed in the queue.

    I assure you that we are aware of this issue on our end and will work on a fix for it as soon as the time allows. Thank you for your continued patience and understanding in this process.

    Thanks,
    Jaime

    Hi @jaimemarchwinski, any update? thank you for checking for us

    • This reply was modified 2 months, 3 weeks ago by arcamedia.
    Plugin Support Abz

    (@abzlevelup)

    Hi @arcamedia,

    Thanks for following up here. I checked the status of the bug ticket here. Our team is still working on a fix for this one.

    Moreover, you could keep an eye on our changelogs for the following tracking code: TEC-3733 when we release future updates.

    Sorry for the inconvenience. Appreciate your time and patience here.

    Best,
    Abz

    arcamedia

    (@arcamedia)

    Hi @abzlevelup 3 weeks in and still no TEC-3733 showing in changelog. We are really needing this fix implemented. We are paying customers and experiencing the issue on 3 of our sites (granted they are all a similar setup with WPML) and keeping all 3 clients in wait for a long while now (literally over two months). one of the clients has even asked us to consider another event plugin which we would prefer to avoid greatly. Any eta yet so we can have a goal? any work around that is reasonable to get it to work (though I think we spent over 20 hours trying to solve it already to no avail)? You guys are doing events on tens of our clients sites and have always been awesome for both support and updates. But this is not the TEC response we are used to. Please help us to get things back on track soon…I am praying 😉

    Thanks

    A 🙂

    Plugin Support Abz

    (@abzlevelup)

    Hi @arcamedia,

    Thank you so much, for the follow-up here. I’m really sorry, first, and foremost, that we’re having this delay and I really understand your frustration. I already notified our team in regard to this.

    We are not happy with this glitch at all either, but until 6.0 is out, we can’t refactor the code to address this issue. This issue is tricky and there’s a lot to consider — refactoring the current code will need to go to a complete dev cycle to make sure that’s solid and stable. We do not have a workaround available for this one as well.

    That being said, I know this answer is not satisfactory to you at the moment, and we would understand if you would consider another plugin. But I do think it is better to be honest of the current situation and what our development roadmaps and prioritization are.

    Lastly, we really do not have a precise date just yet, but this is at the very top of our list. I also know that this is not the TEC response you are used to, but we’ll keep pushing through.

    I really appreciate your time and patience. Apologies for the inconvenience.

    Best,
    Abz

    ________________________
    Internal Bug Ticket Reference:
    TEC-3733

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.