You can create a lock by using flock on one of your existing files (or create a special one fo this. Get the lock before you start the canculation and release it after the result was stored.
If you’re storing a set of options, or a single option with a schema, you should do the following: keep a version number stored in the database, ideally as a separate value, though if you are using a single option with an array inside it, you could store it there keep a version number in … Read more
The options are not being saved correctly because you used the wrong input name — it should match the second parameter for register_setting(). So for example, with register_setting(‘myplugin_options_group’, ‘api_username’), the input name should be api_username, but then you used myplugin_api_username. Additionally, it should be noted that screen_icon() has long been deprecated.
Basically, you’re not using the correct option name. In your viptips_settings_init() function, you use the name viptips_settings as the database option name when registering the setting: // The syntax is: register_setting( ‘<settings group name>’, ‘<database option name>’ ) register_setting( ‘pluginPage’, ‘viptips_settings’ ); So WordPress will use that viptips_settings when saving the option (i.e. update_option( ‘viptips_settings’, … Read more
Create tabs in admin options page from custom post type loop
Addition of custom option panel crashes Media Library & Admin Area
Add Plugin options as subpage to Theme options page
Your sanitize_callback function should not return false or null indicating that input is not valid – its intent is to always return a valid value. The value returned by this function is what will be save to the database, so in order for it to actually sanitize anything it will have to return something that … Read more
The best way to do it is right before you display the options page. Right before your call to settings_fields, add this: if( isset( $_REQUEST[‘settings-updated’] ) ) flush_rewrite_rules(); Remove the flush_rewrite_rules from your other function and that should do the trick. Its worked for me.
The problem is in my file settings.php (which renders the form). Look at the form action. It says action=”options.php” and then the settings_field() inserts a hidden field with the correct action. But WordPress prioritizes the form action, so, when submit the form, WordPress tries to load options.php instead of the correct action in the hidden … Read more