options - Read For Learn

How much string content can I store in an option?

Look at the table schema in wp-admin/includes/schema.php: // regular blog tables CREATE TABLE $wpdb->options ( option_id bigint(20) unsigned NOT NULL auto_increment, option_name varchar(64) NOT NULL default ”, option_value longtext NOT NULL, autoload varchar(20) NOT NULL default ‘yes’, PRIMARY KEY (option_id), UNIQUE KEY option_name (option_name) ) $charset_collate; // Multisite options CREATE TABLE $wpdb->sitemeta ( meta_id bigint(20) … Read more

Add_settings_field() parameterizing callback?

The last optional $args argument the you can pass to add_settings_fields() is passed to callback. So it seems you can use same callback just fine. Hope I am right because I just stumbled onto this two minutes ago because of discussion in chat. 🙂 PS looked through code and it’s indeed relatively recent, before ~2.9 … Read more

Get category slug and display it on a query_post

I am not positive how to do what you want. But I have been using this framework which is very similar to what you have above but is much easier to use http://aquagraphite.com/2011/11/smof-documentation/ setting up options is really easy and it is supported through github. There is a place to ask these exact kind of … Read more

WP_Options ID high

I had a similar issue on another site recently, memory usage was through the roof. When I checked the db, wp_options was about 80megabytes. Running this SQL reduced the entire db to 15mb: DELETE FROM `wp_options` WHERE `option_name` LIKE ‘%_transient_%’ Obviously, replace wp_ with your table prefix.

Where to hook register_settings for Settings API when also want to update options outside of Settings API?

Now i’ve thought about it(Mark is me, i use another account when i’m at other locations) all registering a setting does is prepare options.php to accept your incoming form data when a valid nonce is present and also provides a means to hook a sanitization method to the submission of that data. It’s really a … Read more

Settings API – save an array of options as one setting (array_push?)

Always develop with WP_DEBUG set to TRUE. You’ve a typo: array_push($valid_input[$id], $input[$id]; (missing ) after the array_push) You can’t push to arrays that are not … arrays. // So, check this before pushing: $valid_input[$id] = ! is_array( $valid_input[$id] ) ? (array) $valid_input[$id] : $valid_input[$id];

Blog Settings import/export in WordPress Network environment

Export the options table that is specific to the multisite blog in question (just the option names and values), import them into the new options table on the new site. This will work for every option that doesn’t use a prefixed option name, which is only user-specific stuff like capabilities and roles.

register_setting() vs add_option()

So do I still need to hook admin_init and call those register_setting() if I did add_option() before? Yes. You need. You may add add_option to set the default value. Another call to add_option will do nothing. However, the idea of register_setting() is more than just add_option(). Each setting has the context page such as (general, … Read more

store simple data in get_option()

To recap the comment chain above: I think that’s a perfectly valid way of storing some options in the database, however, it’s good practice to prepend your option name with some unique characters pertaining to your site or something, like ‘my_simple_links’ to avoid possible collisions with other plugins and themes that add_options. Also, if you’re … Read more

What is the advantage of the wp_options design pattern?

The ability to store abstract key-value pairs without modifying the database structure is the reason. Without that, WordPress loses much of its flexibility. I can’t speak for others, but the single largest reason why I develop atop WordPress is its flexible nature. To quote one of your links above, Usually the reasoning behind doing what … Read more

+ More