Documentation

ServiceTemplateTechnicalHandlingIntegration
in package

This class is only needed for the `RCB/Templates/TechnicalHandlingIntegration` filter.

Table of Contents

Properties

$codeOptIn  : string|null
Code opt-in.
$codeOptOut  : string|null
Code opt-out.
$pluginData  : array<string|int, mixed>
Result of `get_plugin_data` for the integrated plugin.
$pluginFile  : string
The plugin file which creates an integration for this template.
$templateIdentifier  : mixed

Methods

__construct()  : mixed
C'tor.
applyFilters()  : mixed
Run the `RCB/Templates/TechnicalHandlingIntegration` filter.
getCodeOptIn()  : mixed
Getter.
getCodeOptOut()  : mixed
Getter.
getPluginName()  : mixed
Getter.
getTemplateIdentifier()  : mixed
Getter.
integrate()  : mixed
Checks, if the current template matches the unique identifier. It returns `true` when you as plugin developer are able to override the opt-in / opt-out scripts, otherwise it returns `false` (e.g. another plugin already created an integration for this template, the unique identifier does not match or the passed `__FILE__` is not valid).
isIntegrated()  : mixed
Getter.
setCodeOptIn()  : mixed
Setter.
setCodeOptOut()  : mixed
Setter.

Properties

Methods

integrate()

Checks, if the current template matches the unique identifier. It returns `true` when you as plugin developer are able to override the opt-in / opt-out scripts, otherwise it returns `false` (e.g. another plugin already created an integration for this template, the unique identifier does not match or the passed `__FILE__` is not valid).

public integrate(string $pluginFile, string $identifier) : mixed
Parameters
$pluginFile : string

The __FILE__ of your main WordPress plugin file (the absolute path to your your-plugin/your-plugin.php file), see also https://developer.wordpress.org/plugins/plugin-basics/header-requirements/

$identifier : string

        
On this page

Search results