Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter kazimieras

    (@kazimieras)

    The issue I think was from the begining. Just, we noticed it recently because of the google saerch console notice (error). So it is difficult to exaclty know actions which are the cause of this problem.
    We also opened topic at yoast plugin page but we have got the answer to check for problems at Your side.
    https://www.ads-software.com/support/topic/wrong-last-modified-date-of-sitemap/#post-16054587

    Thread Starter kazimieras

    (@kazimieras)

    Yes we have updated filter settings and the urls (of the sitemap) dates (Last Mod.) also channges. But the xml’s (filter_seo_rule-sitemap.xml) date remains the same (wrong).
    We tryed to disable sitemap feature, clear cache and enable sitemaps again. But result is the same.

    Thread Starter kazimieras

    (@kazimieras)

    Thanks for Your reply. We use free version of Yoast plugin and apparently it has a bug described above.

    Thread Starter kazimieras

    (@kazimieras)

    yes, problem still persist. You need to check here: https://dresslemuse.com/sitemap_index.xml/
    You will see wrong last modified date of the filter_seo_rule-sitemap.xml file.

    Thread Starter kazimieras

    (@kazimieras)

    Also I should mension that the same errors apears in both languages (en or lt).

    Thread Starter kazimieras

    (@kazimieras)

    Hallo,
    Thank You very much for the reply!
    I checked on more time: after disabling all the WPML plugins (leaving one default EN language) the errors disapears from the frontend.

    I checked again for errors then the WPML plugins are enabled.
    1. pressing the button “add to cart” from a product page:
    Number comparator expects numeric values to be compared, value ” of type ‘string’ given.

    2.pressing “view cart” button:

    Cart
    
    Fatal error: Uncaught InvalidArgumentException: Number comparator expects numeric values to be compared, value '' of type 'string' given. in /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/NumberComparator.php:52 Stack trace: #0 /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/NumberComparator.php(43): WbsVendors\Dgm\Comparator\NumberComparator->normalize() #1 /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/AbstractComparator.php(26): WbsVendors\Dgm\Comparator\NumberComparator->cmp() #2 /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/AbstractComparator.php(16): WbsVendors\Dgm\Comparator\AbstractComparator-> in /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/NumberComparator.php on line 52
    
    There has been a critical error on this website.
    
    Learn more about debugging in WordPress.

    3. Pressing “check out” button:

    Checkout
    
    Fatal error: Uncaught InvalidArgumentException: Number comparator expects numeric values to be compared, value '' of type 'string' given. in /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/NumberComparator.php:52 Stack trace: #0 /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/NumberComparator.php(43): WbsVendors\Dgm\Comparator\NumberComparator->normalize() #1 /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/AbstractComparator.php(26): WbsVendors\Dgm\Comparator\NumberComparator->cmp() #2 /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/AbstractComparator.php(16): WbsVendors\Dgm\Comparator\AbstractComparator-> in /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/NumberComparator.php on line 52
    
    There has been a critical error on this website.
    
    Learn more about debugging in WordPress.

    4. Then removing product pressing x button in the cart widget:

    Fatal error: Uncaught InvalidArgumentException: Number comparator expects numeric values to be compared, value '' of type 'string' given. in /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/NumberComparator.php:52 Stack trace: #0 /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/NumberComparator.php(43): WbsVendors\Dgm\Comparator\NumberComparator->normalize() #1 /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/AbstractComparator.php(26): WbsVendors\Dgm\Comparator\NumberComparator->cmp() #2 /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/AbstractComparator.php(16): WbsVendors\Dgm\Comparator\AbstractComparator-> in /home/leselt/domains/dresslemuse.com/public_html/staging/wp-content/plugins/weight-based-shipping-for-woocommerce/server/vendor/dangoodman/comparator/src/NumberComparator.php on line 52
    
    There has been a critical error on this website.
    
    Learn more about debugging in WordPress.
    Thread Starter kazimieras

    (@kazimieras)

    Thanks for the new plugin update! I tried new version 1.6.2, but unfortunately it seems that the problem is the same: the feed generation process was stopped at the same place as before.
    Please, inform me, how can I help to give You some additional information about this case (configuration, logs, etc.). I will definitely try to help You ASAP.

    Thread Starter kazimieras

    (@kazimieras)

    Hi,
    Thanks for fast reply and new update!
    I’d tried new version of plugin but the result is almost the same. After saving new feed configuration it stated status as ready. But after looking at xml file it revealed that feed generation was stoped at the same products as before. Then I manually refreshed product feed and it started endless “processing” status again.
    P.S. I send new debug information to You by e-mail.

    Best regards

    Kazimieras

Viewing 8 replies - 1 through 8 (of 8 total)