Timeline for Features code changes overriding automatically
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2014 at 7:40 | vote | accept | Mau | ||
| Jun 16, 2014 at 9:48 | comment | added | m1n0 | try doing it manually (mysql dump and import) | |
| Jun 12, 2014 at 22:47 | comment | added | Mau | 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? | |
| Jun 12, 2014 at 9:20 | comment | added | m1n0 | 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.? | |
| Jun 11, 2014 at 22:56 | comment | added | Mau | 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. | |
| Jun 11, 2014 at 7:44 | history | answered | m1n0 | CC BY-SA 3.0 |