Sounds like a couple of possibilities 1) an upgrade that may not have completed successfully or fully – try reloading wordpress completely (download and ftp). This has happening to a few folk or 2) a plugin that may not be compatible with new version. For debugging purposes, try deactivating one by one till problem goes … Read more
I ran into this very same issue and I have a workaround. Hopefully it will be fixed in the upcoming 3.3 release as this trac ticket suggests. The workaround basically replicates the important bits of the wp-admin/options.php file where settings registered via the settings API are processed. The reason additional permalink settings do not currently … Read more
Try this: <?php $options = get_option( ‘schema_theme_options’ ); $meta_desc = $options[‘metadescription’]; ?> <?php if( ( is_home() || is_front_page() ) && ” !== $meta_desc ) : ?> <meta name=”description” content=”<?php echo $meta_desc; ?>”> <?php endif; ?> It’s a bit neater and a bit more foolproof than the other proposed solution.
Add a new settings section for the reset button that is called on every tab. In the callback function for the field create the reset button. I would include the submit button here too to get both side by side. In the validation function delete the whole option if the reset button is present in … Read more
There’re several things to note: get_settings() is deprecated and get_option() should be used instead WordPress comes with a function named select() that takes three arguments: Saved value, looped value, echo You’re better off saving your key, than the HTML capable “title” element in your options. It’s much safer to save in the DB an easier … Read more
It’s a PHP issue. The character ‘ is being escaped so that it can be safely in various places, not least of which is the database. That’s why your ‘ look like \’. You can use PHP’s stripslashes() function to clean it up, or (if it’s an array you need to clean up) WordPress’s stripslashes_deep() … Read more
If you experience such issues, examine the source code of the page, and search for the stylesheet used by Jetpack on the page: http://yoursite.com/wp-content/plugins/jetpack/modules/sharedaddy/admin-sharing.css You want to make sure that this URL can be accessed; if you use a caching service or plugin or if you have added redirection rules that impact this page, you … Read more
Here are few remarks after skimming through your code: you are using options name like id, title and global. You should use a prefix on these names, like vegas_, to avoid possible problems with other stuff using these option names. you should let the users know about validation problems (check out the add_settings_error() function) use … Read more
A better approach would be to have the user simply enter their tracking script ID. You know, something like UA-XXXXXXX-XX? Then in your header.php, output the standard tracking script: <?php if ( $ga = get_option( ‘google_analytics’ ) ) : ?> <script> var _gaq = _gaq || []; _gaq.push([‘_setAccount’, ‘<?php echo esc_js( $ga ) ?>’]); _gaq.push([‘_trackPageview’]); … Read more
The solution was to change the permalink structure from /%postname%/%post_id% to: /%post_id%/%postname%/ This magically fixed it – possibly WordPress queries are not so efficient the other way around or I ran into a bug with a plugin. Anyway, it’s blazing fast again, both backend and frontend