some weird stuff is happening with some entries as you can see Tailor thinks some entries are having some children pages when it is not the case (left arrow)
I’ve had this happen before. Did you recently move the item?
It’s happened to me where I move an item and it still has a child.
It’s also happened to me when the database doesn’t get updated but some other value does.
When converting a blueprint to a structure, it runs this code which should repair this scenario:
// Reset the nested tree nesting columns
EntryRecord::inSectionUuid('uuid-for-blueprint')->resetTreeNesting();
You could run it manually or convert the blueprint to an entry, migrate, then change back to structure and migrate.
1 Like