The form says:

> When these files change, they will be automatically imported at the beginning of the next request. List one file per line.

I have no idea whether to put in filenames from my config/sync folder, or filenames that in my module's config/install. And if the latter, do they need to be declared my module's .info's config_devel section? And are they absolute or relative filenames, and if relative, relative to what?

Comments

joachim created an issue. See original summary.

michaelmallett’s picture

Agreed. 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

joachim’s picture

Ok 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:

modules/mymodule/config/install/node.type.mytype.yml

then any edits to the 'mytype' node type will get updated in the config install for the mymodule module.

joachim’s picture

The 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.

joachim’s picture

Status: Active » Needs review
StatusFileSize
new1.73 KB

Here's a patch.

benjy’s picture

Status: Needs review » Reviewed & tested by the community

LGTM. Interesting that you can use "
" in description tags, I thought they'd be escaped.

  • joachim committed abee76f on 8.x-1.x
    Issue #2845304 by joachim: Fixed admin UI form needs more instructions.
    
joachim’s picture

Status: Reviewed & tested by the community » Fixed

Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

firfin’s picture

For 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_id and see if you get some feedback. Worked for me.