README.txt 7.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187
  1. README for the Imagecache Actions Drupal module
  2. -----------------------------------------------
  3. Project page: http://drupal.org/project/imagecache_actions
  4. Current and past maintainers for Imagecache Actions:
  5. - dman (http://drupal.org/user/33240)
  6. - sidneyshan (http://drupal.org/user/652426)
  7. - fietserwin (http://drupal.org/user/750928)
  8. Release notes for 7.x-1.0
  9. -------------------------
  10. - If you use custom actions, run update.php.
  11. - If you use effects that use files (mask, overlays, underlays, text fonts),
  12. check the way they are specified. From 7.x-1.0 on, you have to specfiy the
  13. location using one of the schemes private://, public://, module:// or
  14. temporary://. If no scheme is specified, the file is searched for as is, thus
  15. relative to the current directory or as an absolute path.
  16. - Effects that use the transparency layer (e.g. mask, rounded corners) do not
  17. automatically convert to PNG anymore. Use the "Change file format" for that.
  18. - There's no upgrade from D6. You will have to recreate your styles manually.
  19. Warning:
  20. Ongoing development in the area of e.g. making the effects more consistent,
  21. adding and/or removing parameters or redefining their meaning, might cause
  22. forward incompatibilities with future versions. Thus, we cannot and do not
  23. guarantee backwards compatibility or automatic upgrade paths for future
  24. versions.
  25. Introduction
  26. ------------
  27. The Imagecache Actions module provides a suite of additional image effects that
  28. can be added to image styles. Image styles let you create derivations of images
  29. by applying (a series of) effect(s) to it. Think of resizing, desaturating,
  30. masking, etc.
  31. The additional effects that Imagecache Actions provides include:
  32. - Watermark: place a image with transparency anywhere over a source picture.
  33. - Overlay: add photo-corners etc to the image
  34. - Text overlay: add e.g. a copyright notice to your image.
  35. - Color-shifting: colorize images.
  36. - Brighten/Darken.
  37. - Alpha blending: use a grayscale image to define the transparency layer of an
  38. image.
  39. - Canvas manipulation: resize the canvas and add a backgroundcolor or image.
  40. - File Format switcher: if you need tranparency in JPGs, make them PNG. If your
  41. PNG thumbnails are 30K each, save them as JPGs.
  42. - Rounded corners.
  43. - TODO: complete list, check short descrptions
  44. These effects are grouped in submodules. Just enable the ones you want to use.
  45. TODO: list submodules and their sets of effects.
  46. Imagecache Actions supports both the GD toolkit from Drupal core and the
  47. Imagemagick toolkit. However, please note that Imagemagick support is not yet
  48. complete. Please file an issue if you encounter problems in using Imagemagick.
  49. What is imagecache_action not?
  50. ------------------------------
  51. Imagecache Actions does not provide a new UI or new menu items. It hooks into
  52. the already existing image styles system (from Drupal core). See
  53. http://drupal.org/documentation/modules/image for more information about working
  54. with images.
  55. A note about the name of this module
  56. ------------------------------------
  57. Image styles are part of Drupal 7 core and are the successor of the Drupal 6
  58. imagecache module. In Drupal 6 image styles were called (imagecache) presets and
  59. the separate effects that made up a style were called (imagecache) actions. In
  60. porting to D7, that name has not been changed (yet).
  61. Augmenting the Drupal core image module
  62. ---------------------------------------
  63. This module might also provide additional features to the Drupal core image
  64. module. Currently no such features are implemented, but they might be in the
  65. future, think e.g. of adding a "copy image style" feature. This allows to test
  66. D8 image module features in real life.
  67. Solving errors in the core image handling:
  68. - [#1554074]: scale does not work with imagemagick when dimensions are unknown?
  69. Which toolkit to use?
  70. ---------------------
  71. Personally, I (fieterwin) prefer the imagemagick toolkit:
  72. - It is better in anti-aliasing. Try to rotate an image using both toolkits and
  73. you will see what I mean.
  74. - It does not execute in the PHP memory space, so is not restricted by the
  75. memory_limit PHP setting.
  76. - The GD toolkit will, at least on my Windows configuration, keep the font file
  77. open after a text operation, so you cannot delete, move or rename it anymore.
  78. On the other hand: the GD toolkit is always available (in the correct version),
  79. whereas imagemagick is not always present on shared hosting or may be present in
  80. an antique version that might give problems.
  81. Please also note that effects may give different results depending on the
  82. toolkit used.
  83. Dependencies
  84. ------------
  85. - Drupal 7.x
  86. - Image module from Drupal core
  87. At least 1 of the available image toolkits:
  88. - GD toolkit from Drupal core
  89. - Imagemagick toolkit: http://drupal.org/project/imagemagick
  90. Installing
  91. ----------
  92. As usual.
  93. Usage
  94. -----
  95. After enabling the module:
  96. - Assure that the Image module from core is enabled.
  97. - Configure your toolkit and its settings at admin/config/media/image-toolkit.
  98. - Define image styles at admin/config/media/image-styles and add 1 or more
  99. effects as defined by this module
  100. - Use the image styles via e.g. the formatters of image fields.
  101. Upgrading from D6
  102. -----------------
  103. There's no upgrade path defined for sites upgrading from D6 to D7. This means
  104. that you will have to manually redefine your D6 imagecache presets as D7 image
  105. styles. Note that actually an upgrade path would have to be defined by the
  106. imageacache module, not this imagecache actions module. However, as there is no
  107. D7 version of imagecache that provides an upgrade, users may post an upgrade
  108. function to the issue queue and we will incorporate it.
  109. Backwards compatibility
  110. -----------------------
  111. Future releases will not be guaranteed to be backwards compatible. Implementing
  112. Imagemagick support e.g. might give unforeseen problems that can only be solved
  113. by changing the details of what an effect does. furhtermore current behavior of
  114. the image mask effect is to also change the file format to png. This effect
  115. should not do so, and thus will probably be changed in a future release. We will
  116. document these kind of incompatibilities in the changelog and the release notes.
  117. File form fields
  118. ----------------
  119. A number of effects have a file form field where the editor can define a file
  120. name to use. This canbe e.g. for overlays, masks or fonts. The file name should
  121. be defined using either:
  122. 1 of the (enabled) scheme's:
  123. - public://
  124. - private:// Preferred for site specific masks, overlay's, etc, that do not need
  125. to be shared publicly.
  126. - module://{module_name}/{resource-name} Introduced by the imagecache_actions
  127. module and preferred for module provided resources, like the button overlay
  128. of the Video Embed Field Overlay module
  129. (http://drupal.org/project/video_embed_field_overlay).
  130. - temporary:// Unlikely to be useful, but supported anyway as all schemes are
  131. supported.
  132. or a relative (to the current directory, probably Drupal root) or absolute path.
  133. Support
  134. -------
  135. Via the issue queue of this project at Drupal.org.
  136. Known problems
  137. --------------
  138. These are better documented in the issue queue, but might be listed here (as
  139. well).
  140. - Underlay does not work in imagemagick if the dimensions of both images are not
  141. equal. As a workaround first add a canvas effect with a fully transparent
  142. background.
  143. - Underlay/overlay: keywords in the x and y offset fields do not work.
  144. - Underlay does still display a message about Iamgemagick not being supported.
  145. - Brightness values outside the -250 .. 250 range are accepted.
  146. - Check colorfields that allow a transparency component or allow to be empty to
  147. specify fully tranparent.