InputfieldImage::renderReady() method

Called right before Inputfield render

Called before Inputfield::render() or Inputfield::renderValue() method by the parent InputfieldWrapper instance. If you are calling either of those methods yourself for some reason, make sure that you call this renderReady() method first.

The default behavior of this method is to populate Inputfield-specific CSS and JS file assets into $config->styles and $config->scripts.

The return value is true if assets were just added, and false if assets have already been added in a previous call. This distinction probably doesn't matter in most usages, but here just in case a descending class needs to know when/if to add additional assets (i.e. when this method returns true).

Usage

// basic usage
$bool = $inputfieldImage->renderReady();

// usage with all arguments
$bool = $inputfieldImage->renderReady($parent = null, bool $renderValueMode = false);

Arguments

NameType(s)Description
parent (optional)Inputfield, null

Parent Inputfield

renderValueMode (optional)bool

Whether or not we are in renderValue mode

Return value

bool

True if assets were just added, false if already added.


InputfieldImage methods and properties

API reference based on ProcessWire core version 3.0.244

Latest news

  • ProcessWire Weekly #569
    The 569th issue of ProcessWire Weekly brings in all the latest news from the ProcessWire community. Modules, sites, and more. Read on!
    Weekly.pw / 5 April 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

“We chose ProcessWire because of its excellent architecture, modular extensibility and the internal API. The CMS offers the necessary flexibility and performance for such a complex website like superbude.de. ProcessWire offers options that are only available for larger systems, such as Drupal, and allows a much slimmer development process.” —xport communication GmbH