Fatal errors with 2.1.0, Developers not tagging releases

  • Resolved Joshua Goode

    (@verygoode)


    2 years, 7 months ago

    Hi there!

    While checking in on some client and test sites, we discovered various fatal errors coming from the latest wp-travel-blocks 2.1.0 update.

    Here’s a truncated stack trace.

    Fatal error: Uncaught Error: Call to undefined function wptravel_get_settings() in /srv/htdocs/wp-content/plugins/wp-travel-blocks/wp-travel-blocks.php:93
Stack trace:
#0 /wordpress/core/5.8.2/wp-includes/class-wp-hook.php(303): WPTravel_Blocks->wptravel_blocks_loader('')
#1 /wordpress/core/5.8.2/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array)
#2 /wordpress/core/5.8.2/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
#3 /wordpress/core/5.8.2/wp-settings.php(441): do_action('plugins_loaded')
#11 {main}
  thrown in /srv/htdocs/wp-content/plugins/wp-travel-blocks/wp-travel-blocks.php on line 93

    #### Release Tags

    Additionally, we noticed that the plugin is not using SVN release tagging properly.

    This means that there are no previous versions available via the WordPress.org repo which would normally be accessible via WP-CLI or https://wordpress.org/plugins/wp-travel-blocks/advanced/

    It appears previous tags have been deleted.

    For more on this please see https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/#tags and check examples of proper tagging such as Yoast’s https://plugins.trac.wordpress.org/browser/wordpress-seo/tags

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Joshua Goode

    (@verygoode)

    2 years, 7 months ago

    Looking further, it appears that wp-travel had been deactivated in some situations. This is what led to the fatal.

    That’s somewhat expected but perhaps that can be handled better so that the site doesn’t crash when wp-travel isn’t present.

    wptravelsupport

    (@wptravelsupport)

    2 years, 7 months ago

    Hello,

    We would like to apologize for trouble you are facing.

    Regarding fatal error you have reported, we will fix the issue in our side and release the update but we would like to inform you that you need to activate WP Travel plugin to use WP Travel Blocks plugin.

    If you have any queries further, please let us know.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal errors with 2.1.0, Developers not tagging releases’ is closed to new replies.