Niklas Johansson

Hi,

Thanks for replying back. Which information do you need?
I cannot attach pictures unfortunately, but the error message above is available both in the Settings panel and in emails to client.

Just to test, I reset to theme Twenty Twenty-One and disabled all plugins except Woocommerce and WooCommerce Checkout & Account Field Editor, but the issue still persisted. Running version 1.2.4 and version 4.8.0 of WooCommerce.

Downloading and updating the Event Tickets Pro plugin manually solves this issue. You can find the update on your account page: https://theeventscalendar.com/my-account/downloads/

If your update window has expired, you are out of luck (the plugin author should add in a check for this!).

Hi! Thanks for the update! However, this update crashes the site with an undefined function being called if you have latest event tickets plus installed.

Fatal error: Uncaught Error: Call to undefined function tribe_tickets_new_views_is_enabled()
public_html/wp-content/plugins/event-tickets-plus/src/Tribe/Assets.php on line 42

Same here, it completely crashed my site and took me a long time to get access to my site again. Had to go through both PHPAdmin and ftp! Impressive how this can be let through. Thanks @robert1776 for the quick fix, but I would expect support to fix this asap.

Pasting the full error message below:
Fatal error: Uncaught Error: Call to undefined function tribe_tickets_new_views_is_enabled() in /home/customer/www/lustfyllt-torslanda.se/public_html/wp-content/plugins/event-tickets-plus/src/Tribe/Assets.php:42 Stack trace: #0 /home/customer/www/lustfyllt-torslanda.se/public_html/wp-content/plugins/event-tickets-plus/src/Tribe/Service_Provider.php(76): Tribe__Tickets_Plus__Assets->enqueue_scripts() #1 /home/customer/www/lustfyllt-torslanda.se/public_html/wp-content/plugins/event-tickets-plus/src/Tribe/Service_Provider.php(54): Tribe__Tickets_Plus__Service_Provider->hook() #2 /home/customer/www/lustfyllt-torslanda.se/public_html/wp-content/plugins/the-events-calendar/common/vendor/lucatume/di52/src/tad/DI52/Container.php(480): Tribe__Tickets_Plus__Service_Provider->register() #3 /home/customer/www/lustfyllt-torslanda.se/public_html/wp-content/plugins/the-events-calendar/common/src/Tribe/Container.php(288): tad_DI52_Container->register('Tribe__Tickets_...') #4 <strong>/home/customer/www/lustfyllt-torslanda.se/public_html/wp-conten in /home/customer/www/lustfyllt-torslanda.se/public_html/wp-content/plugins/event-tickets-plus/src/Tribe/Assets.php on line 42</strong>

• This reply was modified 4 years, 4 months ago by Niklas Johansson.

This issue is not solved, just given an explanation. I had the same issue and now have to manually update hundreds of posts.

At the very minimum there should be a check to notify users of potential loss, and to fix it character encoding should be respected. ? ? ? are all available in utf-8 so that shouldn’t be an issue.

Hi Judge.me,

I have exactly the same error. I sent a support email with a screenshot for further help. The plugin is currently inactivated on the site, but let me know if you need it to be active to perform an analysis.

Kind Regards,
Niklas

Hi,

I think I have the same issue. I have installed the plugin from the WordPress plugin catalog but find no way to sign up and register my domain for the first time on your server.

Am I missing something? How do I connect my site to your system?

Thank you a lot! A great plugin and a quick and good answer.

Keep it up! ??

An update to my previous post.

It does work in compatibility mode. I found a conflicting shortcode in my theme that caused it to fail.

Great plugin, great work!

Does this work in compatibility mode?

I didn’t manage to get it right, but I might miss something. What I use is:

[su_spoiler title="Parent"]
      Parent Content
      [_su_spoiler title="Nested spoiler"] Nested spoiler [_/su_spoiler]
      [_su_spoiler title="Nested spoiler"] Nested spoiler [_/su_spoiler]
[/su_spoiler]

This is the live version:
https://juridikibutik.se/niklas-work-page/.

I’ve removed the posts on the front page and replaced them with normal pictures instead and thus eliminated the problem. Mark this as resolved. If someone else has the problem, please feel free to pick it up again.