for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
/**
* Auto Load Next Post Settings Page
*
* @since 1.0.0
* @author Sébastien Dumont
* @category Admin
* @package Auto Load Next Post
* @license GPL-2.0+
*/
if ( ! defined('ABSPATH')) {
exit;
}
// Exit if accessed directly
if ( ! class_exists('Auto_Load_Next_Post_Settings_Page')) {
* Class - Auto_Load_Next_Post_Settings_Page
class Auto_Load_Next_Post_Settings_Page {
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.
protected $id = '';
protected $label = '';
* Add this page to settings.
* @access public
* @param array $pages
* @return array $pages
public function add_settings_page($pages) {
$pages[$this->id] = $this->label;
return $pages;
} // END add_settings_page()
* Add this settings page to plugin menu.
public function add_menu_page($pages) {
} // END add_menu_page()
* Get settings array
* @return array
public function get_settings() {
return array();
} // END get_settings()
* Output the settings.
public function output() {
$settings = $this->get_settings();
Auto_Load_Next_Post_Admin_Settings::output_fields($settings);
} // END output()
* Save settings.
* @global $current_tab
* @global $current_section
public function save() {
global $current_tab;
Auto_Load_Next_Post_Admin_Settings::save_fields($settings, $current_tab);
} // END save()
} // END class
} // END if class exists.
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.