Tag Info

Hot answers tagged

8

The JavaScript function wp_attempt_focus is causing this issue. The function fires shortly after page load, clears the form and focuses on it, forcing users to manually enter their login information. Chrome is filling in the username and password automatically, just milliseconds before the JS function clears the field. Chrome does not properly pick up the ...


4

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.


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.


3

You can use admin_notices hook http://codex.wordpress.org/Plugin_API/Action_Reference/admin_notices For example: function ravs_admin_notice() { ?> <div class="error"> <p><?php _e( 'Article with this title is not found!', 'my-text-domain' ); ?></p> </div> <?php } on ...


2

The output that you posted above is expected behaviour for $wpdb->print_error() if the following is true - You are running a single site, not multisite $wpdb->suppress_errors is set to false $wpdb->show_errors is set to false From the looks of your code, you meet all those conditions. Note also that, unless you have turned them off previously, ...


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?


2

The notice is easy to set via the hook admin_notices. You can set on each page a message via this hook. function my_admin_notice() { ?> <div class="updated"> <p><?php _e( 'Updated!', 'my-text-domain' ); ?></p> </div> <?php } add_action( 'admin_notices', 'my_admin_notice' ); Ping this hook on your ...


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 ...


2

Upon successful login wp_signon() sets a cookie in the http response header. Hence it has to be called before any HTML output is sent to the browser. Otherwise the "headers already sent" error will occur. After a successfull login you should redirect your user. Otherwise the login information will not present when the page HTML is rendered. A very ...


2

First of all, never use query_posts. Rather use WP_Query to construct your custom query which is the prefered way You are also using the category_name parameter wrong. If you look at the WP_Query documentation, it states category_name (string) - use category slug (NOT name). Go and have a look at the examples given in the docomentation under the ...


2

Xan is a georgian letter as I can find in Google, but it's not a valid Unicode Script for RegEx, you can find a list of the Unicode Scripts here: http://www.regular-expressions.info/unicode.html Maybe try using another one than Xan, maybe Georgian: preg_match( '/[\p{Georgian}]/u', $content, $results ); Let me know how that goes.


1

The root of the problem is that isset expects a variable to be passed to it. Also, I'm assuming that you expect the get_post_meta() to return a scalar value and not an array, so I added the third parameter set to true. // 3rd param: $single. Value of true means get scalar value, not an array. $ytlink = get_post_meta( get_the_ID(), ...


1

First thing i see that needs to be changed is your assigining unchecked values to your input fields. Try wrapping isset round the variable before echoing, this will stop errors if they are not assigned or empty. Second thing as you have passed a post id to get_post_custom() you dont need the second array. function basin_manager_meta_options(){ global ...


1

The first issue is your hosting company fault. The underlying library that performs the authentication that you are actually connecting to wordpress.org is probably missing some related configuration to be able to complete correctly the authentication. The solution they gave you is not secure and while I don't believe anything bad will happen because of ...


1

Using a tool to monitor itself is always a problematic idea, if wordpress has errors how do you know that those errors do not impact your integration code in a way which prevents them from being reported upstream? Your best option is probably to setup error reporting levels in php and if applicable in wordpress, and have an external tool to monitor the file ...


1

This is a PHP variable scope issue, there is no $wpdb defined in your function. Add global $wpdb; before trying to use the $wpdb object.


1

I found the problem. I didn't realize this was a generic message for pretty much all errors. I stripped everything out of the activation routine (similar to above) and ran it... got no errors. Started adding "stuff" back. And it appears a call to flush() at the end of the activation function trying to force the /wp-content/debug.log to be flushed to disk was ...


1

Issue was resolved by commenting the code that was requesting the jquery file from www.jquerye.com site. But as that site is expired the jquery link too which was giving 403 Forbidden error. I found that piece of code in themes/themename/framework/functions/init.php file with cURL requests. I have commented the last line which was adding to wp_head ...


1

It's probably due to an unclosed curly brace somewhere. Can include more code? The line numbers in the error message are not always where the actual issue is.


1

Your path have an extra _ in between widget-plugin.php and /js/upload.js. BTW, your path should just be plugins_url( '/js/upload.js' , __FILE__ ), Go and check the following wp_enqueu_scripts wp_enqueue_script wp_register_script admin_enqueue_scripts


1

First, you need to to find out what your current version of MYSQL... WordPress requires MySQL 5.0 or greater Since its a VPS, I'm assuming its a linux installation. Just type mysql -V on the command line and it will return your MYSQL version. If the version is compatible with wordpress, this message may be a "plugin/theme related" message. Look at your ...


1

wp-login is the file used to send user passwords e.g. new user registrations user lost passwords It might be you're getting a lot of registration spam? Is registration turned off on your install (settings > general)?


1

This is a lazy low quality list generate by your hosting. It is hard to understand it without more context but basically it is just lists the files in which there is a "mail" string and it has very little to do with the actual place which send mail. This kind of list are rarely useful in practice as they flood you with so much details it becomes hard to ...


1

For those who stumble upon this later, use either option 1 or 2 found here: https://core.trac.wordpress.org/ticket/19373. “For other developers who run into this and need to work around it, either of these 2 options work: call wp_set_post_terms() to add your taxonomies after calling wp_insert_post() set up a "current user" in your script before calling ...


1

Is the site still working/displaying properly , other than this error on the front end? It looks to me like your new hosting environment has warning and notice reporting ON. Consider looking in your wp-config.php file for WP_DEBUG and make sure it's set to false. Depending on how much control you have on your hosting environment, you should contact your ...


1

There are couple issues I see with your code that are probably contributing to your overall problem. Try fix the issues below and see if you can move forward with it. Syntax error: // Syntax here would cause error $q = new WP_Query( array('posts_per_page' => 'posts_per_page,'post_type'=>array($post_type),'category_name'=>$category)); Fix to ...


1

EDIT I have rewritten your complete shortcode. I've tested the code from my original answer, and with your code combined, the output was a bit unexpected. Major modifications I've removed category and replaced it with a tax_query (see WP_Query). The reason is, a tax_query can be used for build-in categories and for custom taxonomies, and custom ...


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( ...


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 ...


1

I had a similar issue when the permissions on the upload dir were not allowing the upload, try that first. Take a look at the codex Changing_File_Permissions for more info. Alternatively, check that the uploads dir is owned by the same user (on the server) as Wordpress, it's also mentioned in the above link. For how to... please find someone with more ...



Only top voted, non community-wiki answers of a minimum length are eligible