If you just want to update that one value, then you can use wp_update_site(): wp_update_site( 123, [ ‘domain’ => ‘new-slug.domain.com’, ] ); But to really update the site URL/address, you’d need to update both the siteurl and home options for the site: switch_to_blog( 123 ); update_option( ‘siteurl’, ‘new URL here’ ); update_option( ‘home’, ‘new URL … Read more
Ok, it took me a while to figure it out, but at the end I fixed the problem. The malware infected 99% of the wordpress files. It generated files in 99% of the folders and subfolders and in almost every single files it added the following: if (file_exists($filename = dirname(FILE) . DIRECTORY_SEPARATOR . ‘.’ . … Read more
If I take the value sanitize_callback out of the argument array completely, everything works as desired, so error-free. Yes, and that’s because you used the wrong callable syntax which then causes PHP to use a global function named sanitize_options instead of the method/function of the same name in your class (i.e. Faqdesk_Settings::sanitize_options()). So to solve … Read more
Want some honest advice? Work from a better code base.. Though, it’s not your fault, there are hundreds of blogs with variations of similar code, i’m not sure where it originated, but i see similar code “alot”… If you can get by without the hand holding and just manage with a good code base, i’d … Read more
If i had to venture a guess at the cause of the problem my initial thought would be toward the flush rules call. As Andy said, having debug on helps a great deal, and if you really don’t want to see the errors, you can always use the debug log instead, using the following in … Read more
Try changing this line: if(isset($_POST[‘field_id’]) && !empty($_POST[‘field_id’])) to: if(isset($_POST[‘field_id’]) && !empty($_POST[‘field_id’]) && current_user_can(‘update_core’)) and: function pp_add_admin() { to: function pp_add_admin() { if(!current_user_can(‘update_core’)) return; and ask for a refund 🙂
I am not sure this is the issue here, but if I remember right the current limitation of Settings API is that manage_options capability is required for everything to be saved properly. Quick search shows it might get fixed in 3.2, see this trac ticket.
Fixed my problem! I was finally able to find some info out there in the vast internet. Visit this site for info on fixing this odd issue. Over all using the remove_filter(‘the_content’,’wpautop’); did the trick. http://www.undermyhat.org/blog/2009/07/sudden-empty-blank-page-for-large-posts-with-wordpress/
If you configure your Theme settings code properly, the Theme will work fine without having any user-defined settings. The key is to define a defaults array, and anytime you need to output a Theme option, run an array_merge() on the defaults array, and the theme’s options DB entry. Something like this: <?php global $mytheme_options; $mytheme_options … Read more
I believe the issue is that your function that sets up the settings initially isn’t getting run upon activation. Add a call to your mouldings_register_settings_initial() in the activation hook, like this: function mouldings_activate() { global $wpdb, $mouldings_options; mouldings_register_settings_initial(); if ($mouldings_options === false){ $mouldings_options = array( ‘idea_item_columns’ => ‘4’ ); update_option( ‘mouldings_settings’, $mouldings_options ); } } … Read more