Your options are saved under a single key my_option_name, so you would access the individual options like: $my_options = get_option( ‘my_option_name’ ); echo $my_options[‘title’]; echo $my_options[‘id_number’];
Options are for general settings not specific to a post. To get the name of the author of a post, you will need to first get the ID of the author from the $post object and then use that to create a $user object from which the name can be retrieved. Example code: global $post; … Read more
Your register_settings function is not being called. Hook it into admin_init. function register_settings() { register_setting(‘settings-group’,’apiemail’); register_setting(‘settings-group’,’apipassword’); } add_action( ‘admin_init’, ‘register_settings’ );
The problem is your value=”” attribute, for example <textarea value=”<iframe>”> is invalid HTML, and the browser will do its best to try and fix the markup. That’s why you’re getting strange results So instead, remove the value attribute. You’ll also want to escape with esc_textarea to prevent malicious code breaking out of the text area
You’re not actually querying the database twice, if that’s what you’re worried about. Regardless, as you’ll see from the documentation, get_option() has a second argument you can use to define a default value for if the option hasn’t been set: $option = get_option( ‘option_name’, [] );
So I could understand why you “customized” (i.e. use your own version of) the do_settings_sections() and do_settings_fields() functions — because you want to use div and not table, right? But if it’s just about styling, you could actually just use CSS to style the table so that it doesn’t look like a table; however, you’ll … Read more
update_user_meta($current_user->ID, ‘description’, $_POST[‘user_description’]); in the form processing function will save the bio. I would keep the form action on the same admin page. As for data validation, I don’t see what there is to validate in the first place. It’s just a string – not an email, address or the like that needs to be … Read more
Unless you are working on WordPress core development you should not be writing anything but a: Theme Child Theme Plugin Mu-Plugin Drop-In For the last two see: http://hakre.wordpress.com/2010/05/01/must-use-and-drop-ins-plugins/ I am out on a limb a little bit here but I think that is the exhaustive list, with the first three by far the most common.
The privacy page was removed in WordPress 3.5. Go to wp-admin/options-reading.php and set search engine visibility there.
What you are looking at is serialized data– possibly multiple bits of serialized data as @Rarst noted. The Options API will serialize and unserialize automatically so all you need to do is: $data = get_option(‘optionkey’); // $data will be unserialized into whatever data type it was originally, object, array, etc // manipulate your data with … Read more