InputfieldImage::getImageThumbnailActions() method

Get the image thumbnail icon actions/links/buttons

These are icon-only actions/links displayed next to the trash icon when hovering over an image preview. They are also displayed as icons on the far right side of a image when in full list mode.

Example:

Available since version 3.0.212.

Example

$wire->addHookAfter('InputfieldImage::getImageThumbnailActions', function(HookEvent $event) {
  $image = $event->arguments(0); // Pageimage
  $class = $event->arguments(3); // class to use on all returned actions
  $a = $event->return; // array
  $a['download'] = "<a class='$class' href='$pagefile->url' download><span class='fa fa-download'></span></a>";
  $event->return = $a;
}); 

Usage

$array = $inputfieldImage->getImageThumbnailActions(Pageimage $pagefile, string $id, int $n, string $class);

Arguments

NameType(s)Description
pagefilePageimage
idstring

Image id string

nint

Image index number

classstring

Class that should appear on all returned actions/links/buttons

Return value

array


Hooking InputfieldImage::getImageThumbnailActions(…)

You can add your own hook events that are executed either before or after the InputfieldImage::getImageThumbnailActions(…) method is executed. Examples of both are included below. A good place for hook code such as this is in your /site/ready.php file.

Hooking before

The 'before' hooks are called immediately before each InputfieldImage::getImageThumbnailActions(…) method call is executed. This type of hook is especially useful for modifying arguments before they are sent to the method.

$this->addHookBefore('InputfieldImage::getImageThumbnailActions', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $InputfieldImage = $event->object;

  // Get values of arguments sent to hook (and optionally modify them)
  $pagefile = $event->arguments(0);
  $id = $event->arguments(1);
  $n = $event->arguments(2);
  $class = $event->arguments(3);

  /* Your code here, perhaps modifying arguments */

  // Populate back arguments (if you have modified them)
  $event->arguments(0, $pagefile);
  $event->arguments(1, $id);
  $event->arguments(2, $n);
  $event->arguments(3, $class);
});

Hooking after

The 'after' hooks are called immediately after each InputfieldImage::getImageThumbnailActions(…) method call is executed. This type of hook is especially useful for modifying the value that was returned by the method call.

$this->addHookAfter('InputfieldImage::getImageThumbnailActions', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $InputfieldImage = $event->object;

  // An 'after' hook can retrieve and/or modify the return value
  $return = $event->return;

  // Get values of arguments sent to hook (if needed)
  $pagefile = $event->arguments(0);
  $id = $event->arguments(1);
  $n = $event->arguments(2);
  $class = $event->arguments(3);

  /* Your code here, perhaps modifying the return value */

  // Populate back return value, if you have modified it
  $event->return = $return;
});

InputfieldImage methods and properties

API reference based on ProcessWire core version 3.0.244

Latest news

  • ProcessWire Weekly #560
    In the 560th issue of ProcessWire Weekly we'll check out the latest core updates, cover newly released ProcessWire modules, and more. Read on!
    Weekly.pw / 1 February 2025
  • ProcessWire 3.0.244 new main/master version
    ProcessWire 3.0.244 is our newest main/master/stable version. It's been more than a year in the making and is packed with tons of new features, issue fixes, optimizations and more. This post covers all the details.
    Blog / 18 January 2025
  • Subscribe to weekly ProcessWire news

“Indeed, if ProcessWire can be considered as a CMS in its own right, it also offers all the advantages of a CMF (Content Management Framework). Unlike other solutions, the programmer is not forced to follow the proposed model and can integrate his/her ways of doing things.” —Guy Verville, Spiria Digital Inc.