for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
/**
* Base class for hooking CMB2 into WordPress.
*
* @since 2.2.0
* @category WordPress_Plugin
* @package CMB2
* @author WebDevStudios
* @license GPL-2.0+
* @link http://webdevstudios.com
*/
abstract class CMB2_Hookup_Base {
You can fix this by adding a namespace to your class:
namespace YourVendor; class YourClass { }
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.
* Array of all hooks done (to be run once)
* @var array
* @since 2.0.0
protected static $hooks_completed = array();
* @var CMB2 object
* @since 2.0.2
protected $cmb;
* The object type we are performing the hookup for
* @var string
* @since 2.0.9
protected $object_type = 'post';
public function __construct( CMB2 $cmb ) {
$this->cmb = $cmb;
$this->object_type = $this->cmb->mb_object_type();
}
abstract public function universal_hooks();
* Ensures WordPress hook only gets fired once
* @param string $action The name of the filter to hook the $hook callback to.
* @param callback $hook The callback to be run when the filter is applied.
* @param integer $priority Order the functions are executed
* @param int $accepted_args The number of arguments the function accepts.
public function once( $action, $hook, $priority = 10, $accepted_args = 1 ) {
$key = md5( serialize( func_get_args() ) );
if ( in_array( $key, self::$hooks_completed ) ) {
return;
self::$hooks_completed[] = $key;
add_filter( $action, $hook, $priority, $accepted_args );
You can fix this by adding a namespace to your class:
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.