A fork of phpThumbOf 1.4.0. pThumb is a lightweight, efficient, and actively maintained replacement for phpThumbOf. It offers most of the functionality of its predecessor while adding new features, fixing bugs, and offering some potentially dramatic speed improvements on sites which use phpThumbOf heavily.
Вопросы? Проблемы? Пишите по-русски!
pThumb is a drop-in replacement for phpThumbOf. It uses the same namespace, settings and component names, so after it's installed any code using phpThumbOf will automatically use the new version instead, with no further changes to the site required.
- Download pThumb via Package Management.
- Uninstall phpThumbOf if it's installed.
- Install pThumb.
Your phpThumbOf cache will be cleared in the process, but since pThumb generates slightly different filenames the images would have to be regenerated anyway.
(Actually you don't have to uninstall phpThumbOf first, but it makes things less confusing. If you uninstall phpThumbOf later, you'll have to reinstall pThumb.)
pThumb includes two snippets: phpthumbof and pthumb. They're exactly the same; use whichever snippet name you like best. phpthumbof is handy for an existing site that was already using phpthumbof; pthumb better for future compatibility and shorter too :-)
pThumb adds the following system settings:
Check File Modification Time: Checks the original image's file modification time and updates the cached version if necessary. Changing this setting's value will cause all currently cached images to become stale. Default: No
Global Defaults: An options string of global defaults. For example:
q=60&zc=C. These may be overridden by specifying another value in the snippet call.
Use Resizer: A global setting for which image manipulation class to use. Setting this to No means pThumb will use the MODX's built-in phpThumb class. See the Resizer section and extra for more details. Default: No
Use pThumb Cache: Controls which cache system to use: the ”classic” phpThumbOf cache or the new pThumb cache which supports subdirectories and uses shorter hashes. See the section below for more on this. Default: No
Clean Level: Specifies what the cache manager plugin should do on site refresh (site cache clear) events. The plugin processes all 3 caches: phpThumbOf style, pThumb style, and remote images. Possible values — 0: (default) Do nothing. || 1: Clean the caches separately based on the “Max Cache *” system settings (core > phpThumb). || 2: Delete all cached images. || One tip for option 1: changing one of the “Max Cache *” settings to 0 will disable cache cleaning for that parameter.
and several new properties to the phpthumbof/pthumb snippets:
&debug: When this is on, phpThumbOf will write the phpThumb debugmessages array to the MODX error log. This is very useful for troubleshooting phpThumb issues, like whether it's using ImageMagick on not.
&useResizer: Overrides the phpthumbof.use_resizer system setting to allow more flexibility in switching between phpThumb and Resizer. Useful if you generally want to use one but need the other in a few particular places.
&toPlaceholder: Stores the output in three placeholders: thumbnail URL, width and height. Ex:
[[pthumb? &input=`[[*imagetv]]` &options=`w=200` &toPlaceholder=`thumb`]]then
<img src="[[+thumb]]" width="[[+thumb.width]]" height="[[+thumb.height]]">. For more details on this see the Image Dimensions section.
&s3output, &s3multiImg: See the S3 documentation.
New pThumb Features
[Requires PHP 5.3 or higher]
pThumb comes bundled with Resizer, a lightweight modern alternative to phpThumb. Built on Imagine, Resizer supports the Gmagick, Imagick and GD extensions and is considerably faster than phpThumb for image sizing and cropping operations. Plus all the ZC options now work with GD.
See the Resizer documentation for more on its requirements and supported options. Note that it doesn’t support any of phpThumb’s filters, but many of these things can be done with CSS nowadays.
To enable it, go to System Settings and under phpthumbof, change Use Resizer to Yes. You don't need to make any other changes to your site; pThumb transparently handles switching between them. You can even override the system setting for a particular pthumb call by using the
&useResizer property (1 for yes, 0 for no).
New in version 2.1 is the pThumb Cache, an option which allows cleaner, more semantic and SEO-friendly URLs. Instead of everything being lumped into a one-level directory and having a 32-character hash appended, the new cache system stores thumbnails in subdirectories which mirror part of the original image's path and adds only an 8-character hash to filenames. Plus, pThumb still offers the original phpThumbOf-style cache. You switch between the two via a system setting.
Cache operation is controlled by three settings (in System Settings under phpthumbof):
pThumb Cache Location: The directory to store cached images. The path is relative to the MODX base directory, which is generally your web root. It defaults to
assets/image-cache. pThumb will create this directory if it doesn't already exist (as long as filesystem permissions allow it to).
Images Base Directory: This should be set to the directory where you have your images. It defaults to
assets, but you'll probably want to make it more specific. This directory and any above it will be left out of the cache filename's path. Any subdirectories below it will be included. See the example below for more details. If you run pThumb on an image outside this directory, it'll simply be put in the top level of the cache.
Use pThumb Cache: Once you've checked the above two settings, flip this to Yes to switch to use the new cache.
Example: You've set up a media source for all the content images on your site and they're all in
assets/acme/images/ Use that for the Image Base Directory setting. Leading/trailing slashes don't matter; pThumb will deal with them either way. You leave Cache Location set to the default. First you call pthumb on this image:
assets/acme/images/products/whiz-o-matic/exploded-view-1.jpg. To create a cache filename your Image Base Directory value—and anything in front of it—will be replaced with Cache Location and the rest of the path used for the name, meaning you'll end up with a thumbnail URL of
/assets/image-cache/products/whiz-o-matic/exploded-view-1.a9b0032f.jpg. Now suppose you've got some oddball image in
assets/misc/clutter/junky-junk.jpg (that is, outside the Image Base Directory you set). No problem, it'll just go to
Note: Switching cache systems won't migrate your cached images from one cache to the other; images be regenerated as needed. But it won't delete existing images either, so if you switch back they'll still be there.
Version 2.3 adds S3 support, with some improvements over phpThumbOf. See this page for instructions on how to use it.
pThumb goes to some lengths to handle remote images well, whether they’re coming from an S3 media source or from some other server. It uses cURL to download the original image to assets/components/phpthumbof/cache/remote-images/, then uses that local copy for all future operations, meaning things are quite fast after the first run. Version 2.3 improves file naming for remote images, so the output thumbnail file names will be the same as if the original images were local.
Be aware though that once the remote image has been cached, pThumb won't look at the original again unless you delete the cached copy. Or as an alternative, you may use a query parameter for cache busting. For example if you have a TV called someImageTV, you can do something like this:
<img src="[[pthumb? &input=`[[*someImageTV]]?v=1` &options=`h=150&w=150`]]">. The first time through this will cause pThumb to download a new copy of the remote image and generate a new thumbnail.
Starting in version 2.3.1 pThumb can also output image dimensions. It provides two ways of doing this. The first is the &toPlaceholder property described above. Sometimes though placeholders can be tricky, like when they’re being used in a chunk being iterated over by something like getResources. In certain cases—if you don’t give the placeholders distinct names like
&toPlaceholder=`img[[+idx]]`—all the placeholders will be filled in with the values from the last iteration.
However there’s another way to get image dimensions which doesn’t involve placeholders: add
dims=1 to the options string and pThumb will output src, width and height all together. Like this:
<img [[*imagetv:pthumb=`w=200&dims=1`]] alt="test image"> becomes
<img src="/image-cache/test.d39f9375.jpg" width="200" height="300" alt="test image">.
If pThumb runs into a problem during thumbnail creation, it will simply return the input file name and exit. Usually this happens because some part of the input path or file name is incorrect and pThumb can’t find the image. A broken image link on the front end is a sure sign of this, meaning your web browser can’t find the image either. pThumb will actually correct for several common configuration mistakes and find the image anyway, but in some cases it can’t. Check the MODX error log for more insight into what’s going awry.
Changes from phpThumbOf 1.4.0
pThumb addresses the following open phpThumbOf issues:
- [#37] Add a phpthumbof.jpeg_quality global default JPEG quality setting
- [#46] add phpthumbof.check_mod_time option to refresh the cached image if the original has been modified
- [#44] [#49] Prevent generation of identical images when the same image is used in multiple resources
- [#48] [#49] Fix duplication of images with identical names in different directories
- [#47] Exit quickly and silently when called with no filename, such as in the case of an empty placeholder
- [#52] Make input filename handling more robust, particularly when MODX is installed in a subdirectory
- [#53] Trim extension properly
- [#54] [#50] Fix cache cleaning
In addition to that it:
- Improves performance, especially on sites and pages which use phpThumbOf extensively. In some cases the difference can be very significant.
- Adds better debugging output, like the page's resource ID to make finding broken images easy, or simple access to phpThumb's debug messages.
- Improves phpThumbOfCacheManager behavior so that the cache isn't wiped out by default. The cache manager provides three different levels of cleaning and does better reporting on the number of files and the size of a cache.