update is run)

 are moved from 'node_' to 'content_' namespace)
+ fixes for older 4.7 versions migration path
update.php required !!

 Karen and myself

#106932 fix install module to account for node_type table that is either renamed or not renamed by core during core installation.

#100744 fix problems that occur if 5.0 update is done without first renaming node_type table by adding error messages and rerunning the core update that will fail, #100742 add escaping to sql, add UPGRADE.txt file

Add drop table and clear cache to install after moving files from node_type_content table to core node_type table

#80335 got the go-ahead from JonBob to commit port to 5.0, patch by dopry, yched, drewish, edrex, and KarenS

of forms. Those using views.module may have to re-save views after this change.
Custom node templates will need to be renamed.

This commit changes the storage mechanism for hopefully the final time. As
was discussed a while back, now data is stored in tables for each content
type unless it cannot be. It may require per-field storage for two reasons:
- The field is present in more than one content type.
- The field allows multiple values.

Per-field help text. Currently only visible in text widget; to be added to
all widgets.

Added default values for DB fields.