and thanks for the tutorial! it’s bit lengthy btw! needed it though tired of creating plugins with tons of update and get_option!

New:
$settings = array(
‘version’ => ’0.8′,
‘custom’ => false,
‘custom_css’ => ”,
‘custom_html’ => ”,
);
Old:
$old = array(
‘use_custom’ => false,
‘cl_login_custom_code’ => ”,
‘cl_login_custom_html_code’ => ”,
);

Not sure the best way to go about this..

Also, register_setting and add_settings_field make it even simpler to use options (with array too).

1) You’re not going to overwrite anything unless you write the option back to the database. To save changes, call the entire array, change whatever elements you want, and then you write the entire array back to the database.

2) I’m pretty sure you can write an array to post_meta, though I’ve never had to do such myself.

Note that if the array is *really* large, it may be good to break it up into a couple different arrays (saved to different options or meta). Depends on the usage, but you may find that certain settings are only called in admin, for example.

1) My plugin has quite a few setting that loading up an array and storing that array in options is ideal for. But how do I not over write that array? I know that’s really stupid and obvious but… Do I just test for the option existing and not reload the array (unless say, there’s a reset option)?

2) What about post_meta, can that handle an array? How might you suggest managing 30+ “parms” at the per post level?

Hopefully you’re still keeping an eye on this thread. Thx.