Tag Info

Hot answers tagged

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


1

This is a known bug: https://core.trac.wordpress.org/ticket/32118?cversion=0&cnum_hist=10 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 ...


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

get_term_link() will return a WP_Error object on error. You can't print an object or array or you will get messages similar to what you are getting. Use var_dump() instead or print_r() and you should see what is occuring. Your error even tells you that WP_Error is the object involved. You are getting errors when the term you are looking for is not found. ...


1

Found the problem. It was a problem with my host, in the path the ID3 folder name was uppercase, while on the server for some reason it was lowercase, this is why it didn't find it.



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