15Teds Not much you can do to fix it, unfortunately. A fix is in the works by a member of fof, but there's no expected date for it to arrive. I apologize :/.

    a month later

    Edit: nevermind, i see why, merge new posts to older large posts (things we would likt to do sometimes) will fail at the moment.... hopefully there will be a fix soon.

    today i have installed this everything works fine 😄 many thanks to flarum family

    9 days later

    how to redirect merged old urls to new urls ?

    if https://www.website.com/d/21 merged into https://www.website.com/d/85

    old 21 url should get redirected to 85

    if /d/85 merged into /d/21

    /d/21 should get redirected to /d/85

    please consider adding this feature . its very important factor need to be considered in SEO

    https://wordpress.org/plugins/redirection/

    https://github.com/johngodley/redirection

    https://discuss.flarum.org/d/23787-managing-url-redirections-404-301

      Hari It's not possible right now. It's probably a good idea though.

        25 days later

        Merge Discussions - Failed to merge discussions.

        {"errors":[{"status":"422","code":"validation_error","detail":"Failed to merge discussions.","source":{"pointer":"\/data\/attributes\/fof\/merge-discussions"}}]}

        Console : /api/discussions/431/merge 422 https://www.domain/ask/assets/forum-0bdbe762.js

        https://i.imgur.com/5dKLtZo.png

          datitisev

          FriendsOfFlarum/merge-discussions9
          imorland commented: By adding an additional sort on the discussion first, setting the number out of the current range, then continuing with the merge, everything works again 😄

          should I need to add a few more posts? then need to merge?

              Hari No, that's not what that means. The code that was added was to avoid two posts having the same number (not allowed in DB because the column must be unique) by making them extremely big and then sorting back down to normal. You can't fix the issue yourself.

                next time i will not delete or split posts. lets hope for a bug fix . fingers crossed

                Edited :

                ok i have tried to merge d-437 & d-438 to d-431

                whenever I try to do this I got an error. then i merged d-431 to d-437 it worked, next i merged d-438 to d-437 .

                renamed d-437 as d-431 luckily all posts are posted on time-based. - this resolved my issue temporarily.

                  Hari basically you can't merge newer discussion into the older one. And it's really annoying, because 95% of merging is splitting some posts from one topic and merge them into another. But now you need to merge your big old topic into splitted couple of posts and then rename it, Sometimes after that some topics stop being highlighted when there are new posts. So I'm waiting for that bug fix too.

                    Hello everyone, unable to merge discussions is a big issue like mentioned by goofy and others, all the time we can not pull all old discussion to new threads.

                    I request FOF to fix this. I would like to contribute $20 USD towards it. (I respect the efforts, at the same time others who are getting benefited by this plugin I request them to contribute for the same)

                    please bring these features :

                    if a discussion is deleted. reserve space for that discussion and mention in the same page as post is deleted.
                    if a discussion is moved. reserve a page mentioning newly moved discussion link
                    if a discussion is merged. reserve a page mentioning newly merged discussion link

                    i do not know this is a perfect solution or not, but I think this is an easy way to avoid surprising flarum core.

                    in addition, creating a new rule / new extension: it should search for all flarum discussion numbers d/1 or d/3 .. to latest discussion numbers. where the new extension will create empty pages mentioning "this page is not available" and those newly created discussions to fill gaps will be automatically flagged and will not displayed to the public.
                    so our FoF merge plugin will not show errors I guess

                      13 days later

                      Hari if a discussion is deleted. reserve space for that discussion and mention in the same page as post is deleted.
                      if a discussion is moved. reserve a page mentioning newly moved discussion link
                      if a discussion is merged. reserve a page mentioning newly merged discussion link

                      we need these features ... PLEASE

                          Hari

                          if a discussion is deleted. reserve space for that discussion and mention in the same page as post is deleted.
                          if a discussion is moved. reserve a page mentioning newly moved discussion link

                          These don't seem to be in the scope of this extension?

                          if a discussion is merged. reserve a page mentioning newly merged discussion link

                          This could be done.

                          in addition, creating a new rule / new extension: it should search for all flarum discussion numbers d/1 or d/3 .. to latest discussion numbers. where the new extension will create empty pages mentioning "this page is not available" and those newly created discussions to fill gaps will be automatically flagged and will not displayed to the public.
                          so our FoF merge plugin will not show errors I guess

                          I'm not sure what you mean by this.

                              datitisev if a discussion is merged. reserve a page mentioning newly merged discussion link

                              This could be done.

                              Personally, I've long thought that at least a redirect being in place, but a view showing where to find the merged content would be good too..

                                  IanM Yeah, I'm more in favor of a redirect as well. That's probably how I would implement it.

                                    datitisev in addition, creating a new rule / new extension: it should search for all flarum discussion numbers d/1 or d/3 .. to latest discussion numbers. where the new extension will create empty pages mentioning "this page is not available" and those newly created discussions to fill gaps will be automatically flagged and will not displayed to the public.
                                    so our FoF merge plugin will not show errors I guess

                                    now the issue is occurring due to the empty gap between discussion numbers right?

                                    as we are deleting or moving pages it's creating empty space in discussion

                                    numbers and merge extension could not handle it. so I am asking to run a corn job or something to create dummy pages to fill empty discussion numbers.

                                    datitisev These don't seem to be in the scope of this extension?

                                    when merge discussions extension is creating gap between posts .. it should leave a note in the old pages. and old deleted or / moved page should not be visible in forum timeline. these deleted pages should be visible to for those who have direct link access. (like spiders, search engines)

                                          Hari I think you misunderstood what the issue relating to numbers is. It is not about discussion IDs, but about the post numbering in a discussion (post #1, post #2, etc... in discussion x).

                                            Whenever a discussion is completely merged into another discussion, we should redirect requests to the discussion that no longer holds posts to the one that the posts were merged into. Personally, it seems to me to make the most sense.

                                              5 days later