Most likely what you’re are experiencing is that within the edit_post() the updated post is automatically removed from the sticky posts. This happens for users that can publish posts and edit others post’s, after the post is updated and the save_post hooks have fired. Note that core uses helper functions like stick_post(), unstick_post() and is_sticky() … Read more
@Bowe You would need to create an array in your options function for the checkbox and give it an id a default state and assign the “checkbox” type to it. Here is a sample assuming you already have the code in place for the admin panel <?php // Set variables for the options panel $themename … Read more
The latest and greatest php version is always the recommended version. Seriously. All core devs use it when developing trunk. Only a few bother to test older php versions, as can be seen by the occasional ticket opened related to php4 or php5.x incompatibility. The same cannot be said by plugin authors, however… As you … Read more
Alternate approach (if you want/need to keep this in functions.php and go via hooks instead of modifying template) would be something like this: add_action( ‘pre_get_posts’, ‘pre_get_posts_home’ ); function pre_get_posts_home( $query ) { global $wp_query; if( $wp_query == $query && $query->is_home ) $query->set( ‘posts_per_page’, 1 ); }
If you are using the Settings API then you don’t have to save the options, that’s done for you. So when using an array to store the options your validation function should get an array of all existing options, update only the changed and return that array. Something like this: function my_settings_option_validate( $input ) { … Read more
try to change do_settings_sections(‘sample_section1’); to do_settings_sections(‘sample’);
This thread suggests that this isn’t necessarily an intended Child Theme usecase so theme-options.php isn’t explicitly overrideable. It indicates that you should rather be adding extra options using add_settings_field and the admin_init hook.
WordPress load is complicated process and hard to grasp in full. The very basic overview would be like this. What you should do for starters – think in specifics. A lot of common tasks (adding scripts, using hooks, etc) are standardized technically or conventionally. So go by task – decide what you want to do … Read more
Updating options via pure SQL is wrong. If you feel you have too many options to use the regular API you probably have too many options at all. A theme should not do the job a plugin can do. In fact, it should do as little as possible and let the user choose a plugin … Read more
<?php $user_id = 9; $key = ‘last_name’; $single = true; $user_last = get_user_meta( $user_id, $key, $single ); echo ‘<p>The ‘. $key . ‘ value for user id ‘ . $user_id . ‘ is: ‘ . $user_last . ‘</p>’; ?> More information here – http://codex.wordpress.org/Function_Reference/get_user_meta