Closed (fixed)
Project:
Configuration development
Version:
8.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Jan 2017 at 13:42 UTC
Updated:
26 Jan 2018 at 01:37 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
michaelmallett commentedAgreed. This module needs some basic instructions on how to set it up.
I've so far tried adding the yml files to the info file as per the instructions here
http://drupal.stackexchange.com/questions/191435/how-to-refresh-new-migr...
And adding them to the UI with full paths, relative paths, with and without yml. None work. Tried then running drush cdi1 {module}, no joy
Comment #3
joachim commentedOk so for the export, I've figured it out:
You enter a filename with a relative path to your Drupal root, where the name of the file is a config YML filename.
When that piece of config is saved in the UI, Config Devel writes the new config to the location specified.
So for example, if I put:
then any edits to the 'mytype' node type will get updated in the config install for the mymodule module.
Comment #4
joachim commentedThe same principle applies to the import.
This is useful if you're manually tweaking a YML config file in your module's config/import folder, for example. You'd add:
modules/mymodule/config/install/node.type.mytype.yml
to the import section, and changes to the YML file are imported automatically.
Comment #5
joachim commentedHere's a patch.
Comment #6
benjy commentedLGTM. Interesting that you can use "
" in description tags, I thought they'd be escaped.
Comment #8
joachim commentedThanks!
Comment #10
firfin commentedFor those who follow, sometimes new migrations still don't show up. This can happen when there is an error in your yml file. You can however try and make migrate_tools run your migration to get you some feedback.
Just try a
$ drush ms yourmigration_idand see if you get some feedback. Worked for me.