luceos hey thanks, i dont know technology, i just want to make sure if i updated the extension successfully and my flarum will work correctly.

    Something is wrong. I updated without any problems, cleared the cache. Previously the sitemap for my forum was here:
    https://pianoclack.com/forum/sitemap.xml

    However when I open this address I get redirected to another address where the sitemap is empty:
    https://pianoclack.com/forum/sitemap-live/index

    P.S. I rolled back already, so the first URL should be working OK because I'm on 1.0.2

    What is wrong? How can I uninstall and return to previous since this has the potential of messing the Google index.

      I hope this gets sorted quickly. I'm wondering if there's an easy way to downgrade though until that happens.

      OK, whoever needs to downgrade to the last known stable version:
      composer require fof/sitemap:1.0.2
      php flarum cache:clear

      clarkwinkelmann Added admin setting to exclude all user profiles from sitemap.

      This setting is missing!

      Solved:

      My bad I forgot to remove the below code from extend.php 😃 thanks for adding this feature to the extension.

      (new \FoF\Sitemap\Extend\RemoveResource(\FoF\Sitemap\Resources\User::class)),

          Hari This setting is missing!

          It will appear if you remove the custom setting in extend.php that was there for the old version 🙂 While I was testing the new version, I thought the setting was for the old version and commented it out in the extend.php then it appeared in the settings.

            If you would like to see it, I can upgrade again to 2.0.0 for you to check. I'm just afraid that I can mess up the Google search indexation... Basically, the sitemap.xml from the second (redirected) URL was a very short XML containing a few XML entities that contained something like live1, live2, live3... or maybe something similar, can't remember. I am on runtime mode. Is it possible that the problem is in my forum being installed under a sub-folder? I've noticed that extensions often have problems with such an installation.

              CyberGene Basically, the sitemap.xml from the second (redirected) URL was a very short XML containing a few XML entities that contained something like live1, live2, live3...

              Yeah that's what is supposed to happen 😉

                  luceos I will temporarily upgrade again to 2.0.0.0 but I don't have 50k discussion on my forum, I have 200 or something. There was something apparently wrong.

                    OK, I got it, all is good, apologies 🙂 Seems like the new sitemap is an index to other sitemaps, here's the actual result:

                    <sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://myforum.com/forum/sitemap-live/0</loc>
    <lastmod>2022-07-26T09:13:15+00:00</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://myforum.com/forum/sitemap-live/1</loc>
    <lastmod>2022-07-26T09:13:15+00:00</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://myforum.com/forum/sitemap-live/2</loc>
    <lastmod>2022-07-26T09:13:15+00:00</lastmod>
  </sitemap>
</sitemapindex>

                    The links to the sub-sitemaps work as expected.

                    Based on the replies, it seems the problems were fixed, but just to comment on what was discussed above.

                    CyberGene the sitemap is empty

                    If the file is completely blank, then there's likely a PHP error which might not be logged to the Flarum log file, but should be logged in the global system PHP error file (might be the Apache error file on Apache)

                    However if it contains 3-4 entries it's entirely normal. It's an index to the other files. Even if you have few records, everything is now always split like for large forums.

                    CyberGene something like live1, live2, live3

                    The /sitemap-live/<number> subfolder is basically a virtual folder that returns each file that would be created by the cached mode. As the "live" part indicates, they aren't actually cached when accessed that way but instead generated on the fly.

                    Hari This setting is missing! [...] forgot to remove the below code from extend.php

                    The setting and the line in extend.php achieve the exact same thing. Both are fully supported options.

                    The choice was made to hide the setting in the admin when the extender is used, otherwise it would be confusing on a shared hosting where the host made the choice to force that value for the client, since you can't re-enable a resource that was disabled from extend.php.

                          Im having a problem where google sitemap.xml, but not sitemap-live/2 and 0.
                          Is this normal or is it an issue?