PageTable - Cleanup?

[ceberlin]

Since I discovered PageTableExtended I love PageTable. Now I can give editors the possibility to assemble new content from "building block" elements. That makes my setup very flexible.

With the growing number of edits, things start to become messy and I am thinking of clean-up strategies

 

A. Storing blocks at a central location

I chose the option to store all blocks at a central location. Because having the blocks stored in the page tree makes the page tree messy.

 

Now after having set 15 pages with approx. 3-5 PageTable pages each, I already ended up with abt. 280 PageTable pages. A lot of them are unpublished.

 

Questions:

1. Is it possible to identify the related parents to PageTable-Page easily, so I can sort out those with none?

2. Is it possible to clean up the not needed PageTable pages automatically (which not linked to a PageTable field somewhere)?

 

B. Storing blocks with the page that holds the PageTable field?

If I would love to use the alternative option to store PageTable pages with a page instead (which has benefits):

 

Questions:

1. Is it possible to make those  items optionally hidden in the PageTree? So they do not get mixed with real children-pages (which would look messy and be confusing for editors)?

2. Is it easy to switch the storage option in the PageTree module settings without making a lot of mess?

[LostKobrakai]

There are quite dedicated options in each pagetable field about how created pages should be handled in cases where they would become orphans. You should really use them to clean up. For how to find those unused pages afterwards take a look at this https://processwire.com/talk/topic/9730-get-pages-used-by-a-pagefield/ or the hooks in FieldtypePageTable.module. 

B. 1. Nope. At least there's nothing in the core to do that.

B. 2. It shouldn't matter to much which option you use. The mess will always be the same if unused pagetables are preserved.