0

I have a panels page in Features but as soon as i change the Features code, it automatically overrides the DB, this means that i don't get to see the "Overridden" state grey button, but always the normal "Default" state is shown and the changes are automatically shown on the web page.

The features should not change automatically the code, but only after i choose to override them.

Any ideas why this is happening?

I thought that was an UUID problem, but after removing the UUID module, the issue still persists.

Improve this question

1 Answer 1

Reset to default
1

No, this is how Features work. If your feature is in Default state, code change will cause direct effect on the components (there are some exceptions when clear cache is required). This is actually one of the biggest points and benefits of features, you can easily deploy updated code without any further required action.

Maybe there is a problem with your workflow, you should create you features on you Dev environment (configurations etc), then export them and deploy to Stage/Prod. It is not a good practice to directly change the configuration of components on Stage/Prod environments, you should always do your changes on Dev, then recreate the feature and deploy.

Improve this answer
4
  • I do have that workflow, but sometimes editors change content (of the "featured" panels page) on Prod and I would have thought (and think it was happening before at some stage) that importing the DB (and files) to a local deploy, would keep the same scenario as Prod: overridden features. So that I can easily recreate locally a new version of the feature, put it in version control, then push to prod again. This is not happening, so I will need to recreate the editor's changes manually on my local website, re-create the overridden state locally, then re-create the feature and push to the repo.
    – Mau
    Commented Jun 11, 2014 at 22:56
  • The issue is something else then, of course that when you import the DB with overrides to you local machine you should see the same overrides. Are you sure that your export/import DB procedure is ok and that your local site is using the correct newly imported production DB? E.g. all new content is present etc.?
    – m1n0
    Commented Jun 12, 2014 at 9:20
  • You are right, I have noticed that some parts of the DB are not getting synced when I drush sql-sync with Prod. For example, a content page didn't get imported... I wonder what could that be. I will consider to remove this question. Any ideas what could cause this strange behaviour?
    – Mau
    Commented Jun 12, 2014 at 22:47
  • try doing it manually (mysql dump and import)
    – m1n0
    Commented Jun 16, 2014 at 9:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.