You are here

README.txt in Date Repeat Entity 7

Same filename and directory in other branches
  1. 7.2 README.txt
-- SUMMARY --

The Date Repeat Entity Module complements the Date suite of modules, in
particular the Date Repeat module.  For repeating dates that follow a
recurring rule, this module creates a unique entity for each date instance in
the series.

When an entity that belongs to a repeating date series is updated
or deleted, the user is offered the choice of updating/deleting the current
entity, all current and future entities or all entities in the series.

If the recurring rule for a date series is changed significantly (and this
can be controlled through a hook - see Customization section below) the existing
entities are replaced by a new set of entities that is generated to represent
the new series.  In this case the module provides a warning to the user if
referenced entities, associated with the current date entity, may be affected.

-- REQUIREMENTS --

The following modules must be installed and enabled for this module to work:

* Date, Date API, Date Repeat, Date Repeat Field (all part of Date module)
* Replicate
* UUID

-- INSTALLATION --

* Install as usual.  For more information see
 https://drupal.org/documentation/install/modules-themes/modules-7

-- CONFIGURATION --

* For each entity that you want to use this module with, you need to add two
  additional fields

  - field_clone_state (boolean)
  - field_master_uuid (text)

  These fields are necessary to manage the replication of entities in a date
  series and to track related entities via a master UUID.  An example feature
  module Date Repeat Entity Example, bundled with this module, provides these
  an Event content type including the above fields and a calendar view.

  Eventually, it is hoped that these two fields can be integrated with the
  schema definition provided by the Date module.

-- CUSTOMIZATION --

* When a date series is changed it may be  significant enough that the existing
  entities in the series should be deleted and replaced by a new series.  This
  module provides HOOK_repeat_entity_repeating_date_has_changed that gives other
  module developers the ability to determine when the change is significant such
  that the series is replaced.

* If a date series that is changed and the change is not significant to generate
  a new series the existing entities representing each date in the series are
  updated.  A separate HOOK_repeating_date_update is provided to enable other
  module developers to determine which properties and fields of each entity
  should be updated.

-- CONTACT --

Current maintainers:
* Simon Shutter (eft) - https://drupal.org/user/458578
* Tom Metzger (tmetzger) - https://drupal.org/user/423974

This project has been sponsored by:

* Groupanizer Technology Services

  We create websites and online tools that help choirs, choruses and music
  groups manage and organize members, music and more while creating a
  captivating public presence.  Visit http://www.groupanizer.com/ for more
  information.

File

README.txt
View source
  1. -- SUMMARY --
  2. The Date Repeat Entity Module complements the Date suite of modules, in
  3. particular the Date Repeat module. For repeating dates that follow a
  4. recurring rule, this module creates a unique entity for each date instance in
  5. the series.
  6. When an entity that belongs to a repeating date series is updated
  7. or deleted, the user is offered the choice of updating/deleting the current
  8. entity, all current and future entities or all entities in the series.
  9. If the recurring rule for a date series is changed significantly (and this
  10. can be controlled through a hook - see Customization section below) the existing
  11. entities are replaced by a new set of entities that is generated to represent
  12. the new series. In this case the module provides a warning to the user if
  13. referenced entities, associated with the current date entity, may be affected.
  14. -- REQUIREMENTS --
  15. The following modules must be installed and enabled for this module to work:
  16. * Date, Date API, Date Repeat, Date Repeat Field (all part of Date module)
  17. * Replicate
  18. * UUID
  19. -- INSTALLATION --
  20. * Install as usual. For more information see
  21. https://drupal.org/documentation/install/modules-themes/modules-7
  22. -- CONFIGURATION --
  23. * For each entity that you want to use this module with, you need to add two
  24. additional fields
  25. - field_clone_state (boolean)
  26. - field_master_uuid (text)
  27. These fields are necessary to manage the replication of entities in a date
  28. series and to track related entities via a master UUID. An example feature
  29. module Date Repeat Entity Example, bundled with this module, provides these
  30. an Event content type including the above fields and a calendar view.
  31. Eventually, it is hoped that these two fields can be integrated with the
  32. schema definition provided by the Date module.
  33. -- CUSTOMIZATION --
  34. * When a date series is changed it may be significant enough that the existing
  35. entities in the series should be deleted and replaced by a new series. This
  36. module provides HOOK_repeat_entity_repeating_date_has_changed that gives other
  37. module developers the ability to determine when the change is significant such
  38. that the series is replaced.
  39. * If a date series that is changed and the change is not significant to generate
  40. a new series the existing entities representing each date in the series are
  41. updated. A separate HOOK_repeating_date_update is provided to enable other
  42. module developers to determine which properties and fields of each entity
  43. should be updated.
  44. -- CONTACT --
  45. Current maintainers:
  46. * Simon Shutter (eft) - https://drupal.org/user/458578
  47. * Tom Metzger (tmetzger) - https://drupal.org/user/423974
  48. This project has been sponsored by:
  49. * Groupanizer Technology Services
  50. We create websites and online tools that help choirs, choruses and music
  51. groups manage and organize members, music and more while creating a
  52. captivating public presence. Visit http://www.groupanizer.com/ for more
  53. information.