Issue: Node History

Moved up to Alpha 1 because doing so any later would require us to create all content again. Instead of every node getting a page later, all nodes get a page automatically. Further, only pages and unpageable nodes get URLs, so we can avoid the node-page URL conflict false positive, as well as the easily mismatches with category/group/book membership. Further, this relationship would allow us to have Book-ness or Category-ness as combinable add-ons to a page, though I don't personally see the point.

Not doing this and moving forward with the current Alpha 1 data management scheme would actually be a feature reversion since we already track title edits for Books and Categories, and leaving this until later would remove that ability.

Unfortunately this will be a slight setback since most content nodes will have to be reworked around the page node rather than all being separate entities, and all the spots that utilize them may need to be updated. I can't see this rework taking more than a few days to a week, however.

That said, I don't recommend starting on this until we have finished the other tests, templates, and plugins possible, since making this change will require a dev environment backup restore.

Okay updated most of the DMs and other code. Still need to handle existing custom area paths (paths are now attached to the page node), creating the missing area page nodes on import, and the updates to the page creation UI.

With respect to my earlier assumption about combining Book/Category, etc, I don't think this will be possible (at least outright), since the permissions for each type are separate for now and are probably better that way.

On the same note, I think it would be best to have an error message if combining Island with Category or Template, since Category and Template wouldn't be able to do anything in an Island.

Things got complicated:

An Area requires a page node to be created, but likewise a page node requires an area to be created in.

This added 3 more steps to the upgrade process now that pages are required for all routable nodes (we originally wrote VaultWiki 4 with them optional).

Counter updates had to be almost completely rewritten to support the change. Needed to add a new node-type field to identify child node-types (Chapters to Books, Members to Categories, Group Pages to Groups).

Also added the page DM as an internal DM to the attach and area DMs, since those nodes need to have IDs first. Other node types like books and categories are internal to the page DM since they don't really need anything extra at creation time.

Still some other things to round out before closing this issue and re-installing: the interface changes, and external URL validation for old main pages.

Closing this issue. Fix up the editor when we debug the Edit tab.