| 1 |
|
======================================================= |
| 2 |
Additional actions for imagecache processing - a bundle |
Additional actions for imagecache processing - a bundle |
| 3 |
|
======================================================= |
| 4 |
|
by dman http://coders.co.nz |
| 5 |
|
|
| 6 |
This release was built against |
Not all actions are ported to imageMagick yet, most are GD only. |
| 7 |
imagecache: DRUPAL-5--2-0 |
Please have a go if you understand imageMagick syntax! |
|
imageapi: DRUPAL-5--1-1 |
|
| 8 |
|
|
| 9 |
As retrieved 2008-05-27 |
Some actions are incredibly inefficient. The transparency effects may load |
| 10 |
|
a whole image into memory and do bitwise operations on each pixel. This is |
| 11 |
|
impractical on limited hosts. Take care. |
| 12 |
|
|
| 13 |
... anything else may encounter mixed results |
Not all the modules in this package need to be enabled, |
| 14 |
|
just choose the ones you want. |
| 15 |
|
|
| 16 |
|
The new actions should become available when you edit an imagecache preset |
| 17 |
|
in the 'new action' drop-down underneath /admin/build/imagecache/{preset} |
| 18 |
|
|
| 19 |
|
=============== |
| 20 |
|
TROUBLESHOOTING |
| 21 |
|
=============== |
| 22 |
|
If actions don't seem to be showing up, it may be because of some heavy caching |
| 23 |
|
the admin utility does. |
| 24 |
|
|
| 25 |
|
- Visit /admin/build/modules. |
| 26 |
|
- DISABLE one of the imagcache presets |
| 27 |
|
- Visit /admin/build/modules/uninstall |
| 28 |
|
- UNINSTALL that preset |
| 29 |
|
- Then re-enable it! |
| 30 |
|
|
| 31 |
|
That will shake up the system enough to recognize the new action. |