Hihave you checked the existing child page nodes with crx/de/ ? i've seen this behaviour when the jcr:content node was missing for one of the child pages (maybe due to importing content with not existing parent nodes).if this is the root cause of your problem i think Adobe has a hotfix for 5.6.1 sol...