Manages the images uploaded by the users of the CMS Icybee.

Installs: 405

Dependents: 3

Suggesters: 0

Security: 0

Stars: 0

Watchers: 1

Forks: 0

Open Issues: 0


4.0.x-dev 2018-03-12 22:33 UTC

This package is auto-updated.

Last update: 2021-01-07 13:40:15 UTC


Packagist Build Status HHVM Code Quality Code Coverage Downloads

The Images module (images) manages the images uploaded by the users of the CMS Icybee.

Rendering Image records

Image active records render as string:


$image = $app->models['images']->one;

echo $image;

Will produce something like:

<img src="/repository/files/image/140-porte-verre-blanc.jpeg" alt="Porte verre" width="484" height="518" data-nid="140" />


The icybee/module-thumbnailer package is used to create thumbnails from images. The thumbnail() method is used to obtain a Thumbnail instance which represent a thumbnail of an image:


$thumbnail = $image->thumbnail([ 'w' => 64, 'h' => 64 ]);
# or
$thumbnail = $image->thumbnail('w:64;h:64');

echo $thumbnail->url; // /api/images/123/64x64
echo $thumbnail;      // <img src="/api/images/123/64x64" …

Thumbnail versions

The following thumbnail versions are created when the module is installed:

  • $icon: Represents an image or the image assigned to a record. It's a 24×24 image, usually used in the manage view (the index of a module in the admin).

  • $icon-m: A bigger icon usually used by the AdjustImage element to display available images in a grid.

  • $popimage: Represents a preview of an image in a PopImage element.

  • $popover: Represents a preview of an image that appears as a popover when the cursor hovers an $icon image.

  • $gallery: Represents images when they are displayed in a gallery.

Creating a thumbnail with a version is very easy:


$thumbnail = $image->thumbnail('$popover');

echo $thumbnbail->url; // /api/images/thumbnails/$popover
echo $thumbnail;       // <img src="/api/images/thumbnails/$popover" …

Assigning images to content records

The module provides to ability to assign images to content records—such as news or articles—to illustrate them. The Thumbnailer module is used to provide thumbnails through a fluent API.


echo $app->models['images']->one->thumbnail;
echo $app->models['images']->one->thumbnail('news-list');

echo $app->models['news']->one->image->thumbnail('news-list');
# or
echo $app->models['news']->one->image->thumbnail(':list');

echo $app->models['news']->one->image->thumbnail('news-view');
# or
echo $app->models['news']->one->image->thumbnail;

Configuring the assigning

An option to enable the association is injected in all the modules extending the Contents module. When the option is enabled the following things can be specified:

  • Whether or not the assigning is required.
  • The image to use by default if the association is not required.
  • The title and description of the injected image control.

These settings are stored in the global registry:

  • images.inject.<flat_module_id>: (bool|null) true if enabled, undefined otherwise.
  • images.inject.<flat_module_id>.required: (bool) true if the association is required, false otherwise.
  • images.inject.<flat_module_id>.default: (int) Identifier of a default image to use when no image is associated to a record. This only apply when the association is not required.
  • images.inject.<flat_module_id>.title: (string) The label of the image control injected in the edit form of the record.
  • images.inject.<flat_module_id>.description: (string) The description of the image control injected in the edit form of the record.

Additional controls specify the thumbnail options to use for the different views of the record, usually home, list and view. The thumbnail version name is created according to the following pattern: <module>-<view>, where <module> is the normalized identifier of the module, and <view> is the normalized identifier of the view.

Edit control

The edit block of the target modules is altered to provide a control allowing the user to select the image to associate with the record being edited.

The identifier of the selected image is recorded in the image_id meta property of the record.

Obtaining the image associated with a record

The image associated with a record is obtained through the image magic property:



Note that it's not an Image instance that is obtained but a NodeRelation instance. Because all calls are forwarded, the NodeRelation instance can be used just like an Image instance, although set throws a PropertyNotWritable exception.

The NodeRelation instance makes it possible to use short thumbnail versions. For instance, one can use ":list" instead of "article-list" to obtain the thumbnail to use in a list view of articles:



The magic property thumbnail returns the view thumbnail:


// or

Thumbnail decorator

Components can be easily decorated with a thumbnail using a ThumbnailDecorator instance:


use Icybee\Modules\Images\ThumbnailDecorator;

echo new ThumbnailDecorator($record->title, $record->image);

The previous code will produce something like:

<a href="/repository/files/image/140-porte-verre-blanc.jpeg" rel="lightbox[thumbnail-decorator]"><img width="24" height="24" data-popover-image="/api/images/140/thumbnails/$popover" class="thumbnail thumbnail--icon" alt="" src="/api/images/140/thumbnails/$icon"></a> My record title

Event hooks

The following event hooks are used:

  • Icybee\Modules\Views\View::alter_records: Include the assigned images to the records, if any.


The package requires PHP 5.5 or later.


The recommended way to install this package is through Composer. Create a composer.json file and run php composer.phar install command to install it:

$ composer require icybee/module-images

Note: This module is part of the modules required by Icybee.

Cloning the repository

The package is available on GitHub, its repository can be cloned with the following command line:

$ git clone git://github.com/Icybee/module-images.git images


The test suite is ran with the make test command. Composer is automatically installed as well as all the dependencies required to run the suite. The package directory can later be cleaned with the make clean command.

The package is continuously tested by Travis CI.

Build Status Code Coverage


The package is documented as part of the Icybee CMS documentation. The documentation for the package and its dependencies can be generated with the make doc command. The documentation is generated in the docs directory using ApiGen. The package directory can later by cleaned with the make clean command.


The package is licensed under the New BSD License - See the LICENSE file for details.