Comments on: WordPress: Working With Options

By: Darío Ferrer

Darío Ferrer — Sat, 23 Jan 2010 15:32:08 +0000

Sorry krillo, the above code is wrong, this is the right

$args = $wpdb->get_results( bla bla bla...
$options = maybe_unserialize( $args->option_value );

Then you can use it in this way:

echo $options['your_array_element'];

By: Darío Ferrer

Darío Ferrer — Sat, 23 Jan 2010 15:26:29 +0000

krillo,

$args = $wpdb->get_results( bla bla bla...
$args = maybe_unserialize( $args );

By: krillo

krillo — Tue, 05 Jan 2010 12:18:46 +0000

Hey, good info. It gave me the clue how to read wp_options values from one wpmu blog to another. This is how i did it:

    global $wpdb;
    $args = $wpdb->get_results("select * from wp_6_options where option_name = 'widget_zmags_thumb'");
    $options = $args[0]->option_value;
    $zmags = maybe_unserialize($options);

Where I used maybe_unserialize() from wp-includes/functions.php to unserialize the data to an array. Cheers!

By: Ajay

Ajay — Tue, 22 Dec 2009 15:57:14 +0000

How do you implement this with WordPress themes? The tutorial I followed adds a separate row for each option!

By: Dario Ferrer

Dario Ferrer — Sat, 19 Dec 2009 00:28:04 +0000

Well, I solved the issue with some conditionals on data (before send it to DB), but I'm still curious about some direct hook which allows delete (or at least set to 0) an array element placed into some option.

By: Dario Ferrer

Dario Ferrer — Fri, 18 Dec 2009 11:55:59 +0000

I wish to set the param2 to 0, or better, delete it. But "0" is fine also. Thanks.

By: Michael

Michael — Fri, 18 Dec 2009 11:31:24 +0000

Dario, depends on what you need. Override the array or object with a new one and update_otions. Or set the value of the param2 to '' or 0.

By: Dario Ferrer

Dario Ferrer — Fri, 18 Dec 2009 11:11:24 +0000

Great post. Handling data as objects is an excellent method. However I think the "add_option" hook can be replaced with "update_option", which also can creates new fields. By the way I have a question ¿how to delete only one of those elements, e.g. "param2"?. At this moment I'm some stucked with this issue.

By: Theme Uninstaller - WordPress, Options, Datenbank - dynamicinternet

Theme Uninstaller - WordPress, Options, Datenbank - dynamicinternet — Sat, 05 Dec 2009 08:50:42 +0000

[...] Diejenigen, die immer noch jede einzelne Option separat speichern, müssen die Zeile delete_option('your_theme_options') selbstverständlich entsprechend erweitern. Daher gilt, besser die Einstellungen in einem Array oder Objekt zu speichern und performanter zu arbeiten. Weitere Hintergründe gibt es im Beitrag WordPress: Working With Options [...]

By: Michael

Michael — Fri, 27 Mar 2009 21:41:37 +0000

Ozh, you mean the set_/get_transient stuff?
I think, many plugin authors should learn first to use one tablerow instead of 60. Than we can write about set_transient

By: Ozh

Ozh — Fri, 27 Mar 2009 21:19:15 +0000

Nice article for beginners.
But I was expecting something about how you need to register options for 2.8

By: kubi

kubi — Fri, 27 Mar 2009 15:00:09 +0000

Thanks! I always thought that i have to do serialize and unserialize, but good to know that wordpress does handle that for me.

By: Peter

Peter — Fri, 27 Mar 2009 14:03:47 +0000

Ahh.. Brilliant. Wordpress strikes again!

By: Michael

Michael — Fri, 27 Mar 2009 13:59:05 +0000

Thanks Alex

Peter, WordPress does the job for you. add_option and update_option calls internal maybe_serialize().
See function maybe_serialize() in wp-includes/functions.php at line 801.

By: Peter

Peter — Fri, 27 Mar 2009 13:48:06 +0000

I always assumed that both arrays and objects needed to be explicitly serialized (with serialize()) before they were stored in a database. Is this not the case? Does wordpress do this for you with add_option, or is it just unneccesary all together?

Obviously I need to do some reading on the subject...

By: Alex

Alex — Fri, 27 Mar 2009 12:38:12 +0000

Great article guys! This is something I've been needing to know about for a while.