Tag Info

New answers tagged

0

The error you are getting is quite specific and tells you exactly what is wrong. Also debug errors are off topic here. Your real issue here is adding an image to the first post only, which you can accomplish with the build-in loop counter $current_post that starts at 0, so the first post will be 0, not 1. Inside your loop, you can do the following if ( ...


0

I know this is an old question, but I got this problem and to solve it. I just clean the database transient options. I used the plugin WP-Optmize to do this. Just remember to make a backup before install and run the plugin. I've been using this plugin a while and is very effective.


0

shanebp- you were totally right! It was an issue with the theme's BetterStudio plugin. There was a text field where I put an old Analytics ID# there. I just had to delete it. All good, now. :D


1

The function is_wp_error checks if the given var is an instance of WP_Error class (soruce code as WP 4.2.2): function is_wp_error( $thing ) { return ( $thing instanceof WP_Error ); } As you can see, if the given variable is a instance of WP_Error class, the function returns true, even if the object is empty. Your $error variable is a WP_Error ...


0

If you simply place the favicon.ico in the root level of your WP installation (using FTP, or whatever), it will work. A plug-in for this task is both unnecessary and a waste of resources


2

Try to disable the plugins via the database running this query in your MySQL: UPDATE wp_options SET option_value = 'a:0:{}' WHERE option_name = 'active_plugins'; Also, try to enable error debugging in your wp-config.php file adding this line: define( 'WP_DEBUG', true ); Also, could you paste a copy of your .htaccess file?


0

@TheDeadMedic was right, in my second code snippet, admin_init should be admin_menu. That solved my problem, thanks a lot to all of you! Corrected code: //remove from menu function remove_posts_menu() { remove_menu_page('edit.php'); remove_menu_page('edit.php?post_type=page'); remove_menu_page('edit-comments.php' ); } add_action('admin_menu', ...


3

If you don't wish to modify your core wordpress files to fix the issue, you can simply add the missing definition into your wp.config.php file. Something like: define('SCRIPT_DEBUG', true); Would remove the error. There is already a WP_DEBUG definition in there already so I would suggest putting it close to that.


1

You should use wp_enqueue_script to add the script. The documentation contains information about the function and how it should be used and some helpful examples. Basically, you will need to add something like this to the functions.php file: function myextension_enqueue_scripts() { wp_enqueue_script( 'myextension-angular', plugins_url( ...


4

This is a known bug As far as I'm concerned, you can easily fix it by replacing if ( SCRIPT_DEBUG ) { with if ( defined('SCRIPT_DEBUG') && SCRIPT_DEBUG ) { That should suppress the error for now. When Wordpress is updated again, this error may be overwritten, but I believe it will be fixed in the next update. UPDATE Fixed at build 32482.


0

I add ob_start(); to top of my pluggable.php and works - magic. Line 1 of file would be: <?php ob_start();


0

Well I did solve this. I have downgraded the wordpress version. I uploaded the old wp files to my server. Files should be rewritten ones in the server. Then I go back to website and upgrade it. Problem solved! This is my solution no other sugessions have worked for me. And the last warning DO NOT CHANGE YOUR WEBSITE URL EVER!!!! :)


2

Your problem is that you're using Reserved Terms. error is a reserved term, you can't use it. To get around this, you could intercept the request early, and do a redirect, changing the query parameters in the process. For example, handling a link get parameter: add_action( 'wp' , 'reserved_term_intercept' ); function reserved_term_intercept(){ global ...


0

I got the same error message after a plugin update for my [directory] website 1 Asked the hosting company to increase the allowed size but didn't work. Uninstalled all plugins and reinstall one by one and here goes the bingo.


0

There is a class variable that stores the last error string - $wpdb->last_error. By the looks of the way $wpdb is coded, if the query succeeds, $wpdb->last_error will be an empty string, if it fails, it will be the error string returned by MySQL. So something like this would do the trick. $result = $wpdb->get_results("SELECT * FROM this is not a valid ...



Top 50 recent answers are included