This feature was changed in WordPress 3.5 already and was moved from Privacy to Settings -> Reading. You where in all propability using a very old WordPress version. You now just have the option to discourage indexing by search engines Checkbox ticked -> Search engines should not index your site, however this will not force … Read more
Save yourself a headache and make a class. The static variable can be accessed like a global once it’s loaded. Just be sure the class exists before you try to use it! if ( ! class_exists( ‘WPSE_20150123_Plugin’ ) ) { class WPSE_20150123_Plugin { // our variable that will be set and read back later public … Read more
It sounds like you have some of your Settings API calls wrong. Your dropdown input is created in the callback of your add_settings_field(). Each settings field needs to be told which settings section it is part of, and then your options page communicates which settings sections it needs to display through the do_settings() function. Here’s … Read more
If the setting in question is $setting, and is a checkbox type, you validate it like so: <?php $valid_input[$setting] = ( isset( $input[$setting] ) && true == $input[$setting] ? true : false ); ?> In this case, $input is the form data passed to the validation callback, where $input is an array-of-arrays. The validation method … Read more
Skimming through the Core_Upgrader::should_update_to_version() method, it looks like we can override the defined( ‘WP_AUTO_UPDATE_CORE’ ) // true (all), false, minor check, used to setup the local boolean variables$upgrade_dev, $upgrade_minor and $upgrade_major, with the following filters: … apply_filters( ‘allow_dev_auto_core_updates’, $upgrade_dev ) … apply_filters( ‘allow_minor_auto_core_updates’, $upgrade_minor ) … apply_filters( ‘allow_major_auto_core_updates’, $upgrade_major ) … So these filters have … Read more
You should (if available) submit the code you are working with, even if just a snippet, so we can assess your process in relation to your question. The short answer however is YES, it is safe, so long as you, prevent input fields being displayed on user profile page for certain user roles prevent unauthorized … Read more
You should store a version number for your plugin in the database (if you don’t already, add this pronto), using that you can do this (note that this is pseudocode): if( $db_version < {your desired version} ) { // previous updates and such $db_version = $new_version; //put that in the database } if( $db_version < … Read more
The correct way to store multiple options is as a multidimensional array and save to one option field. $myopt = array( ‘variable1’ => … ‘variable2’ => … …. ); Then simply pass the array to update_option() update_option(‘my_settings_field’, $myopt); If you pass an array WP will auto serialize the data for you. Then to read back … Read more
If you wrote your code correctly, then delete_option would be the correct way. The question isn’t how to clear the option; the question is how to structure your code such that the “option does not exist” case is a valid case. Think about it. The first time you start this code, that option isn’t going … Read more
…because your input (POST) name needs to match the one in your register_setting call: register_setting( ‘first_tab_options’, ‘first_tab_items’ ); …. <input type=”text” name=”first_tab_items”… Otherwise how the hell does WP know that some_name in POST holds your option data? 😉