Fieldtype::getFieldClass() method

Get class name to use Field objects of this type (must be class that extends Field class)

Return blank if default class (Field) should be used.

Available since version 3.0.146.

Usage

// basic usage
$string = $fieldtype->getFieldClass();

// usage with all arguments
$string = $fieldtype->getFieldClass(array $a = []);

Arguments

NameType(s)Description
a (optional)array

Field data from DB (if needed)

Return value

string

Return class name or blank to use default Field class


Fieldtype methods and properties

API reference based on ProcessWire core version 3.0.148

Twitter updates

  • ProcessWire 3.0.153 (dev) focuses on comments field updates, significant refactoring/improvements to ProcessWire’s core Template class and PagesLoader class (which is used by the pages API variable), and we introduce a useful new pages API method— More
    20 March 2020
  • ProcessWire 3.0.152 core updates— This week we have some major improvements to our core date/time Inputfield, as well as a new ability to specify your own custom classes for Page objects— More
    6 March 2020
  • This week we’ve got a couple of really useful API-side improvements to the core in 3.0.151, including predefined image settings and static language translation improvements— More
    21 February 2020

Latest news

  • ProcessWire Weekly #306
    In the 306th issue of ProcessWire Weekly we'll check out ProcessWire 3.0.153, introduce a new third party module called Image Crop Ratios, highlight some recent module updates, and more. Read on!
    Weekly.pw / 21 March 2020
  • ProcessWire 3.0.153 core updates
    This latest version of the core on the dev branch focuses on comments field updates, significant refactoring/improvements to ProcessWire’s core Template class and PagesLoader class (which is used by the $pages API variable), and we introduce a useful new $pages API method.
    Blog / 20 March 2020
  • Subscribe to weekly ProcessWire news

“We were really happy to build our new portfolio website on ProcessWire! We wanted something that gave us plenty of control on the back-end, without any bloat on the front end - just a nice, easy to access API for all our content that left us free to design and build however we liked.” —Castus, web design agency in Sheffield, UK