Presently, there is no differentiation between a standard webform node and a VoIP webform node. This may cause confusion, as most of the standard webform components are not available as VoIP components (i.e. textarea, fieldgroup, etc).

This patch aims to fix the problem via the following:

- Adds a checkbox to webform enabled nodes allowing a user to specify whether the node is a VoIP-enabled webform or a standard webform.
- Adds a small database table, voipwebform_node, which tracks the specification
- Modifies the available components on the VoIP webform building page to only those compatible with VoIP Webform.

As an aside, the patch also does the following:
- Adds dependencies of voip and voipcall modules to the module's .info file
- Adds module into VoIP Drupal package in the module's .info file

CommentFileSizeAuthor
#1 voipwebform-webformnode-1515414.patch3.62 KBmatt@antinomia

Comments

matt@antinomia’s picture

matt@antinomia commented
StatusFileSize
new voipwebform-webformnode-1515414.patch3.62 KB

Here's the patch...

matt@antinomia’s picture

matt@antinomia commented

Devin, some advice on this one would be helpful... The way the patch is rolled there's a checkbox on the webform node edit form that allows the node creator to specify whether the webform is a VoIP webform. If so, it restricts the webform component types on the webform building page. I think this is a good idea.

Additionally, it may be a good idea to strip down the options on each of the component pages, as well. For example, when adding a 'select' component, many of the options on the component's edit page are not relevant to the VoIP implementation. Multiple, Listbox, Randomize (although it could be implemented my guess is that it would break things at the moment), Label Display. However, this may cripple the operation of the module for those attempting to build a webform for VoIP and web-based use.

Do you have any thoughts?