Support » Plugin: XML Sitemaps » PHP Fatal error:

  • Resolved persiantech

    (@persiantech)


    [08-Jun-2022 13:55:32 UTC] PHP Fatal error: Uncaught TypeError: Unsupported operand types: int * string in /home/*****/public_html/wp-content/plugins/google-sitemap-generator/class-googlesitemapgeneratorstandardbuilder.php:507
    Stack trace:
    #0 /home/*****/public_html/wp-content/plugins/google-sitemap-generator/class-googlesitemapgeneratorstandardbuilder.php(44): GoogleSitemapGeneratorStandardBuilder->build_taxonomies()
    #1 /home/*****/public_html/wp-includes/class-wp-hook.php(307): GoogleSitemapGeneratorStandardBuilder->content()
    #2 /home/*****/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
    #3 /home/*****/public_html/wp-includes/plugin.php(476): WP_Hook->do_action()
    #4 /home/*****/public_html/wp-content/plugins/google-sitemap-generator/sitemap-core.php(1961): do_action()
    #5 /home/*****/public_html/wp-content/plugins/google-sitemap-generator/class-googlesitemapgeneratorloader.php(387): GoogleSitemapGenerator->show_sitemap()
    #6 /home/*****/public_html/wp-content/plugins/google-sitemap-generator/class-googlesitemapgeneratorloader.php(250): GoogleSitemapGeneratorLoader::call_show_sitemap()
    #7 /home/*****/public_html/wp-includes/class-wp-hook.php(305): GoogleSitemapGeneratorLoader::do_template_redirect()
    #8 /home/*****/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
    #9 /home/*****/public_html/wp-includes/plugin.php(476): WP_Hook->do_action()
    #10 /home/*****/public_html/wp-includes/template-loader.php(13): do_action()
    #11 /home/*****/public_html/wp-blog-header.php(19): require_once(‘/home/*****/…’)
    #12 /home/*****/public_html/index.php(17): require(‘/home/*****/…’)
    #13 {main}
    thrown in /home/*****/public_html/wp-content/plugins/google-sitemap-generator/class-googlesitemapgeneratorstandardbuilder.php on line 507

Viewing 5 replies - 1 through 5 (of 5 total)
  • Kimberly

    (@amiga500)

    Yea i too reported this error last week. The author forgot to set the offset variable to 0 when there is no numerical value to parse out.

    Sadly, he didnt correct it in the latest release (came out a few days ago) so hopefully he will finally take notice of this error now that we’ve both reported it.

    For now i just manually fixed his bug since it was creating a massive error_log file over time.

    If he doesnt correct it in the next release, then, due to the other recent bugs being reported, i will likely downgrade back to the more stable older version. That or just apply my own php fixes for all the new bugs since they are all quick & easy to fix.

    Plugin Author Auctollo

    (@auctollo)

    Thanks for raising the issue, everyone. This issue was already reported and tracked on version 4.1.4. We are also going to release the 4.1.5, now generally available. Please upgrade as soon as possible and let us know if problems persist.

    itsgotime

    (@itsgotime)

    You mentioned that 4.1.5 was now available but I just checked and the latest is still 4.1.4…

    Plugin Author Auctollo

    (@auctollo)

    Yea, my connection is quite slow. It’s finally committed.

    LX T

    (@lxt)

    4.1.5 does not fix the problem for me.

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