WordPress Custom Post Types Get Into The Loop

WordPress started a new era with the Custom Post Types for developers in the WordPress environment. The possibilities are numerous and primarily from the knowledge of the developer dependent. Nevertheless, there are so many tutorials how to use Custom Post Types in WordPress, but that is not enough - at least not in most cases and therefore are various other steps necessary to make the use of CPT more efficient and smooth.

In this article I would like to briefly explain how to get content of Custom Post Types in the loop of WordPress. This is not a complete guide, but please feel free to add tips, critics, hints in our comment area.

Continue reading …

New Plugin to Style your Plugin on WordPress Admin with Default Styles!

WordPress is developing fast - this also applies to the design of the backend. So it is important not to use your own styles in the admin area and use tags and classes of WordPress. This is the best way you can simplify your work as a developer and you don't have to test the design with every update. Unfortunately, there are quite extensive opportunities in the backend to implement the requirements. Several different classes and HTML structures are used. To be able to look up something this simple, I have developed a small Plugin, which tinkers in the development environment and quickly represents the necessary elements. Here you see two screenshots with the differences between version 3.1 and 3.2 of WordPress and the current contained elements of the Plugin.
Continue reading …

WordPress MultiSite, Plugins and Activation

WordPress offers for normal Plugins the hook register_activation_hook();. This is active right after the activation of a Plugin, so you can start small installation scripts. But if we are in a MultiSite environment (old: MultiUser) and put the Plugin in the folder wp-content/mu-plugins, then the hook doesn't do anything, because the Plugin is automatically activated. But there are few ways you can still have a kind of activation hook. One is this option:

if ( ! class_exists( 'my_mu_plugin' ) ) {

    if ( function_exists( 'add_action' ) ) {
        add_action( 'plugins_loaded' ,  array( 'my_mu_plugin', 'get_object' ) );
    class my_mu_plugin {

        static private $classobj = NULL;

        public function get_object () {
            if ( NULL === self :: $classobj ) {
                self :: $classobj = new self;
            return self :: $classobj;
        public function __construct () {
            // Fake-Activation-Hook
        private function activation () {
            if ( 'activated' == get_blog_option( 1, 'my_mu_plugin_activated' ) ) {
                // Do Stuff during activation
                // Update Option
                update_blog_option( 1, 'my_mu_plugin_activated', 'activated' );



We are doing the following: We check whether a certain option is set in blog 1, if not, then run through an activation function, otherwise do nothing - Blog 1 simple so that the install script is only in blog 1 in use. If you want to use it in all the blogs then simply use the function get_option(). Easy, right?

Guest Post

This post is written by Thomas Herzog - hughwillfayle.de and is a guest post on WP Engineer about WordPress.
Thank you very much from my part to Thomas. Please see his nice plugins on the official WordPress repository.
If you also like to have your interesting post published on our website, please let us know on our contact page. Of course we will appreciate your contribution!