summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--modules/content_multigroup/README.txt16
1 files changed, 8 insertions, 8 deletions
diff --git a/modules/content_multigroup/README.txt b/modules/content_multigroup/README.txt
index 2d83cd3..f2f9172 100644
--- a/modules/content_multigroup/README.txt
+++ b/modules/content_multigroup/README.txt
@@ -3,7 +3,7 @@
THIS MODULE IS STILL EXPERIMENTAL AND NOT READY FOR PRODUCTION!
===================================================================
-To try it out, add a content_multigroup.info file to the module.
+To try it out, add a content_multigroup.info file to the module.
The info file should be a plain text file that looks like:
===================================================================
name = Content Multigroup
@@ -20,7 +20,7 @@ The Multigroup group treats all included fields like a single field,
keeping the related delta values of all included fields synchronized.
To use a Multigroup, create a new group, make it the 'Multigroup' type,
-set the number of multiple values for all the fields in the Multigroup,
+set the number of multiple values for all the fields in the Multigroup,
and drag into it the fields that should be included.
All fields in the Multigroup will automatically get the group
@@ -43,26 +43,26 @@ widget list.
All fields that allow the Content module to handle their multiple
values should work correctly when a Multigroup is changed back to
a normal group. Fields that handle their own multiple values
-which may store different results in Multigroup and standard groups should
-implement hook_multigroup_no_remove_widgets() to add their widgets
+which may store different results in Multigroup and standard groups should
+implement hook_multigroup_no_remove_widgets() to add their widgets
to the list of widgets that cannot be removed from Multigroups.
If a simple array of widgets is not sufficient to test whether this
action will work, modules can implement hook_multigroup_allowed_in()
and hook_multigroup_allowed_out() to intervene.
-Custom code and modules that add fields to groups outside of the UI
+Custom code and modules that add fields to groups outside of the UI
should use multigroup_allowed_in() and multigroup_allowed_out()
to test whether fields are allowed in or out of a Multigroup.
TROUBLESHOOTING
-The most likely cause of problems with field modules not working in
-multigroup is if they wipe out #element_validate with their own
+The most likely cause of problems with field modules not working in
+multigroup is if they wipe out #element_validate with their own
validation functions, or they hard-code assumptions into submit or
validation processes that the form is structured in the usual
-field => delta => value order instead of allowing for the possibility
+field => delta => value order instead of allowing for the possibility
of a different structure. See Nodereference for an example of a field
that handles validation without making assumptions about the form
structure.