WordPress相邻岗位的职能，被3.1-beta1打破

到目前为止，我一直在使用这个整洁的小代码片段来显示相邻的帖子（即与当前帖子在同一个类别中的帖子）。它是由代码taked> 制成的，看起来像这样，并且做得很好： cat_ID, $categories)) { => tag1+tag2,\"orderby\"=> I\"m running now this template on a 3.1-beta1 test site, and I notice that this snipped doesn\"t output anything at all. It doesn\"t give any error message either. The resulting HTML code from the function above: Any idea what\"s going on? An unpatched 3.1-beta bug, or a deprecated function? As an aside, it would be great if we could find in the Codex documentation more concrete examples of \"how to get things done\", which would be trusted methods that won\"t become invalidated by updates. Examples of such functions that come to my mind: – Displaying image-attachments in a custom manner. The best sample code that I found so far is not in the codex, but in this blog: http://digwp.com/2009/08/awesome-image-attachment-recipes-for-wordpress/ – Creating a simple breadcrumb trail. The solution I used until now was based on this: http://dimox.net/wordpress-breadcrumbs-without-a-plugin/ — it doesn\"t work in the latest 3.1-beta. – Displaying posts that share the same parent categories as the current post. The solution I used until now: see above. Broken by 3.1-beta. In other words: I certainly do appreciate the diversity of the WordPress eco-system, but sometimes I wish there would be a more centralized \"cook-book\" where theme developers can look for tested, documented and reliable recipes, rather than finding 10 different custom solutions that may or may not be future-proof… Or maybe I should urge the authors of the above solutions to integrate their examples into the Codex, and see what happens ? Just a quick observation: If I wanted to get the next/previous posts, I would try with built-in WP functions first.I would start with> Now I have the two adjacents posts in the same category, and can go on to do what I want with them.Say: if ($prev_in_cat) echo $prev_in_cat->ID . \"\";if ($next_in_cat) echo $next_in_cat->ID . \"\"; getu previousu post（）和getu nextu post（）在WP中已经有很长一段时间了，它们在内联和法典中都有记录，我可以使用它们而不必担心兼容性。一般来说，当我不知道WP是否为我想要的东西提供内置功能时，我会说： http://phpdoc.wordpress.org/trunk/ …并搜索函数或API是否已经存在；函数和类名在大多数情况下是不言自明的。感谢Demetris的观察。内置的\"next/prev\"函数确实很有用，上面的小调整可能非常实用。但在某些情况下，例如一个CMS类的网站，强烈依赖于类别，有必要能够显示一个完整的类别列表。我不知道phpdoc子网站，所以谢谢你让我知道！关于我提到的WP 3.1问题，看起来它们都与影响get_category功能的修改有关…请参阅http://core.trac.wordpress.org/ticket/15442所以我想我们只能拭目以待了。啊哈！这就解释了谢谢。谢谢用于指出问题。损坏的功能是有文档记录的功能，因此，我想，迟早会提供修复。干杯！很高兴看到这些问题已经在今天的3.1-beta1-16884中解决了！

WordPress相邻岗位的职能，被3.1-beta1打破

admin_action_{$_REQUEST[‘action’]}

admin_footer-{$GLOBALS[‘hook_suffix’]}

customize_save_{$this->id_data[‘base’]}

customize_value_{$this->id_data[‘base’]}

get_comment_author_url

network_admin_edit_{$_GET[‘action’]}

network_sites_updated_message_{$_GET[‘updated’]}

pre_wp_is_site_initialized

WordPress 的SEO 教学：如何在网站中加入关键字（Meta Keywords）与Meta 描述（Meta Description）？

谷歌的SEO是什么