Home Explore Help
Sign In
bachir
/
materio-base-d7
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: ddae683ff3
Branches Tags
materio-base-d7
/
sites
/
all
/
modules
/
contrib
/
dev
/
strongarm
/
README.txt

README.txt 2.4 KB
History Raw

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859 
  1. 

  2. Strongarm 2.x for Drupal 7.x
    3. 

  3. ----------------------------
    4. 

  4. Strongarm gives site builders a way to override the default variable values that
    5. 

  5. Drupal core and contributed modules ship with. It is not an end user tool, but a
    6. 

  6. developer and site builder tool which provides an API and a limited UI.
    7. 

  7. 

  8. An example of such a variable is `site_frontpage`. In Drupal this defaults to
    9. 

  9. `node`, which ensures that the front page gets content as soon as some exists,
    10. 

  10. but for many Drupal sites this setting is simply wrong. Strongarm gives the site
    11. 

  11. builder a place in the equation - an opportunity to set the default value of
    12. 

  12. `site_frontpage` to something that makes sense for their site.
    13. 

  13. 

  14. 

  15. Installation
    16. 

  16. ------------
    17. 

  17. Strongarm can be installed like any other Drupal module -- place it in
    18. 

  18. the modules directory for your site and enable it (and its requirement,
    19. 

  19. CTools) on the `admin/build/modules` page.
    20. 

  20. 

  21. Strongarm is an API module. It does absolutely nothing for the end user out of
    22. 

  22. the box without other modules that take advantage of its API.
    23. 

  23. 

  24. 

  25. How Strongarm works
    26. 

  26. -------------------
    27. 

  27. Strongarm uses the CTools export API to make entries in the system module's
    28. 

  28. `variable` table exportables. Exportables are Drupal configuration objects that
    29. 

  29. lead a dual life -- they may be *defaults* set by code exports in modules, they
    30. 

  30. may be *overridden* if a user chooses to change the value in the database, or
    31. 

  31. they may be *normal* if the configuration object lives only in the database but
    32. 

  32. not in code. To learn more about exportables and the CTools export API, see the
    33. 

  33. CTools advanced help on "Exportable objects tool."
    34. 

  34. 

  35. 

  36. Exporting variables
    37. 

  37. -------------------
    38. 

  38. If you are a developer or site builder Strongarm gives you tools to export the
    39. 

  39. settings of variables in your site database and manage any overrides to default
    40. 

  40. values.
    41. 

  41. 

  42. To export variable values, you will need to enable either the [Features][1]
    43. 

  43. module or the [Bulk Export][2] module provided by CTools (as of June 29, 2010
    44. 

  44. you must use a recent checkout CTools `DRUPAL-6--1` in order to use Bulk Export
    45. 

  45. with Strongarm). Features provides a UI for adding variable exports to a
    46. 

  46. feature. Bulk Export provides a UI for generating defaults hooks with exported
    47. 

  47. variables that you can add to your own modules. You do not need to enable both
    48. 

  48. modules.
    49. 

  49. 

  50. 

  51. Maintainers
    52. 

  52. -----------
    53. 

  53. 

  54. - jmiccolis (Jeff Miccolis)
    55. 

  55. - yhahn (Young Hahn)
    56. 

  56. 

  57. 

  58. [1]: http://drupal.org/project/features
    59. 

  59. [2]: http://drupal.org/project/ctools
    60.