Comments on: scbOptions Reference http://scribu.net/wordpress/scb-framework/scb-options.html Hello, this is where scribu geeks out Tue, 16 Mar 2010 16:01:20 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: scribu http://scribu.net/wordpress/scb-framework/scb-options.html#comment-3234 scribu Wed, 23 Dec 2009 18:58:51 +0000 http://scribu.net/?p=564#comment-3234 Hello and thanks for the 2 cents. :) I agree that serialized arrays are not a panacea. In your case, I would go even further and suggest a custom table for storing such a large amount of data. Hello and thanks for the 2 cents. :)

I agree that serialized arrays are not a panacea. In your case, I would go even further and suggest a custom table for storing such a large amount of data.

]]> By: Kim http://scribu.net/wordpress/scb-framework/scb-options.html#comment-3233 Kim Wed, 23 Dec 2009 18:52:30 +0000 http://scribu.net/?p=564#comment-3233 Hi, I just wanted to say nice work, but I have one comment on this option class you are suggesting. On our development department, we have been experiencing issues with serialization of large arrays. One solution was using the Pear unserialize function. Pulling this through to the way WP stores options (nothing wrong with it actually...on a small scale) it can cause errors sometimes. An alternative on the other hand, can be that a certain plugin developer prefixes the plugins' option names, for ex. myplug_option1 myplug_option2 ... With one simple SQL query, you can fetch all the options your plugin would require ( WHERE option_name LIKE 'myplug_%' ), and you can then 'maybe_unserialize()' the values before returning them as regular options... I use this technique in a personal ecommerce plugin to fetch a collection of over 100 options... which would otherwise result in a gigantic array of possible problem-values as decimals and sub-arrays. Just my 2 cents. Kind regards, Kim Hi,
I just wanted to say nice work, but I have one comment on this option class you are suggesting.

On our development department, we have been experiencing issues with serialization of large arrays. One solution was using the Pear unserialize function.

Pulling this through to the way WP stores options (nothing wrong with it actually…on a small scale) it can cause errors sometimes.

An alternative on the other hand, can be that a certain plugin developer prefixes the plugins’ option names, for ex.

myplug_option1
myplug_option2
…

With one simple SQL query, you can fetch all the options your plugin would require ( WHERE option_name LIKE ‘myplug_%’ ), and you can then ‘maybe_unserialize()’ the values before returning them as regular options…

I use this technique in a personal ecommerce plugin to fetch a collection of over 100 options… which would otherwise result in a gigantic array of possible problem-values as decimals and sub-arrays.

Just my 2 cents.

Kind regards,

Kim

]]>