25

With drush you can probably do drush config-delete module_name.settings to delete the configurations that complain


23

Sure, Install the features module and then you go to structure -> features Click on "create new feature" Give it a name and then on Edit component you can select what you want to export. Select Content-type: node and you will see a list of all your content types, check the content types you want to export,( when you click the checkbox, you will see the ...


20

Welcome to the land of Features Configuration Management, aka FCM! It is not only about Features, and not about Configuration Management (as introduced in Drupal version 8). Instead, it is a special case of Software Configuration Management, aka SCM. Mostly because Features can be considered as a code generator, whereas that generated code needs to be ...


16

A feature or features may not revert for the following reasons as cited by some developers in the issue queue #744450: If your feature includes a view views cache could cause it to remain changed; especially, the migrate module (#1) Other features can cause your feature to be overridden (#10) Adding a line in your info file (#24) There are hooks overriding ...


16

You can revert a single features module with features_revert_module(). features_revert_module('my_feature');


16

Revert ALL components in feature $feature = features_get_features('my_feature_machine_name'); $components = array_keys($feature->info['features']); features_revert(array('my_feature_machine_name' => $components));


15

Solution Using a hook_uninstall() in FEATURE_NAME.install file and changing the status of the content type, so the system thinks it is an unlocked, custom content type. I posted this also on d.org. <?php /** * Implements hook_uninstall(). */ function FEATURE_NAME_uninstall() { // List custom content types added by this feature $custom_ctypes = ...


11

For me, the solution was to load the delete page manually since there is no "delete" link on the content types page. To do this, you just need to construct the URL yourself by following the same URL structure as the delete page for other content types: admin/structure/types/manage/YOUR_CONTENT_TYPE_MACHINE_NAME/delete This brought up the content type ...


11

You can use the Features Tools Module to disable a features module while leaving the functionality that was provided by the feature in place. Instructions provided by autopoietic here. First BACKUP YOUR DATABASE backup your feature (files) if you would like to use it again. Once installed, go to the 'recreate' page for a feature, uncheck all of ...


10

This is bypassable by cloning the views you need from the four views that the module provides, disabling the original views, and doing all your work in your clones which are 100% trackable.


10

You can get really fine-grained control over your cron runs with these modules: Elyisa cron Elysia Cron extends Drupal standard cron, allowing a fine grain control over each task and several ways to add custom cron jobs to your site. Ultimate Cron The Ultimate Cron handling for Drupal. Runs cron jobs individually in parallel using configurable ...


10

I assume what you want to know is how to generate a UUID in Drupal 8, because there's really not much else that you can do ;) Entities all have an UUID automatically, so if you store your data as a config or content entity, you just have to define the uuid entity key. To generate a UUID yourself, you need the uuid service: $uuid = \Drupal::service('uuid');...


9

Make sure the panel was not already added to another feature-module. You need to add the pagemanager stuff (handlers and pages) to the feature too. BTW the pagemanager status enabled/disabled is set via a drupal variable, so check also strongarm: If i.E. node/%node is enabled, then the variable page_manager_node_view_disabled is set to FALSE.


9

features_exclude is generated by the Features UI when creating a Feature. It is not created by drush fu FEATURE_NAME. See https://www.drupal.org/node/1064472#comment-7196064. The features_exclude lines are purely for the new UI to determine if an auto-detected dependency should be checked or if you have specifically unchecked it.


8

For a single View, there is no difference in functionality really. The view will be the same regardless. I use Features anyway because it's makes it more conventient to organize multiple pieces of configuration into "features". I'm not aware that ctools offers any easy way of doing "This view with that panel and those three dependencies in one module". That ...


8

Remove the component by deleting the corresponding line in your feature's .info file. Then run: $ drush fu <feature_name> In your case: Open the file /sites/all/<features_folder>/myfeature/myfeature.info. Delete the following line. features[views_view][] = myview2 Save the file. Run $ drush fu myfeature in your site's folder.


7

Use this procedure to rename a Feature module: drush pm-disable old_feature_name drush pm-uninstall old_feature_name rename the Feature module folder rename the .info file rename the .module file rename any hook prefixes drush pm-enable new_feature_name


7

menu_masks is a Drupal variable used to find the possible ancestors of a menu item. It contains an array of values that are calculated from the paths defined from modules; each values is essentially a binary number where the digit is 1 when the path part doesn't contain a placeholder, and 0 when it contains a placeholder. For example, the number for node/%...


7

Say you have two Features, and one field that is used in both Features, then you only need to export the field base ONCE. This is why I generally have a "controller" Feature that contains field bases, update hooks etc, and then for every other Feature I export the field instance, and then add a dependency on my controller feature. Basically, you are right -...


7

Open the content type (for example: article) for editing which should bring you to a URL: admin/structure/types/manage/article You can then append "/delete" into the URL like so: admin/structure/types/manage/article/delete Which should open a form that will let you delete the content type. I don't know if this lets you delete ones that are coming ...


7

Merge conflicts are probably going to be a given when multiple developers are integrating their configuration into a Feature. I wrote up several guidelines for reviewing feature code, but I think the most important is this: Only commit intended code changes. What does this mean? This means that each developer must review code before committing. There is no ...


6

In the current version of Drush, you can show a list of all features and their override state with (both short and long versions of commands shown, with and without the "-y" flag to skip confirmation questions): $ drush features-list $ drush fl If you want to show only the overridden features: $ drush features-list | grep -E "Overridden|Needs" $ drush fl |...


6

There is a feature request issue in a Drush queue, just stumbled on it. In donquixote's Drux project are commands you need: drux-enable-dependencies (dep-en) - Download and enable dependencies of existing modules. drux-find-obsolete (obs) - Find modules that are not direct or indirect dependencies of the modules given as arguments drux-generate (obs-...


6

Most include files exported by features are included on-demand by the modules that define that type of component. For instance, example.views_default.inc is included by the views module when loading default views. This is a common pattern in Drupal, not something that is specific to Features.


6

This is usually caused when the initial feature revert or install went bad. The feature has attempted to created a field (I've only seen it happen with fields) and it's got as far as creating the base table and it's revision table but as far as features is concerned the field doesn't exist. Features then tries to re-create the field but Drupal errors out ...


6

If you have the YAML file, you can put this in: /modules/your_module/config/install. Then the View will be imported, when the module is installed (but there will be no updates, if you change the YAML file, it will only be imported once). Btw. to export the YAML file you don't need Features, you can do this with core (admin/config/development/configuration/...


5

features_revert(array('module' => array('component'))); Where 'module' is the name of the specific features module (i.e. the the module generated when you download the feature) and 'component' are the components of those features. So if you just want to revert the fields defined in the feature you can use 'field' for component.


5

I used this patch from here - http://drupal.org/node/1014522#comment-5719202 After you patched it you can then use drush features-import-all --yes or drush fia -y to import features to database.


5

You can also just run a cron job from the server. If Cpanel is in use, it's simple to run cron.php on any schedule.


Only top voted, non community-wiki answers of a minimum length are eligible