a month later
16 days later

When this extension will have a site map "sharding" feature? When the index is greater than 5000, a new sitemap .xml file will be created.

    Hi, I had a problem. I installed the plugin and accidentally deleted the sitemap file. Now it does not appear again 🙁. I have reinstalled the plugin and it is still not generated. How can I get it again ?, I don't know how to generate a new sitemap.xml

    Thanks for your help.

      • [deleted]

      • Post #80

      LagunaLife The sitemap is generated on the fly - it doesn't exist as a file.

          2 months later

          [deleted] For some strange reason the sitemap still does not update automatically. More than a month ago I made a sitemap of my forum on the web www.xml-sitemaps.com, but of course I have to be generating it manually on the web if I want to see the new entries in the sitemap.

          I also tried uninstalling and reinstalling the extension but it didn't work either. What am I doing wrong?

          I appreciate all help.

              • [deleted]

              • Post #83

              LagunaLife Hmm. It should automatically populate. Did you create this by hand at any stage at all ? I don't seem to have this issue

                  [deleted] Simply install the extension manually, with the command:

                  composer require flagrow / sitemap

                  What happens is that later I accidentally deleted the file "sitemap.xml", and I waited a few days but it was not generated 🙁

                      • [deleted]

                      • Post #85
                      • Edited

                      LagunaLife Right. If you deleted the sitemap.xml file, then it must have been there to start with, so that could explain it. Can you disable the extension, check to ensure no sitemap.xml file exists in the root of flarum, then re-enable ?

                      Test by loading the sitemap.xml file directly in a browser, and see if this reflects the true posts in your forum.

                      To be clear, sitemap.xml is dynamically generated, and should never be created by hand as per https://discuss.flarum.org/d/14941-flagrow-sitemap/80

                        7 days later

                        0.3.0

                        • Support Flarum beta.13
                        • Moved from flagrow to FoF namespace
                        • Support for disk caching
                        • Support for multi-file sitemaps

                        Requires minimum flarum/core beta.12

                        Updating

                        composer require fof/sitemap
php flarum cache:clear

                        Thank you @luceos for your hard work on this

                          @clarkwinkelmann please remove composer require flagrow/sitemap and change by composer require fof/sitemap because I have broke my forum

                          @IanM I have this error

                          Flarum encountered a boot error (Error)
                          Class 'FoF\Sitemap\Providers\ResourceProvider' not found
                          thrown in /home/deje2074/forum.batocera.org/vendor/flarum/core/src/Foundation/Application.php on line 426

                            fakruzaruret nether494 please be patient. Because not every FriendsOfFlarum member is a moderator on this forum, they can't update the first post themselves. I have now copied the latest README from GitHub to the first post.

                            nether494 can you share the output of your php flarum info ?

                                  Hi, I love this extension, but I got one problem that I am facing. This does not add the "Pages" extensions's pages' links into the sitemap. :/

                                    dumi_dev it should. Make sure you have the fof/sitemap and the fof/pages extensions installed and not older non-FriendsOfFlarum versions.

                                    If it still doesn't work, can you share your php flarum info output ?

                                    EDIT: after investigation it turns out it was indeed not working. See post below with update.