Name one field gpp_image_sizes[width] and the second gpp_image_sizes[height]. You will get an array in your save callback: $_POST = array ( ‘gpp_image_sizes’ => array ( ‘width’ => 100, // some number ‘height’ => 100, // some number ) )
You can use the get_settings() member function: public function register_widget_scripts() { $options = $this->get_settings(); wp_localize_script( ‘widget-name’, ‘obj-name’, $options ); }
The problem is your validate function RSP_options_validate(). This function always a empty string. Check your conditional statement with preg_match. If you test your source without this functions, it works. register_setting( ‘RSP_options_group’, ‘RSP_options’, ‘RSP_options_validate’ ); to register_setting( ‘RSP_options_group’, ‘RSP_options’ );
This kind of setup skeleton works for me to process the custom options page input : <?php /* Plugin Name: Settings Skeleton */ if(!class_exists(‘MySettings’)){ function call_my_settings() { return new MySettings(); } if (is_admin()){ add_action( ‘init’, ‘call_my_settings’ ); } class MySettings{ public function __construct(){ add_action(‘admin_menu’, array(&$this, ‘add_menu’)); add_action(‘admin_init’, array(&$this,’settings’) ); } public function add_menu(){ add_options_page(__(‘My Plugin … Read more
WordPress will only do a database lookup the first time if the option hasn’t been auto-loaded or already accessed prior. The performance hit is negligible, however if you’re loading multiple separate options with a bunch of get_options instead of using the serialised option functionality, then the initial lookup * X number of separate option rows … Read more
WordPress does not automatically texturize options. If you are using add_option(), update_option(), and/or get_option() then it should “just work”. Example: //Add an option to the database update_option(‘my_test_option’,’This is an option. Isn\’t it “special”?’); //Returns string: This is an option. Isn’t it “special”? echo get_option(‘my_test_option’);
Are you talking about Custom Fields? I would recommend reading this part of the codex: http://codex.wordpress.org/Custom_Fields#Usage
not really php solution, but that’s how I solved this problem. I deactivated phone and email fields from Store Settings -> Chekout and created custom ones. so now when I go to orders it displays in like Additional Checkout Fields Phone: Email:
Maybe a little debugging will help. Try this in your piece no.1 $theme = AisisCore_Factory_Pattern::create(‘AisisCore_Template_Builder’); if(isset($_POST[‘aisis_reset’])){ $theme->reset_theme_options(); } $options = get_option(‘aisis_reset’); print_r( $options ); //outputs $options value wp_die(); //will halt further process if($options == ‘true’){ echo ‘<div class=”alert alert-success”><strong>SUCCESS!!!!</strong> All Options have been reset! You can start again!</div>’; update_option(‘aisis_reset’, ‘false’); } What value do you … Read more
I’m wanted to comment rather than answer as I don’t have a solution for you, but I think this is too long 🙂 Hosts vary so widely on how and where they set memory allocation, and whether they allow hosted scripts to set it, that I don’t think there is a bullet-proof solution for you. … Read more