timfarley

I had this problem and the issue for me was that somehow the database “table prefix” field got changed. Took me awhile to figure it out, but was super simple to fix once I got it – just change the $table_prefix in your wp-config.php file to match your database tables.

This is just one of many possible solutions, so if it doesn’t work then it must be a different issue you are experiencing…

Second this. Having a function like is_retina() would be incredible useful for creating responsive images…

Thanks a ton @mrangelmarino – your code worked perfectly for what I wanted to do!

I just pasted it into functions.php, added the name of my custom taxonomy and bingo, now when I use post_class() I get the tax terms too!

Cheers.

Thanks for the post – helped me solve that annoying issue as well. Just to clarify for anyone who stumbles onto this post: If you have a function to hide some of the menu items on the left side admin panel, like this:

function mytheme_remove_menu_pages() {
	remove_menu_page('link-manager.php');
	remove_menu_page('edit.php');
	remove_menu_page('upload.php');
	remove_menu_page('edit-comments.php');
}
add_action( 'admin_init', 'mytheme_remove_menu_pages' );

Change the last line to
add_action( 'admin_menu', 'mytheme_remove_menu_pages' );

Turns out the new function wp_editor has a few more capabilities and the fix is not as easy as just changing the function call.

For my use, I’m going to just switch over to plain old textareas for now – but I’m pretty sure the fix will involve a modification to this deprecated function call – on line 80 in “more-fields-settings-object.php” – and probably some other reworking somewhere because you have to no specify the HTML ids of the textareas for each place the TinyMCE WYSIWYG will appear.

Hope that helps a bit…

For those having issues with TinyMCE and the WYSIWYG editor on custom fields – I turned on WP errors and saw this Notice: wp_tiny_mce is deprecated since version 3.3! Use wp_editor() instead.

I’m going to try to update the call to wp_tiny_mce and see if that solves the issue…

I was having issues with this too, and manually deleting the custom field seems to have fixed it. And I agree, this is an awesome plugin.

Okay, I’ve figured it out. Thought I’d post my troubleshooting process for anyone with the same issue:

I went back and disabled all plugins again, but this time I also reverted back to TwentyTen theme. Everything worked as it should. I activated BuddyPress, and still no issues. Then went back to my Theme and the issue came back – so obviously something wrong with my code (kinda my thought all along). I started looking in functions.php – deleted all the code, and no more problem.

After a quick search through functions.php for the keyword “author” (the assumed culprit) I found the issue. Because my site is about books, I had set up a Custom Taxonomy called Author with the slug “author”. Changed this and all is good ??

Lesson learned – stay away from obvious reserved names!

I’ve checked the database, and in the posts table every post has an associated author ID – most say 1 (default super admin, which I’ve used to create most of the test posts), yet it doesn’t return results when I put this number into the custom query.

I was able to get it working using the ‘author_name’ parameter, but only for the admin account – other users still returned no results, even when I can see posts associated with their user ID in the database. I’d prefer to do the query on the user ID anyhow, in case the names change for whatever reason.

I’ve been using <?php wp_reset_query(); ?> as well, but it doesn’t seem to make a difference. As I said originally, I’m also seeing the problem on the Admin Edit Posts table, which certainly shouldn’t be affected by any custom queries that I’ve written.

Can anyone direct me where to look in the WP core for the place that author => 1 gets translated into a SQL query? Because the db table seems to be fine, and the query is constructed correctly I assume there must be an issue with translating the custom query into an actual SQL call? Perhaps?

I’m still having problems with this same issue. It seems anytime I try to use the parameter “author” anywhere on the site, I’m seeing broken results. Like the query returns nothing.

Noticed today that the Author template page is also not showing up (I get a 404) even though author.php is in the theme directory. I turned off permalink rewriting to check the query string, and sure enough it uses the same “author=…” syntax. Could this be an issue with a mislabeled table in the database?

I’m at a loss here…greatly appreciative of anyone that can point me in the right direction. Thanks.