User:

From: myBlog (info@myBlog.com)
Subject: [myBlog] Your username and password info

Username: new_user

To set your password, visit the following address:<http://myblog/wp-login.php?action=rp&key=3oCJkevP1ZSSb0P8DlOW&login=new_user>

http://myblog/wp-login.php

Admin:

From: myBlog (info@myBlog.com)
Subject: [myBlog] New User Registration

New user registration on your site myBlog:

Username: new_user

Email: new_user@myblog.com

Until version 4.8 the content of the mail was hard coded. The only way to alter the emails was to hook into wp_mail() or even phpmailer.

WordPress v4.9 now offers the ability to easily customize these emails by using the following filters:

• wp_new_user_notification_email
• wp_new_user_notification_email_admin

The filters fire after the user has been added to the database.

The filters for the user’s and the admin’s email follow the same logic, just the filter and the variable names differ:

$wp_new_user_notification_email_admin = apply_filters( 'wp_new_user_notification_email_admin', $wp_new_user_notification_email_admin, $user, $blogname )

The parameters contain the following values:

• $wp_new_user_notification_email_admin: Associative array with the keys to, subject, message, headers.
• $user: A WP_User object of the registered user.
• $blogname: A string containing the name of the blog the user registered to.

With these values at hand it’s easy to create your customized mail:

add_action( 'login_init', 'my_wp_new_user_notification_email_admin_init' );

function my_wp_new_user_notification_email_admin_init() {
    add_filter( 'wp_new_user_notification_email_admin', 'my_wp_new_user_notification_email_admin', 10, 3 );
}

function my_wp_new_user_notification_email_admin( $wp_new_user_notification_email, $user, $blogname ) {
    $wp_new_user_notification_email['subject'] = sprintf( '[%s] New user %s registered.', $blogname, $user->user_login );
    $wp_new_user_notification_email['message'] = sprintf( "%s ( %s ) has registerd to your blog %s.", $user->user_login, $user->user_email, $blogname );

    return $wp_new_user_notification_email;

}

(As always for filters: do not forget to return the altered variable.)  The mail now looks like this:

From: myBlog (MyBlog@myblog.com)
Subject: [myBlog] New user new_user registered.

new_user (new_user@user.com) has registerd to your blog myBlog.

Of course, you can insert more data than is provided by the filter. E.g., you can tell the admin, how many registered users the blog already has:

function my_wp_new_user_notification_email_admin($wp_new_user_notification_email, $user, $blogname) {

    $user_count = count_users();

    $wp_new_user_notification_email['subject'] = sprintf('[%s] New user %s registered.',
$blogname, $user->user_login);
    $wp_new_user_notification_email['message'] =
    sprintf( "%s has registerd to your blog %s.", $user->user_login, $blogname) .
"\n\n\r" . sprintf("This is your %d. user!", $user_count['total_users']);

    return $wp_new_user_notification_email;

}

The parameter headers can be used to change some header information easily:

In this example, the From information of the mail is changed and the user admin2@myblog is added as an additional recipient. As you can see, multiple headers entries are separated by "\n\r" (return and linefeed).

$wp_new_user_notification_email['headers'] = "From: myBlog <myblog@myblog.com> \n\r cc: Admin 2 <admin2@mblog.com>";

As said before, this all could already be done by using wp_mail() and phpmailer but the new filters are way more convenient.

Note. The strings are \n and \r in the code means.

• \r is the carriage return
• \n is the new line

On the right side of the plugin’s page there a link called “Advanced View”, which should better be called “Version View”:

Very, very (very) far at the end of the page there a dropdown box where you can select the desired version and click “Download” the get the desired version:

Including version 4.6 it was quite difficult to add custom bulk actions to the WordPress admin pages. In version 4.7 a hook is added that simplifies the task a lot:

add_action('bulk_actions-{screen_id}', 'my_bulk_action');

Defining the hook

As an example we’ll use the post page, the variables are named accordingly.

add_filter( 'bulk_actions-edit-post', 'register_my_bulk_actions' );

Definig the hook

function register_my_bulk_actions($bulk_actions) {
  $bulk_actions['my_bulk_action'] = __( 'My Bulk Action', 'domain');
  $bulk_actions['my_other_bulk_action'] = __( 'My Other Bulk Action', 'domain');
  return $bulk_actions;
}

You can define more than one bulk action in this function because it merely adds an additional element to the array $bulk_actions. You simply have to take care that you use different names for the element keys and, logically, for the display texts.

The screen ids

The screen id of an admin page can be displayed this code snippet:

$screen = get_current_screen();
var_dump($screen);

This table shows the ids for some admin pages:

Defining the callback function

Here’s an overview of the whole function:

add_filter( 'handle_bulk_actions-edit-post', 'my_bulk_action_handler', 10, 3 );

function my_bulk_action_handler( $redirect_to, $action_name, $post_ids ) { 
  if ( 'my_bulk_action' === $action_name ) { 
    foreach ( $post_ids as $post_id ) { 
      $post = get_post($post_id); 
      // process $post wp_update_post($post); 
    } 
    $redirect_to = add_query_arg( 'bulk_posts_processed', count( $post_ids ), $redirect_to ); 
    return $redirect_to; 
  } 

  elseif ( 'my_other_bulk_action' === $action_name ) { 
    foreach ( $post_ids as $post_id ) { 
      $post_meta = get_post_meta( $post_id ); 
      // process $post_meta update_post_meta( $post_meta ); 
    } 
    $redirect_to = add_query_arg( 'other_bulk_posts_precessed', count( $post_ids ), $redirect_to );
    return $redirect_to; 
  } 
  
  else 
    return $redirect_to; } 

As mentioned above you can define more than one custom bulk action but only a single callback function. So you first have to test which bulk action has been selected (lines 4 and 13).

Next the posts are processed in a foreach loop (lines 5 and 14). In this loop you can load the post with get_post or the post meta with get_post_meta() and process the data. Next the changed data is written back to the database with wp_update_post() or update_post_meta().

The variable $redirect_to (lines 9 and 18) is used to define the URL the browser will change to after the bulk actions have been completed, in our case it is set to .../wp-admin/edit.php?paged=1. We do not want to change the location but to use the variable to pass a value to the page the browser is redirected to.
With the function add_query_arg() we add an argument to the URL that specifies the number of processed posts: /wp-admin/edit.php?paged=1&bulk_posts_processed=1.

Display a success notification

After completing processing all posts you can display an admin notice using the action admin_notices(). The second parameter of the function call needs to contain the text string we have defined in our filter bulk_actions-{screen-id}:

function my_bulk_action_admin_notice() { 
  if ( ! empty( $_REQUEST['bulk_posts_processed'] ) ) { 
    $posts_count = intval( $_REQUEST['bulk_posts_processed'] ); printf( '
' . _n( 'Processed %s post.', 'Processed %s posts.', $posts_count, 'domain' ) . ' ', $posts_count ); 
  } 
} 

Trivia

A little fun fact at the end: The corresponding ticket (#16031) was opened six years ago, 2010, in that times we used WordPress v3.0.

… and your blog doesn’t work anymore

… and you have no backup

…

… of course not!

Wouldn’t it be nice if you could download the previous versions and get your blog back on track again? Well… you can!

Tell your browser to go to wordpress.org/plugins/<your_plugin> and navigate to the rightmost tab called “Developers” (1):

Here you can download every version of the plugin ever published to wordpress.org. Click on the version number to download the plugin as a ZIP file (2), use FTP to copy it to your server, and be happy again. Until next time.

Next week I will be at WordCamp San Francisco and a week later at the WooConf! Maybe one or antoher of our loyal readers will also be there. It would be great to meet you in person!

Frank and I had such a blast at WordCamp Europe in Sofia last month. It was great to meet many of our old WordPress buddies and get to know even more WodPress freaks there.

We also had the chance to show many people the newest version of our Multlingual WordPress plugin MultlingualPress. Everybody was very excited about it. Because it is a clean solution without any performance issues. It is very userfriendly, build on existing core functionality, no compromises in SEO, etc. … see all features here.

Many people we talked to, had the problem, that they are tight to their current multilanguage solution. If they deactivate their plugin, the content is gone. Big issue if you want to move to a better performing solution. Very soon, it won’t be anymore, espacially with your help testing it. We are currently building a WPML importer to easily switch to MultlingualPress. Other importer will follow soon too.

There are two ways to win a pro plugin of MultilingualPress

We are looking for some engaging tester for our new WPML importer. If you participate, you can get our pro version for free. If you are interested please contact Frank directly at frank@bueltge.de, for more information read our post on Google+. We really appreciate your support!

On #WeSpeakWP we will have a little contest going for WordCamp San Francisco. Get a sticker in your language from me, if available, at WordCamp San Franciso or WooConf and post a photo/selfie with the sticker on Twitter. Not to forget with hashtag #WeSpeakWP ! The more fun and crazy the photos are, even better!

Of course there is also a free version available, so try it out. Here you can see the differences between the pro and free version. Not to forget, with the pro version you get an excellent support!

I’m really looking forward to meet you in San Francisco! Let me in our comments know if you will be there! Can’t wait!

To prevent spammers from flooding old articles with useless comments, you can set WordPress to close comments after a certain number of days:

It might be surprising for some users if the comments are closed automatically, so it might be a good idea to inform them about the remaining time.

add_action( 'comment_form_top', 'topic_closes_in' );

function topic_closes_in() {
    global $post;
    if ($post->comment_status == 'open') {
        $close_comments_days_old = get_option( 'close_comments_days_old' );
        $expires = strtotime( "{$post->post_date_gmt} GMT" ) +  $close_comments_days_old * DAY_IN_SECONDS;
        printf( __( '(This topic will automatically close in %s. )', 'domain' ),  human_time_diff( $expires ));
    }
}

While the code should be almost self explanatory there is an interesting function not every WordPress developer might know: human_time_diff(). This function is hidden in the .../wp-includes/formatting.php file. It is originally planned to be used in themes to provide a more “human” touch to the date/time a post was written. Since the function does not care if the date is in the past or in the future we can use it for our needs.

“Briefly unavailable for scheduled maintenance. Check back in a minute.”

This message is useful to keep users away from your blog during the upgrade but right now it’s keeping you from restarting the upgrade. To solve this problem we have to take a look at how WordPress determines that it’s in maintenance mode.

WordPress is looking for a possible maintenance mode very early to prevent the system dying from any fatal error. So it using a very simple method by writing a file called .maintenance to the WordPress root directory. If the blog or backend is accessed it will check for the file and stop if it’s present.

Knowing this the solution to our problem is quite simple: access your WordPress system via FTP and delete the file .maintenance.

If you’re not able to log in to your server via FTP for some reason there is a second method for escaping from maintenance mode: simply wait 10 minutes!
The file .maintenance contains a timestamp of the time the file was created. If this time is less than 10 minutes ago WordPress will go into maintenance mode otherwise it will continue to work as usual and enable you to restart the upgrade unless something worse keeps it from starting.

• automatic_updates_complete
  Action triggered after all automatic updates have run.
  (wp-admin/includes/class-wp-upgrader.php)
  

• automatic_updates_debug_email
  Filter the debug email that can be sent following an automatic background core update.
  (wp-admin/includes/class-wp-upgrader.php)
• comment_notification_notify_author
  Filter whether to notify comment authors of their comments on their own posts.
  (wp-includes/pluggable.php)
• dashboard_glance_items
  Include additional elements in the ‘At a Glance’ dashboard widget. This widget was previously ‘Right Now’.
  (wp-admin/includes/dashboard.php)
• user_{$name}_label
  Filter a user contactmethod label.
  (wp-admin/user-edit.php)
• wp_prepare_themes_for_js
  Filter the themes prepared for JavaScript, for themes.php. Could be useful for changing the order, which is by name by default.
  (wp-admin/includes/theme.php)

A list of all new hooks can you also find in the hot list of WP Seek.

]]> https://wpengineer.com/2656/new-hooks-in-wordpress-3-8/feed/ 8 https://wpengineer.com/2652/every-day-a-post-of-wordpress-tipps-and-tricks-until-christmas/ https://wpengineer.com/2652/every-day-a-post-of-wordpress-tipps-and-tricks-until-christmas/#comments Thu, 28 Nov 2013 14:51:16 +0000 http://wpengineer.com/?p=2652

The time has come and our loyal reader know already our traditional Advents Calendar. For the people who don’t know, every year we had in December each day, until the 24th (Christmas Eve in Germany), a post with specials, tips, tricks, plugins, tutorials and so on.

Since it is quite a lot work to accomplish 24 high quality posts, we asked some of the finest WordPress Experts in Germany if they would like to contribute some ideas and great posts to it every day.

We decided to put all the posts on the new marketpress.com blog, where you already can find some really interesting posts like:

Back to the Future – How wp_date_query Works!

Is there a maximum size for WooCommerce shops?

Extend WordPress User Roles: Theme Options for Editors

Code is poetry?

Ghost-Installation with Windows – What You Need to Know!

WordPress Backend Design Study

WordCamp Europe – Video Interviews with Matt, Otto and other Core Contributor

Deploying WordPress with Git and Capistrano

WordPress becomes 10 – free Infographic!

Multilingual WordPress with Multisite? Yes!

Creating and customizing Child Themes

So check out the daily posts on inpsyde.com and enjoy!

More information about this tradition and what you can expect for the next 24 days can be found here!

]]> https://wpengineer.com/2652/every-day-a-post-of-wordpress-tipps-and-tricks-until-christmas/feed/ 7 https://wpengineer.com/2639/download-wordpress-framework-for-free/ https://wpengineer.com/2639/download-wordpress-framework-for-free/#comments Mon, 28 Oct 2013 16:45:57 +0000 http://wpengineer.com/?p=2639 With pleasure we can now announce that Xtreme One 1.6 was released as a beta last week! Xtreme One WordPress Framework gives you the freedom to easily create your WordPress Themes. No more inflexible layouts or having to change the code all the time. With the powerful framework you are able to realize your ideas very quickly.

Xtreme One is the world’s only WordPress framework that allows solid, fluid and flexible layouts.

With Xtreme One 1.6 also comes the possibility to adapt Xtreme One Widgets to your own needs or create custom widgets, an example is supplied in /xtreme-blank/ Child Theme. The Grid post widgets now support custom post types. Therefore an infinite number of options are available with just a few clicks to reposition content.

Using the unique content widgets you can integrate any widget in the post editor. Of particular interest would it for portfolio websites, certain posts in multiple columns responsive and fluid.

Xtreme One comes with 15 awesome Widgets, try out all of them and you will be amazed!

You can find more information about the powerful WordPress Framework here!

Download and test it for free

Beta testing ends 30.11.2013!

]]> https://wpengineer.com/2639/download-wordpress-framework-for-free/feed/ 16