hey,
i've experimented a lot with atrium 2.12 and now trying to move all these changes into feature overrides. i read alla about features, the doc about feature override, but probably there are some open atrium related hints.
is there a proper way to start? lets say we have a feature B that depends on A . should i start overriding A and then B? does it matter? also should i start with the panopoly features before go to open atrium?
one more thing, on a fresh install, there seem to be some features already overriden. i've read an issue about that. in those features, should i also export those overrides?
Before using features_override module i had overriden 29 features and 2 have a needs review mark. while on my clean install test site a have 15 overriden features.
i made 29 features_override, enabled them as usual and in the end i still have 14 "overriden" and 8 "Needs Review".
should i do something? i'm preparing to update to OA 2.13
reverting or recreating the features, or clearing some cache, or whatever magic could help?
should o first revert the features which dont say anymore "overriden", one by one and then look again at the others?
Comments
Comment #1
Argus commentedThis is a good subject for the documentation pages. Added a subpage: https://drupal.org/node/2286149 to the documentation pages.
We could need some directions here.
Comment #2
Argus commentedComment #3
jkingsnorth commentedI've added a little information to this page, just to get started.
Comment #4
Argus commentedComment #5
candelas commentedAs I learned Features Override with Open Atrium, it would be very useful any tips to make this path easier. Thanks for the idea :)
Comment #6
mpotter commentedJust posted a blog on this here: http://www.phase2technology.com/blog/how-to-override-features
Comment #7
cgove commentedThank you for that blog post. I found it very instructive.
Comment #8
candelas commentedTomorrow I will read it. Thanks very much :)
Comment #9
jkingsnorth commentedAdded mpotters blog to the docs page:
https://www.drupal.org/node/2286149
Comment #10
candelas commented@mpotter excellent. Thanks.
Would it be to much to ask that if you have time in your next or so Webminar, you made a demo, please? I understood all, but it makes people confident to see someone working :) Not only changing a view name and creating a new feature, but bad done features and how to check (thanks for the drush commands)... ?
Thanks for all your contribution to our learning ;)
Comment #11
candelas commentedAdded to Features Override documentation https://www.drupal.org/node/1313910
Comment #12
candelas commentedHello
I thinks it would be also interesting a technical explanation on how it works. I want to mean the process that Features and Features Overrides makes reading in the data base using hooks. That could help for people to be able to make patches when they found an error. Of course good new programmers doesn't need that, but people that is learning like me, will appreciate a lot :)
Comment #13
mpotter commentedYou should post that over in the Features or Features Override queue. That's not an OA2 issue. Although honestly, you probably won't get much attention since that kind of detailed technical documentation just isn't typical for Drupal modules. Those modules are quite complex and are very advanced. The way I learned how they work was by going through the code. But you'll need a good knowledge of how Drupal itself works.
Comment #15
candelas commented@mpotter You were very right. Now that I have being studying on free time, I realize the capacity with Features and Features Overrides. Thanks for that work :)
From a designer>site builder > studding programing (free time) point of view:
Trying to optimize... since OA Features and Features Override has an expert (probably the best in D7) use, shouldn't it have a way to facilitate their users and show to other distributions that most advanced use? Or say that if you make many changes, you need to learn both? (in all distributions, of course)
Thanks again. A pleasure learning both modules and your use in OA :)
Sorry for my bad English (I have edited some big mistakes)