Split by options to None // Issue

  • Resolved Sanjay

    (@rsclmumbai)


    5 years, 11 months ago

    WordPress 5.1.1
    —————
    I’m getting the following notification in the admin section:

    A setting in the WordPress SEO plugin causes all date based sitemaps to redirect to the main page. Please either enable Date archives under Archives in your SEO settings or set all Split by options to None under Included post types in your XML Sitemap settings.

    ————
    Date archives is disabled in Yoast & I would like to keep it that way.

    Split by options to already set to None.
    See screenshot https://www.awesomescreenshot.com/image/3958235/119eea0c4fafcfd5207d02c2e9450272

    How do I fix this warning??

    Thanks

    The page I need help with: [log in to see the link]

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

  • Hi, thanks for reporting. We’ll look into it for the next release.

    Meanwhile, have you tried the Dismiss button?

    Thread Starter Sanjay

    (@rsclmumbai)

    Yes, Dismiss button does not remove the notification. It just closes and reappears

    OK, that is not supposed to happen. Will try to reproduce this and work on a fix…

    I’ve identified the issue with the dismiss button. It will be fixed in the upcoming release.

    However, I cannot reproduce the issue where the warning still appears even when the Split by option is set to None.

    Could you try switching the Split by option to Year or Month, then save and then switch back to None and save again?

    Thread Starter Sanjay

    (@rsclmumbai)

    Tried as you asked. No joy ??

    https://www.awesomescreenshot.com/image/3958449/109501750962ae28bb9a165b4638b567
    https://www.awesomescreenshot.com/image/3958450/c886dc0a42ca900f34a8c623bf137b16

    Do you have any other post types on that page except Posts and Pages?

    Thread Starter Sanjay

    (@rsclmumbai)

    Yes, a few more, but those are unchecked.
    See screenshot https://www.awesomescreenshot.com/image/3958927/fc6d4640156a8f06df80bf0281a15388

    OK it makes more sense, and I was able to reproduce the bug now. It will be fixed in the next release, thanks again for reporting ??

    To work around it for now, just set that last post type to None too even though it is not included. This should get rid of the warning message.

    Thread Starter Sanjay

    (@rsclmumbai)

    Yes, that worked!!
    Thanks for your prompt support. Looking forward to the update.

    Meanwhile, I just discovered another issue.
    For unknown reasons, Google is reporting 404 for one of the sitemaps. The same URL is accessible via browser and via external http-status tools.
    https://www.awesomescreenshot.com/image/3959001/7b73687edb90482908782ba22dbcfebf
    https://www.awesomescreenshot.com/image/3959003/4359af0832f5434b502bf367a63d6818

    I’ve been scratching my head bald but no luck.
    If possible, please have a look.

    Thanks

    Thread Starter Sanjay

    (@rsclmumbai)

    2019/04/05 22:03:42 [error] 24896#0: *70035 FastCGI sent in stderr: "nx/html/wp-content/plugins/xml-sitemap-feed/models/public/sitemap.php on line 304
PHP message: PHP Warning:  Division by zero in /usr/share/nginx/html/wp-content/plugins/xml-sitemap-feed/models/public/sitemap.php on line 304
PHP message: PHP Warning:  Division by zero in /usr/share/nginx/html/wp-content/plugins/xml-sitemap-feed/models/public/sitemap.php on line 304
PHP message: PHP Warning:  Division by zero in /usr/share/nginx/html/wp-content/plugins/xml-sitemap-feed/models/public/sitemap.php on line 304
PHP message: PHP Warning:  Division by zero in /usr/share/nginx/html/wp-content/plugins/xml-sitemap-feed/models/public/sitemap.php on line 304
PHP message: PHP Warning:  Division by zero in /usr/share/nginx/html/wp-content/plugins/xml-sitemap-feed/models/public/sitemap.php on line 304
PHP message: PHP Warning:  Division by zero in /usr/share/nginx/html/wp-content/plugins/xml-sitemap-feed/models/public/sitemap.php on line 304

    Checked your posts sitemap from here and it is accessible (not the stylesheet though, because it is forced to be loaded from cloudfront which is another domain so blocked by the browser) so there should be no reason for Google to get a 404. Maybe a temporary fluke? Google will revisit again in a little while but you could try to use the Ping Search Engines button on Settings > XML Sitemap (right side in the Tools section) to tempt it to come sooner…

    Thanks for the PHP notices, I’ll try and find out when these divisions by zero might occur.

    Thread Starter Sanjay

    (@rsclmumbai)

    404 issue is automatically resolved.
    Thanks

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Split by options to None // Issue’ is closed to new replies.