You are not wrong about conceptual limitation, but any development convention is inherently about constraints. Constraints are “bad”, but they are also often good and important. In this specific case it’s slightly soured by Settings API being especially nasty snowflake, which historically led people to reinvent this particular wheel a lot. However, your estimate of … Read more
try using an empty condition <?php $bgimage= get_post_meta( $post->ID, ‘settings_image’, true ); if (!empty($bgimage)) { $imgURL = wp_get_attachment_url( $bgimage ); ?>background: url(‘<?php echo $img ?>’)<?php } ?> That should work as it checks to see if there is anything stored in the meta and will not print the background: url(”) if there is no data.
You appear to have the validation function commented out. Try this one for testing only: // WARNING THIS IS HORRIBLY UNSAFE DO NOT USE IN LIVE SITES function plugin_options_validate($input) { return $input; } Now do your options save? Validation functions are not optional. They take the settings, validate them, and return the valid ones. If … Read more
Well I dug into the function I wrote a bit more and realize the flexibility of the customization I had. So I was able to achieve the above by writing the php this way: if (!function_exists(‘pagination’)){ function pagination($pages=””, $range = 2){ $showitems = ($range * 2)+1; global $paged; if(empty($paged)) $paged = 1; if($pages == ”){ … Read more
500 errors can be for many reasons. In context of submitting form they are more common because of security setup, typically mod_security. It tends to have strict rules for form submissions / POST requests. There isn’t much you can do about it really. At one host in the past I needed to ask support to … Read more
The problem here was caused because I was using a sanitize callback declared in register_settings() (the on_save_chages() function below). This callback will ultimatly update the database with whatever value is returned, creating the fgw_login key if it does not exist. To ensure that I always had my default empty array if required I made the … Read more
The setting that is the first parameter is the not the option key. It is the key that you would’ve registered using register_setting register_setting( ‘settings_unique_key4172_91h, ‘option_key’, ‘name_of_sanitiser_function’ ); Then you can add settings errors like this, inside the callback function name_of_sanitiser_function(){ add_settings_error( ‘settings_unique_key4172_91h’, esc_attr( ‘settings_updated’ ), $message, $type ); } You might like a few … Read more
Save them using update_option(‘failed_login_limit’, 2); then call them by using var $failed_login_limit = get_option(‘failed_login_limit’);. Use the same syntax for the other variables, as well.
So having another look at this again today it occurred to me that it definitely must be an issue with settings_opts_page. In the light of a new day the answer is obvious, clearly settings_fields and do_settings_sections are intended to echo their contents and this is breaking the page render and seeing the form and contents … Read more
Setting aren’t registered in the database by plugin, though a plugin should be using an identifying prefix. That is, there is no specific queryable cross-linking in the database between plugin and setting. The only way to way to pull all settings for a plugin is to know what keys the plugin has used to save … Read more