Is it possible to just use the unlink function to place a feature in the db and not in code, but not use the direct save on Aegir development sites without any issues? I have features built that I just duplicate, replace/rename that are the same essentially, but I may just want to tweak or add a couple things and recreate the feature as a new one. I would like in this instance to be able to enable the original feature, use unlink to put everything in the db, make changes and recreate(without direct save). Would this be possible?

thanks so much for all the hard work!

Comments

perelman.yuval’s picture

perelman.yuval commented

Hi g76, the unlink is supposed to be made in the local environment, its remove the elements from the feature file and put them in unlink file, you can then add the unlink file to your git and commit/push it to your dev site.
If it is not what you need please explain and i will try to help you.
Thanks yuval perelman.

g76’s picture

g76 commented

Thank you so much for your help, I really appreciate it. I am diving into features more deeply, and I am not a developer, just builder/themer, so I have a learning curve here. What I would like to be able to do on dev sites, on the server(not local) is to be able to enable a feature and then have some way to remove it from code and place it in the database. So for instance, if I have a site which has 2 "sections": Workshops and Camps(those could be whatever) and I build and export the "Workshop Section" feature. Now the "Camps Section" feature is essentially the same let's say except for some views display/settings changes and display suite views templates/view modes. So I just rename the directory and file names and find/replace "workshop" with "camps" as everything is kit compliant. I want to upload and enable this on my dev site, but want it in the database not just in code(just as if I cloned everything manually within the site). Then I can make the adjustments and create a new and finished "Camps Section" feature. Is this possible or correct practice?

Also, this is not specific to your module, but is there a way to set features "defaults" on things, but allow users to choose settings/config without it overriding the whole feature? A simple example: I have a fluid grid view with title and image, I have what I would like to be "defaults" set on the fluid grid display settings like css3 settings off, but I would also like the flexibility to enable the css3 border and drop-shadow without overriding the feature. Is this possible? How do you do that? Again, I know this is not a question relating to your module, and I know you are busy, so no need to answer if you do not have time.

Thanks so much!

perelman.yuval’s picture

perelman.yuval commented
Status: Active » Closed (works as designed)