OEL-1301: Move oe_content base fields into submodule #527
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OEL-1301
Description
Move oe_content base fields into its own submodule.
QA notes
Clean install
Testing the update path
git checkout 2.x
Go to
/admin/reports/status
and check that there are no Entity/Field Definitions mismatch errors.Do a login for a test user and, in the
node_field_data
table, check that the base fields bellow are correctly filled.git checkout OEL-1301
./vendor/bin/drush en oe_content_corporate_fields -y
./vendor/bin/drush updb -y
Refresh
/admin/reports/status
and check that there are no Entity/Field Definitions mismatch errors.Check the users_field_data table. The fields should be filled with the previous data.