Updating issues to 6.1.3

  • Hi,
    I currently run version 5.12.1 and updated to version 6.1.3. Now I experience a fatal error making my website unaccessible. All information I have is the following error log. Is there anybody, who could possibly help me interpreting that messages?

    Best
    Paul

    Ein Fehler vom Typ E_ERROR wurde in der Zeile 168 der Datei /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-content/plugins/events-manager/classes/em-booking.php verursacht. Fehlermeldung: Uncaught Error: Call to undefined method EM_Booking::generate_uuid() in /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-content/plugins/events-manager/classes/em-booking.php:168
Stack trace:
#0 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-content/plugins/events-manager/classes/em-bookings.php(636): EM_Booking->__construct()
#1 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-content/plugins/events-manager/classes/em-bookings.php(682): EM_Bookings::get(Array, true)
#2 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-content/plugins/events-manager/admin/em-admin.php(10): EM_Bookings::count(Array)
#3 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-includes/class-wp-hook.php(307): em_admin_menu('')
#4 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
#5 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-includes/plugin.php(476): WP_Hook->do_action(Array)
#6 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-admin/includes/menu.php(155): do_action('admin_menu', '')
#7 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-admin/menu.php(394): require_once('/www/htdocs/w01...')
#8 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-admin/admin.php(158): require('/www/htdocs/w01...')
#9 /www/htdocs/w015a317/staging.whisky-genuss-dresden.de/re.whisky-genuss-dresden.de/wp-admin/themes.php(10): require_once('/www/htdocs/w01...')
#10 {main}
 thrown
Viewing 4 replies - 1 through 4 (of 4 total)

  • Update Events Manager to 6.1.3 (all running PHP 8) lead to no problems on several sites here, so I assume a local problem.

    The method generate_uuid() is defined in em-object.php. Check if it there. If not, something went wrong obviously with your update.
    The file is located in wp-content/plugins/events-manager/classes/em-object.php.
    See Line 1740.

    Hi gulo92,

    I received the same issues with an automated upgrade from 6.1.1 to 6.1.3. It caused the entire website to fail and I had to roll back to a backup pre-update to get everything working again.

    I am unsure of the cause and don’t have time to investigate right now, so will look into it some other time.

    Perhaps you could try restore a backup first, then reapply the update and see how you go?

    Cheers

    Thread Starter gulo92

    (@gulo92)

    Well, I have already copied the entire website to a staging surrounding. There I have noticed the same error. So no idea for what reason it is caused. Let me know, when you have any news on that.
    Cheers

    Plugin Author Marcus

    (@msykes)

    Hello, I’d like to update this thread as someone refered me to it as an example. Sadly, we’ve experienced this issue due to the plugin Events Manager Email Users actually overwriting our own core code and using outdated files which cause this PHP error.

    This seems to be limited to the author’s Pro plugin, and possibly other add-ons he has written and has yet to correct it as far as we’re aware. Our only suggestion is to remove those plugins to prevent this error from happening. Overwriting other plugin core files is not OK and if it was a plugin hosted on www.ads-software.com it’d have been taken down unless corrected.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Updating issues to 6.1.3’ is closed to new replies.