• Resolved wideep

    (@wideep)


    Since the last update of print-my-blog (PMB), Yoast SEO generates an own XML-sitemap for PMB: pmb_content-sitemap.xml. This file is listed on the main sitemap: https://wider-deeper.blog/sitemap_index.xml

    The pmb_content-sitemap.xml links to a directory /pmb which leads to a 404 error when accessed.

    What is the directory /pmb used for and is there a need to have it listed on the sitemap? Can I disable it? Currently, Google search reports this as an error because a non-existent file is announced.

    Best
    Martin

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Michael Nelson

    (@mnelson4)

    Hi @wideep, nice to meet you. Thank you for reporting the issue.

    Print My Blog now adds its own custom post type (“Print Materials”, or “pmb_content”) which is mostly intended to be private, but it seems Yoast SEO didn’t get the memo about that. So I needed to add a bit of code to tell Yoast SEO to not put it in the sitemap index.

    I have a fix ready to go. Would you like to test it before I release to everyone?

    If so, here’s how:

    1. Download the new version from here: https://github.com/mnelson4/printmyblog/archive/refs/heads/BUG/pro-code-in-wporg-version.zip
    2. Go to your WordPress dashboard, click plugins, then “add new”, then “upload” and select the zip file you just downloaded
    3. Deactivate the previous version Print My Blog
    4. Activate the new version of Print My Blog

    You might need to refresh permalinks or refresh Yoast SEO’s settings, too.

    But after that, “pmb_content-sitemap.xml” shouldn’t appear on the sitemap index.

    Is that working for you? No worries if you’d rather not test it first, you’ve already been very helpful with you detailed bug report.

    Thread Starter wideep

    (@wideep)

    Thanks very much! The fixed version did it!

    I tested it and a simple reload on the sitemap made the pmb_content-sitemap.xml disappear. The printing functionality works still fine.

    Can I keep the custom plugin version activated? What happens when the official 3.3.1 comes out? Will future updates work?

    Best,
    Martin

    Plugin Author Michael Nelson

    (@mnelson4)

    Hi @wideep, thanks for testing and confirming it fixed the issue for you.

    Yes once 3.3.1 comes out you’ll want to update. I’m sorry I don’t recall if that will happen automatically or not. I’ll ping you in this thread once it’s released so you can double-check it got updated automatically.

    Plugin Author Michael Nelson

    (@mnelson4)

    Hi @wideep 3.3.1 was released.

    I just checked if auto-updates work when you’re using the version I sent you. They do, but the version I sent you *erroneously* asks you to pay to upgrade (it thinks you bought it, so are a paying customer).

    Just delete the version I sent you (3.3.1) and activate the old version (3.3.0).

    Then you’ll update as normal.

    If you already deleted the old version, no worries: still delete the new version, and go to WordPress’ admin dashboard, then “Plugins”, then “Add New” and search for “Print My Blog” and install and activate it. That will be the newest, regular version, and it will continue to receive automatic updates as normal.

    Does that make sense?

    Thread Starter wideep

    (@wideep)

    Perfect. Thanks!

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