Ok, So I have found a solution to my problem; Pagelines encodes each key and value pair into a json string, within in its own option called pl_settings in the wp_options table. They also give you access to each of these key->value pairs using the following: $value = pl_setting(‘option_key’) Thus I have taken the approach … Read more
Hi @Amit: The answer is “Yes, it is possible.” The follow up question is “Do you really want to?” I thought it would be fun to see if I could build a plugin to do what you are asking for so I decided to see if it was possible. Of course I was able to … Read more
See the filter reference on the codex. In particular, note that you can use the form option_$foo to filter just a specific option key. So if you wanted a filter specific to the siteurl option, you could do: add_filter( ‘option_siteurl’, ‘my_url_filter’ );
There are two options I’m aware of, and neither are free: http://premium.wpmudev.org/project/new-blog-template http://wpebooks.com/replicator/ I haven’t actually tried either of them yet, so can’t recommend one over the other.
WordPress provides a convenient function for just this purpose: wp_handle_upload(). Assuming that you already have the appropriate file form field in your settings page, and that you’re using register_setting() for your options, and therefore already have an options validation callback, simply handle the file form field data using wp_handle_upload(). Here’s an example: <?php // Validate … Read more
I use the same options framework plugin and this is how I specify a select menu using this framework; $test_array = array( ‘one’ => __(‘One’, ‘options_framework_theme’), ‘two’ => __(‘Two’, ‘options_framework_theme’), ‘three’ => __(‘Three’, ‘options_framework_theme’), ‘four’ => __(‘Four’, ‘options_framework_theme’), ‘five’ => __(‘Five’, ‘options_framework_theme’) ); $options[] = array( ‘name’ => __(‘Select a Tag’, ‘options_check’), ‘desc’ => __(‘Passed … Read more
What I have seen in translation plugins (qTranslate, WPML, Multilingual Press) are two approaches. One is qTranslate’s (and the defunct xLanguage): use one field (one for title, other for content, etc) to hold all translations. And then, in the front end, decode its output according to the actual language. <!–en–>English<–:–><!–es–>Español<–:–> In the back end, the … Read more
I found out I needed to add html_entity_decode() around the value so my final code is… /** * Add Copyright text to general settings menu */ $custom_general_settings = new FD_Custom_General_Settings(); class FD_Custom_General_Settings { function __construct() { add_filter(‘admin_init’, array(&$this , ‘register_fields’)); } function register_fields() { register_setting(‘general’, ‘footer_text’, ‘esc_attr’); add_settings_field(‘footer_text’, ‘<label for=”footer_text”>’.__(‘Footer Text’ , ‘footer_text’ ).'</label>’ , … Read more
The settings API is crap. I need a long time and need try many until I got this working. My problem was that the values from my inputs never was passed to the validate callback. I end up in using the array method: <input type=”text” name=”foo[bar]” value=”baz” /> If the formular will be send, in … Read more
The only really interesting (and very important) part of the 3rd query is this: ‘project_location_children’, ‘a:7:{i:22;a:1:{i:0;i:23;}…etc…}}’ The a:n:{i:n; etc } stuff is a serialized PHP array. WordPress – for some historical reason – keeps track of term children in one option entry per taxonomy term. The painful thing is, that a lot of people don’t … Read more