... | ... | @@ -20,8 +20,9 @@ We don't know yet which will be the next CMS (see #141 and #130), but we know th |
|
|
|
|
|
# Tasks
|
|
|
|
|
|
* [ ] Prioritize sections to migrate based on the technical constraints (user-generated content first, or static content first; see section below)
|
|
|
* [ ] Theme port
|
|
|
* [ ] Blog migration (content, taxonomy, authors, comments)
|
|
|
* [ ] Theme port or rewrite
|
|
|
* [ ] Migrate users (and association of user-content)
|
|
|
* [ ] Partner listings
|
|
|
* [ ] Member listing (not launch-critical)
|
... | ... | @@ -29,7 +30,7 @@ We don't know yet which will be the next CMS (see #141 and #130), but we know th |
|
|
* [ ] Make it happen campaigns
|
|
|
* [ ] Events
|
|
|
|
|
|
Custom code:
|
|
|
# Custom code
|
|
|
|
|
|
* [ ] ccrm_extensionvalidation: Extension directory: only a small parts needs to be ported, assumes Tim works on the replacement (Comex), and that it would be ready in time.
|
|
|
* [ ] civicrm_org_members: sumfields hook for member program? (only a few lines of code)
|
... | ... | @@ -40,7 +41,47 @@ Custom code: |
|
|
* [ ] cividownload: download page, and a fundraising campaign that has long been disabled.
|
|
|
* [ ] 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.
|
|
|
|
|
|
Webforms:
|
|
|
# Content updates during the migration, or in what sequence to we update content
|
|
|
|
|
|
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
|
|
|
```
|
|
|
|
|
|
# Webforms
|
|
|
|
|
|
* [ ] [CRM for non-profits, what drives uptake?](https://civicrm.org/crm-for-non-profits), 2019-04 survey
|
|
|
* [ ] [Beyond English: improving internationalization in CiviCRM](https://civicrm.org/i18n-survey), last responses in 2019-08, survey
|
... | ... | |