This caused issues with the rename_column, as column_info expects an array

If a replacement is given the ORM uses the replacement
automatically.

…o number_of_publicly_viewable_posts

is_public is replaced by a different approach in querying data and
by is_publicly_viewable. If we would immediately replace is_public
with is_publicly_viewable, that would be a BC break.

…icly_viewable value

Password protected posts still end up in the post-type- and termarchives
and are publicly queryable. The difference is that the content is password
protected. Because if this detail, these posts should be noindexed, but the
archives should still update their data because the protected posts are
still shown there

This prevents unsetting the last modified date on archive indexables when the last
post of the post-type or taxonomy is removed. Also prevents moving the date back
in time when performing a reindex action.

…IX-22-number-of-posts

…IX-22-number-of-posts

… properties

…IX-22-number-of-posts

If we use the same version number for two separate model changes in
two separate releases, the later release won't receive automatic
model updates because the version hasn't changed as of the previous release.
Adding a comment of the version number, will cause a git merge conflict,
which forces you to look at what the correct version number should be.

…IX-22-number-of-posts

…mber-of-posts