Is it possible (through e.g. CSS only?) to show the final "move posts" button on mobile (iPhone in my case) to always appear on the screen when I start selecting posts for move? Currently that button is visible only if I scroll to the top of the discussion, which means for large discussions I have to use the post scroller to go to the "original post" which is pretty awkward and took me quite some time to figure out.

  • Hari replied to this.

    CyberGene click on posts number on top of the page, you will find a fast scroller you can drag it to top by just one click

      Hari That’s what I’m doing but it’s pretty non-intuitive to have to do that in order to finish the posts move. I think a permanent overlay would be better if there’s at least one post selected for moving.

      2 years later

      Can this be used to move posts up and down within a topic ?
      I migrated one forum from MyBB to flarum Its posts within few topics are not according to posted dates

        wbntff nope, you should try fixing the migration tool instead.

        4 months later

        Is there a way to select and move all the posts in a discussion, without doing it one by one?

        PS: I know about the existence of the Merge Ext, but it rarely works in the proper way.

          robinodds By Move, do you mean re-tag? I am able to re-tag and essentially move threads using the mass actions extension.

            11 days later

            Hello.

            I have "Group sequential post moved event posts into one." on.

            If I select a single post to move, it does not result in any "EventPost PostMovedPost" posts at all in the original discussion.

            However, if I select two or more sequential posts, then I do get the move event logged.

            Anyone else seeing this?

            I don't fully understand the code but I guess I see the bug?

                    if ($groupSequentialPosts) {
                        foreach($posts as $post) {
                            $nextPost = $posts->firstWhere('number', $post->number+1);
            
                        if ($nextPost) {
                            if (! isset($grouped[$index])) {
                                $grouped[$index] = new Collection();
                            }
            
                            $grouped[$index]->push($post);
                            $grouped[$index]->push($nextPost);
                            $grouped[$index] = $grouped[$index]->unique('id');
                        } else {
                            $index++;
                        }
                    }
                } 

            The else statement only increments the $index, but it really should do something like:

            $grouped[$index++] = new Collection([$post]);
            

            I can test the fix on a dev instance, but assuming it works, what's the safest way to deploy the fix? I could modify the PHP manually but that won't survive upgrades/moves. I could submit a PR and hope it eventually gets approved, or I could fork Move Posts and figure out how to transition to the fork?

            Kind of working in the dark here, but this worked for me:

                if ($groupSequentialPosts) {
                    $index = -1;
                    $previousPostNumber = -10;
                    $uniqueSortedPosts = $posts->unique('id')->sortBy('number');
                        
            foreach ($uniqueSortedPosts as $post) { $currentPostNumber = $post->number; $isSequential = ($previousPostNumber+1) == $currentPostNumber; if ($isSequential) { $grouped[$index]->push($post); } else { $index++; $grouped[$index] = new Collection([$post]); } $previousPostNumber = $currentPostNumber; } }

            Here's the PR:
            SychO9/flarum-move-posts22

            And here it's verified in production.

            This sub-thread: https://forum.pianotell.com/d/781-piano/37

            has spawned this thread:
            https://forum.pianotell.com/d/892-fun-exotic-digital-keyboards

            You can see there are several instances of single posts and grouped posts, but all the move event messages look correct! 🙂

            7 months later
            • Edited

            Suddenly seen that this extension likely didn't work with Flarum 1.8.9. However, I am using it. Template of the event message is not applied when changed - I cant remove this dot in the end (maybe translation issue). But in general - it works with Flarum 1.8.9, like noted in first message.

              Gorm the page is confusing, the latest version of the extension 0.2.0 is only compatible with Flarum 2.0, but versions 0.1.0 of the extension are compatible with Flarum 1.x

                SychO any need to specify this in composer.json?

                SychO hm yeah 🤔 , it probably needs to show the latest compatible version of latest stable and upcoming beta, instead of showing compatibility of the latest version only. I'll try to patch that up.

                • Gorm replied to this.
                  • Edited

                  luceos or just fork the previous version like Move Posts 2 for Flarum 2.

                  SychO sadly that Move Posts will not get any updates any more for Flarum 1.x. Or can will? Is it possible?

                  How will compatibility status will be displayed? 🙂

                    Gorm no updates are necessary for 1.x, it works and will continue to

                    19 days later

                    I'm setting up a new FreeFlarum forum. I have your Move extension enabled but I can't find any "Move" option in the UI. The 3-dot menu has no move option. SK, who's hosting FreeFlarum, tells me that there should be something in the right sidebar but my right sidebar is blank.

                    What can I check for?

                      can it move post in the same discussion?