Posted by tomdavidson on February 28, 2014 at 4:44pm
Hello, I would like to included a flexible survey type of content in our spaces, maybe webform. Can anyone comment on creating OA aware content types? What needs accounted for in addition to an OG content type? Anyone use og_webform? What alternatives to webform are there?
Thank you, just trying to start of in the best direction.
-tom
Comments
Documentation on making content types OA-aware
Hi Tom!
So, I don't have any experience using webform or og_webform in Open Atrium 2. There has been some success using the Poll module with OA2 - I'm not personally that fond of that module, but it has worked. :-)
However, I can give you some general information about creating OA aware content types!
Here is some slightly out-dated documentation about making an Open Atrium 2 "plugin" on the old community site:
https://community.openatrium.com/dev/node/4744
According to Mike Potter, this will be updated and moved to Drupal.org, where we'll all b able to change and improve it.
I've personally got a checklist for making a content type Open Atrium-aware, which I'll integrate into the documentation once I'm able to! But for now, I'll include it here, because it contains some steps that aren't mentioned in the above docs:
Hopefully, that documentation plus my checklist and looking at the existing plugins will be enough to get you started. :-) If you have any questions, please feel free to ask here!
Regards,
David.
thanks
thanks
features
Hi,
I don't have much experience using features, can you describe a little more the last part of 5th step?
Thanks
I think Webform works OK with OA2
I did some brief testing of the stock Drupal Webform module with OA2 a couple of months ago and it seemed to work fine - the webform node type can be assigned to a section just like the built-in OA2 types and new forms created via the OA 'create content' button.
thank you David and bjuby. It
thank you David and bjuby. It seems like something that can be handled with features. But to use taxonomy terms for section type needs a work around. It is "better" to not use features when content such as terms are used?
You can use Features for Taxonomy Terms via Features UUID
You can use Features for Taxonomy terms via Features UUID. However, I don't usually in this case, because this is something that is frequently overridden on a individual sites.
For example, Work Tracker creates a "Tasks Section" term but on individual client sites, usually, I end up creating something more specifically geared to that site, ie. "Work Section", "Customer Support Section", etc.
In any case, for your Features you're free to use whatever you like!
https://community.openatrium.
https://community.openatrium.com/dev/node/4744
is been down at least since yesterday, do you have the full instructions at hand?
thanks
What about Entityform
hi
As said in the title does Entityform work's too?
Sorry.. just got an aswer while searching more
Hi
Sorry i think i've got the answer trough this link https://www.drupal.org/project/og_entityform.
Thanks