Latest version gives error – Fatal error: Uncaught Exception: DateTimeZone::__co

  • Resolved Sancoale Technologies

    (@sancoale)


    2 years ago

    On activating the latest version, I get the following error –
    Fatal error: Uncaught Exception: DateTimeZone::__construct(): Unknown or bad timezone (+5.5) in /...../plugins/searchiq/library/plugin.php:2855 Stack trace: #0 /...../plugins/searchiq/library/plugin.php(2855): DateTimeZone->__construct('+5.5') #1 /...../plugins/searchiq/library/plugin.php(2794): siq_plugin->wp_strtotime('today 9:00pm') #2 /...../plugins/searchiq/library/plugin.php(392): siq_plugin->siq_start_delta_sync_cron() #3 /...../wp-includes/class-wp-hook.php(308): siq_plugin->siq_activate('') #4 /...../wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array) #5 /...../wp-includes/plugin.php(517): WP_Hook->do_action(Array) #6 /...../wp-admin/plugins.php(194): do_action('activate_search...') #7 {main} thrown in /...../plugins/searchiq/library/plugin.php on line 2855

    Note that root path has been replaced with /…../

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author SearchIQ

    (@searchiq)

    @sancoale This error is related to some changes in the PHP version 8.0 or greater. We will fix the issue in our next plugin release.

    For now, please go to Settings->General->Timezone and change the current timezone settings from this format UTC-5:30 or UTC+5:30 to a text-based setting like Los Angeles or New York or the timezone relevant to your location. This should fix the issue.
    Please check the screenshot for reference. https://prnt.sc/Nk3ns6ziG621

    Thread Starter Sancoale Technologies

    (@sancoale)

    Hi, thanks for the quick fix. That worked.

    Plugin Author SearchIQ

    (@searchiq)

    @sancoale Great to know. Please feel free to contact us if you have any questions.
    If you liked our plugin and support, please leave us a positive review. We will be grateful.

    Plugin Author SearchIQ

    (@searchiq)

    @sancoale We have released the fix for this issue. You can update the plugin to the latest version now.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Latest version gives error – Fatal error: Uncaught Exception: DateTimeZone::__co’ is closed to new replies.