... | ... | @@ -89,51 +89,9 @@ This page defines the upgrade roadmap and tracks changes at a high level. This p |
|
|
* [x] cividownload: download page, and a fundraising campaign that has long been disabled. It's now a blog that is incorporated in a Gutenberg page. Code is in civiorg8.
|
|
|
* [x] extdir: `extdir/git-urls.json` and other services (medium-sized) - most of it should be replaced by Comex, but we may need to do more review.
|
|
|
|
|
|
# Content updates during the migration, or in what sequence to we update content
|
|
|
|
|
|
See also: [drupal8-upgrade-test](drupal8-upgrade-test)
|
|
|
|
|
|
One of the issues with a big upgrade like this, is that we cannot complete freeze the website during the upgrade.
|
|
|
|
|
|
The following types of contents can be added/changed by the community:
|
|
|
|
|
|
* users
|
|
|
* blog posts
|
|
|
* blog post comments
|
|
|
* extensions
|
|
|
* extension releases
|
|
|
* case studies
|
|
|
* events
|
|
|
* job posts (once a month?)
|
|
|
* demos (rare)
|
|
|
* member benefits (last added: 2018)
|
|
|
|
|
|
However, we do want to be able to change some content during the upgrade, on the Drupal8 site directly. Therefore, it should be fine to say that we:
|
|
|
|
|
|
* freeze all static content (i.e. any change to pages of types that are not in the above, or at least, assume the change must be changed on the d8 site as well)
|
|
|
* freeze all content types
|
|
|
|
|
|
and then the above contents (blogs/users/etc) will be re-imported on a regular basis.
|
|
|
|
|
|
To re-import users:
|
|
|
|
|
|
```
|
|
|
drush migrate-import upgrade_d7_user
|
|
|
```
|
|
|
|
|
|
To re-import blog posts:
|
|
|
|
|
|
```
|
|
|
drush migrate-import upgrade_d7_node_blog
|
|
|
drush migrate-import upgrade_d7_node_revision_blog
|
|
|
|
|
|
# or, possibly more dangerous, since it could resync other content types:
|
|
|
# drush migrate-import upgrade_d7_node_revision_blog --with-dependencies
|
|
|
```
|
|
|
|
|
|
# Content-type stats
|
|
|
|
|
|
This is to help evaluate where to focus:
|
|
|
This was to help evaluate where to focus, and track which content-types were regularly re-synchronized, and which were one-off migrations.
|
|
|
|
|
|
```
|
|
|
> select type, count(*) from node group by type;
|
... | ... | |