@AoBird, avoid daisy chaining child-parent relations if all possible. Use one parent post for everything related or simply pool. In this case old pool was useable, you can add posts to pool by adding pool:<ID> as tag or from pool settings, make it active and now it shows under Add to pool list.

Mairo said:
avoid chaining child-parent relations if possible. Use one parent post for everything related or simply pool.

Why? I don't see a point in making a pool for a few images, children serve the same purpose.
And it's easier to navigate in order when they are not all under same parent.

AoBird said:
Why? I don't see a point in making a pool for a few images, children serve the same purpose.
And it's easier to navigate in order when they are not all under same parent.

The "next" and "previous" are easier to navigate back and forth with, since view child posts takes you to a seperate page to view all of the children even if its just one.

Ramadan_Steve said:
since view child posts takes you to a seperate page to view all of the children even if its just one.

Click on the image not on "view all"

AoBird said:
Why? I don't see a point in making a pool for a few images, children serve the same purpose.
And it's easier to navigate in order when they are not all under same parent.

There's infinite amount of pool IDs and they can contain zero posts, so you don't need to spare them.

- Parent/Child relation is used when there's differend or directly related versions of image. Because of this, the best/original/first version is parent to rest of versions to make navigation easier as you can see all posts from that single post.
- Pools are for sequences of images, were it comic, image set where things happen in order or similar.
- Sets are free for all personal usage pools.

Then you can also combine them, e.g. videos with sequence then have gif versions as child to every video then you can add them to set where you take best videos from artist.

Main aim is to make everything as easy to browse as possible. Daisy chaining parent-child relations is not that. Also like I said, these posts inferior versions already were pooled, so there's pretty much no reason not to use the pool for exactly the same purpose, othervice it's left behind with only deleted inferior posts included.

Parent post link also always lacks preview, which makes it even harder to immidiately see what's going on without going to the parentest parent (which you have no idea how many posts you have to open before getting there) and starting from there where pool you can open up and see all everything immidiately.

AoBird said:
Click on the image not on "view all"

Even then you do need to click on post to change to next post and some people put it in way that parent post is next page and some put child as next page, which is never as clear as previous-next. With two pages comic this is fine, but anything more and now you have either daisy-chaining or bundled childs, neither are ideal. However child posts are shown in upload order, so if you upload 3 page comic in order, top child is alwasys the next page.

Let's take h0rs3 animation from post #1212493 as example. Parent-child posts do not work on mobile site (should file this on forums when get interest and time) and it gets even messier when you bundle in deleted images if you had all everything daisy chained instead of parented to single post like here.

...I know this whole comment is technically nitpicking and there's not actual guidelines for these things. At the same time daisy-chains and loops with parenting system are almost without exception harder to navigate when I browse the site and makes janitor work extremely much harder (did actually just untangle like three daisy-chain loops from you :P).
TL;DR: if it's three pages comic -> pool it.