Yes, its finally here. I know many of you have been anxiously awaiting some guidance on how to use WP User Frontend PRO with woocommerce and allow users to post Products from frontend.

It is as simple as a pie.  It will however, require that you understand some simple things like how to install WordPress plugins and how to use Woocommerce. If you are not you will be with in this tutorial.

Step1: Get and Install Woocommerce and WP User Frontend PRO

Woocommerce is a very popular ecommerce platform and as you are here I assume you already know about it. If not check out their site here. Its Free and have a big, friendly community.

Ok lets start. First go to admin area then Plugins-> Add New

Search “Woocommerce” and you will get the plugin like bellow image.

Click on Install Now and you are done. It will promote you to install initial Woocommerce pages/templates just go through it.

Now, if you already bought and downloaded your WP User front end PRO copy , follow similar steps but choose Upload option.

Upload your wp user frontend PRO .zip file and click on Install Now button, you are ready to play.

Step 2: Create Pages – Edit Pages and Dashboard

First this first, many users get confuse about this. After install WP User Frontend PRO, create two initial pages.

1. Edit page – it requires when you allow users to edit their post or product.

To create a edit page go to Pages-> Add New

Now, put Short Code [wpuf_edit] and publish it.
Now, go to User Frotnend -> Settings from General Options select edit page.

However, if you don’t want to allow users to edit post/product after submission you can set editing option off from Settings -> Dashboard. Image bellow:

1. Dashboard:

To create a Dashboard page go to Pages -> Add New

Now, use shortcode [wpuf_dashboard post_type="product"]

It wills show all Woocommerce Products from that user.

Step 3: Configure User Frontend Forms

Now we are going to configure our very first form. Again from admin area User Frontend -> Forms -> Add Form

If you are not already familiar with WP User Frontend then I will recommend you to take few moments to get familiar with it.

Here I am going to discuss related to simple Woocommerce Product post only. But, you can do many other things and customize according to your requirements.

Form fields:

• Post title – It will be your product tittle
• Post Body – it will be your Products Description
• Featured Image – will be your product’s Main Image

Custom Taxonomies:

• product_type – what type of product it is. If you want to allow user to post just a simple product I will recommend you NOT to use this field. However, if you are building a digital or affiliate store play with it. I will show other types on my next tutorial.
• Product_cat – you can allow users to choose all categories or specify only one or couple by using Exclude Terms.

For a simple product these fields are enough for now.

Custom Fields:

• Text – Price.  Allow users to set their own price.

Use meta key: _price

• Image upload - allow user to add additional image. Currently only one image will works.

Metakey: _product_image_gallery

There are many settings options under forms post settings, edit settings, notification settings. Please take few moments to configure these as your requirements.

Now publish your Form.  Go to User Frontend -> Forms and get your form’s Shortcode . Image bellow :

Finally, Create another page and use this form Shortcode. Now your users can post products in to your e-commerce site and manage them from their Dashboard.

That’s all for today.  I will come with more advanced like – Downloadable product and others in next tutorials.

If you have any question or require support post your topic in our support forum here.

Action hook field is a very extensive solution when you are building your own form controls. When the built-in custom fields in the plugin aren’t helpful, you can render your own fields in the form using the Action Hook field.

Step 1: Give the action a name

Now you can add your own functions on this hook.

Step 2: Binding your functions to the hook

Now that we’ve a hook name, we can bind our functions to this action hook

/**
* Add the input field to the form
*
* @param int $form_id
* @param null|int $post_id
* @param array $form_settings
*/
function render_my_awesome_hook( $form_id, $post_id, $form_settings ) {
    $value = '';
 
    if ( $post_id ) {
        $value = get_post_meta( $post_id, 'your_meta_key', true );
    }
    ?>
 
    <div class="wpuf-label">
        <label>A demo field</label>
    </div>
 
    <div class="wpuf-fields">
        <input type="text" name="my_custom_field" value="<?php echo esc_attr( $value ); ?>">
    </div>
    <?php
}

add_action( 'my_awesome_hook', 'render_my_awesome_hook', 10, 3 );

Here we are adding a function render_my_awesome_hook to our hook my_awesome_hook. We get 3 parameters with that action

• $form_id – The form ID of the form
• $post_id – The post ID. If we are creating a new post, it becomes NULL. If we are editing a post, it gives us the post ID
• $form_settings – The settings of our current form as an array

So basically we are adding text input field to that form. We can add more complex fields if we want

Step 3: Saving our input

Now that we’ve added our form input, it’s time to save those data when submitting the form. WP User Frontend gives you two useful action hooks: 1) when a post is submitted, 2) When a post is updated.

1) When a post is submitted, the wpuf_add_post_after_insert action runs.
2) When a post is updated, the wpuf_edit_post_after_update action runs.

So we bind a function to those hooks and save our input.

/**
 * Update the custom field when the form submits
 *
 * @param type $post_id
 */
function update_my_brand_new_hook( $post_id ) {
    if ( isset( $_POST['my_custom_field'] ) ) {
        update_post_meta( $post_id, 'your_meta_key', $_POST['my_custom_field'] );
    }
}
 
add_action( 'wpuf_add_post_after_insert', 'update_my_brand_new_hook' );
add_action( 'wpuf_edit_post_after_update', 'update_my_brand_new_hook' );

Thats it, easy and fun!

Many people asked us about Image Watermark feature for WP User Frotnend PRO plugin. Well, there are few plugins already out there can do the job for you.

In this tutorial i will show you how to use Image or Text watermark with WP UserFrotnend plugin.

I had a look on couple of plugins – Transparent Image Watermark, Simple Watermark, Bulk Watermark, Easy Watermark, Image Watermark and Watermark RELOADED. All these are free in WordPress plugins repo and at the end i will recommend to use Transparent Image Watermark. It works perfectly with WP UserFrotnend and according to its Author i believe it will shuit with any WordPress projects.

Install and Configure:

To use Transparent Image Watermark is pretty easy and straight forward. Go to Admin area -> Plugins -> Add New now, search with name “Transparent Image Watermark” you will get the plugin like bellow image and click on Install Now.

Lets Configure it . Go to Settings -> Transparent Watermark

• You can choose Watermark Type – Image or Text ,
• There are more options for update version but, free version can do our job so, its up to you
• Images Sizes – I will recommend you to sellect all
• Under Image Watermark tab – you have to insert your watermark image URL or Relative path.

Things to consider:

• If you use Image as watermark make sure its transparent and PNG format
• Make sure you put right image URL or Relative Path. You can check it under Watermark Preiew tab

Thats all. You are ready to use watermark image feature.

If you have any question ask on our Support Forum.

User Approval system is one of the most requested features we recieved to include with WP User Frontend PRO plugin by default. Well We are not considering it to be included with WPUF.Cause there are few awesome plugins already been out who can do the job for you.

In this post i will introduce to you couple of them. One is my favouraite WP Approve User and another one New User Approve. Well both of them are available at WordPress plugins repo and they are free.

Among these plugins, i will recommend WP Approve User, cause author of this plugin updates it frequently and according to description it is Compatible up to WordPress version 3.6 ! . I tested this plugin with WPUF Pro and works like champ !

Features:

• Dutch
• Deutsch
• Hebrew
• Persian
• Russian

Hope you find these plugin helpful for your site. We are here to help you if you require any help.

You can add your own dashboard columns to the WP User Frontends dashboard table.

Adding Column Header

It provides a action hook wpuf_dashboard_head_col, using this you can add a column:

/**
 * Add a new column header in dashboard table
 *
 * @param array $args dashboard query arguments
 * @return void
 */
function wpufe_dashboard_change_head( $args ) {
    printf( '<th>%s</th>', __( 'Sub Title', 'wpuf' ) );
}

add_action( 'wpuf_dashboard_head_col', 'wpufe_dashboard_change_head' );

Adding table rows

Now, you add your row via wpuf_dashboard_row_col, which provides two parameters: $args and $post.

/**
 * Add a new table cell to the dashboard table rows.
 * It adds a form for changing the post status of each posts via ajax call.
 *
 * @param array $args dashboard query arguments
 * @param object $post current rows post object
 * @return void
 */
function wpufe_dashboard_row_col( $args, $post ) {
    ?>
    <td>
        <?php
        if ( $sub = get_post_meta( $post->ID, 'subhead', true ) ) {
            echo $sub;
        } else {
            echo '---';
        }
        ?>
    </td>
    <?php
}

add_action( 'wpuf_dashboard_row_col', 'wpufe_dashboard_row_col', 10, 2 );

If you’ve turned ON the image option in dashboard and you don’t have any featured image, you get a default image in the dashboard.

If you want to add your own custom image, there is a filter wpuf_no_image. You just need to return the image URL to change the image.

function wpufe_dashboard_default_image() {
    return 'http://placehold.it/120x90';
}

add_filter( 'wpuf_no_image', 'wpufe_dashboard_default_image' );

If you want to insert WooCommerce product image gallery via WP User Frontend PRO, you’ll see only 1 image shows in the gallery. WooCommerce uses _product_image_gallery custom field to store the image gallery. It stores those images/attachments IDs separated by comma. Ex: 32,34,3874 in that single custom field. WP User Frontend PRO stores also the images/attachments IDs, but in the same meta key, but separately. For example:

'_image_gallery' => 383
'_image_gallery' => 345

To solve this issue, we’ll be adding a image upload field in the form editor with a different name (that woocommerce doesn’t uses).

Here we are using _product_image meta key to store the image for product gallery. The trick is, we’ll save the image IDs to the WooCommerce’s _product_image_gallery meta key when we hit submit/update button in our form.

/**
* Update the custom field when the form submits
*
* @param type $post_id
*/
function wpuf_woo_product_gallery( $post_id ) {
    if ( isset( $_POST['wpuf_files']['_product_image'] ) ) {

        $images = get_post_meta($post_id, '_product_image' );
        update_post_meta( $post_id, '_product_image_gallery', implode(',', $images) );
    }
}

add_action( 'wpuf_add_post_after_insert', 'wpuf_woo_product_gallery' );
add_action( 'wpuf_edit_post_after_update', 'wpuf_woo_product_gallery' );

Paste the code in your themes functions.php and your product gallery will be showing perfectly.

You can’t create WooCommerce downloadable right out-of-the-box with WP User Frontend PRO because WooCommerce saves the downloadable file paths in an array. But WP User Frontend saves files/attachments ID’s in custom field. So we need a special tweaking to save them in the array.

Here we are adding a file upload field in our form and we are giving the meta key as woo_files. You can change it as you want, but the code reference should be changed according to that also.

function wpufe_woo_file_paths( $post_id ) {
    if ( isset( $_POST['wpuf_files']['woo_files'] ) ) {
        $files = $_POST['wpuf_files']['woo_files'];
        $woo_files = array();

        foreach ($files as $file_id) {
            $file_url = wp_get_attachment_url( $file_id );
            $woo_files[md5( $file_url )] = $file_url;
        }

        update_post_meta( $post_id, '_file_paths', $woo_files );
    }
}

add_action( 'wpuf_add_post_after_insert', 'wpufe_woo_file_paths' );
add_action( 'wpuf_edit_post_after_update', 'wpufe_woo_file_paths' );

When we are creating or updating the the product, we are saving the file URL’s in WooCommerces files meta key _file_paths.

We need to insert a hidden field with meta key _downloadable and value should be yes, that will make the product as downloadable. Simple enough

Limiting characters is a required feature, but due to some problem in TinyMCE integration, the feature has been left out from WP User Frontend PRO. But it’s very easy to do that in text input and normal textareas. Here’s how you can do this.

Step 1: Initialize

We will first add this snippet in our themes functions.php, this will do the limitations.

function wpufe_limit_text() {
	?>
	<script type="text/javascript">
		(function($) {

			function limitText(field, maxChar){
			    var ref = $(field),
			        val = ref.val();

			    if ( val.length >= maxChar ) {
			        ref.val(val.substr(0, maxChar));
			    }
			}
      
      		// Insert Limitations here

		})(jQuery);
	</script>
	<?php
}

add_action( 'wp_footer', 'wpufe_limit_text' );

Step 2: Adding the limitations

We’ve mainly added the necessary code above, now it’s time to tell the code which fields to limit.

Every text input and textarea fields in WPUF has an unique ID and we can identify each fields by their ID. Every ID of custom fields is the same as their meta_key. If you are not sure the ID of a field, you can see your page source code (right click and View Page Source) and find the ID.

Now as we’ve grabbed the CSS ID, in this case textarea_limit of a field, now we can add a limit on that field so that users won’t be able to enter more characters than we allow them.

$('#textarea_limit').on('keyup', function() {
    limitText(this, 10)
});

Insert this code after // Insert Limitations here in that code. Here we are adding a limitation of 10 characters in the textarea_limit ID (note the # (hash) sign, it must be before the ID).

Step 3: Finally!

So the full code will be (includes another field also with a ID user_bio):

function wpufe_limit_text() {
	?>
	<script type="text/javascript">
		(function($) {

			function limitText(field, maxChar){
			    var ref = $(field),
			        val = ref.val();

			    if ( val.length >= maxChar ) {
			        ref.val(val.substr(0, maxChar));
			    }
			}

            // Insert Limitations here
            $('#textarea_limit').on('keyup', function() {
                limitText(this, 10)
            });
      
      		$('#user_bio').on('keyup', function() {
                limitText(this, 250)
            });

		})(jQuery);
	</script>
	<?php
}

add_action( 'wp_footer', 'wpufe_limit_text' );

In this way, we could add limitations on various fields.

After submitting a post or after editing post when clicking on the SAVE button the animation with the turning circle is endlessly visible while the post has been saved already.

Few times we get this question, here’s a answer for it.

Guest Post

Users can now post in your site without registering themeselves. You can enable guest posting by going a forms “Post Settings > Enable Guest Post“.

Auto user registration

Users can submit post without registration, but you can auto register themselves by enabling “Require Name and Email address“. That way, users will need to provide their Name and E-mail address. Upon providing their details, they will be auto registered in your site as a user. Their email address will be used to generate username, if a user already exists with the same username, a random number will be appended to their username. If a user already exists with the same e-mail address, the post will assign to that existing user.

The post 7. Guest Posting appeared first on weDevs Documentation.

Post subscription and payment system is a module where you can add paid posting system with WP User Frontend. You can introduce two types of payment system. Pay per post and subscription pack based.

Pay Per Post

With this you can introduce pay per post feature where users pay to publish their posts each post. When pay per post is enabled from “Settings > Payments > Charge for posting“, users see a notice right before the post creation form in frontend about payment. When the submits a post, the post status gets pending and he is redirected to the payment page (to setup the payment page, create a Page Payment and select the page at “Settings > Payments > Payment Page“. No shortcode is needed). Currently by default PayPal is only supported gateway. Upon selecting PayPal, he is redirected to PayPal for payment. After successful payment he is redirected back to the site and the post gets published.

Subscription Pack

There is an another option for charged posting. With this feature, you can create unlimited subscription pack. In each pack, you can configure the number of posts, validity date and the cost.

When a user buys a subscription package, he gets to create some posts (e.g. 10) in X days (e.g: 30 days). If he crosses the number of posts or the validity date, he can’t post again. You can force the user to buy a pack before posting “Settings > Payments > Force pack purchase“.

To show the subscription packs in a page, you can use the shortcode: [wpuf_sub_pack]. To show the user subscription info: [wpuf_sub_info]. The info will show the user about his pack left post cound and expiration date of his pack

Payment Gateway

Currently only PayPal basic gateway is supported. The plugin is extension aware, that means other gateways can be integrated.

The post 8. Subscription & Payment appeared first on weDevs Documentation.

There is an element on the Form Elements called Action Hook. This is a great addition for developers to extend the form as they want. It’s a placeholder for creating their own hook where they could bind their functions and generate their own dynamic element.

Usage:

add_action('HOOK_NAME', 'your_function_name', 10, 3 );
function your_function_name( $form_id, $post_id, $form_settings ) {
    // do what ever you want
}

Parameters:

• $form_id : (integer) The ID of the form
• $post_id : NULL or (integer) the ID of the post. When creating a new post, the parameter becomes NULL. When editing a post, you get the edited post ID as the parameter
• $form_settings : (array) An array of form settings

Example:

Here we have added a new action hook field called my_brand_new_hook and saving our field informations in a meta key named your_meta_key. We are adding the field into the form with the your_function_name function and updating the form value with update_my_brand_new_hook

/**
 * Add the input field to the form
 * 
 * @param int $form_id
 * @param null|int $post_id
 * @param array $form_settings
 */
function your_function_name( $form_id, $post_id, $form_settings ) {
    $value = '';

    if ( $post_id ) {
        $value = get_post_meta( $post_id, 'your_meta_key', true );
    }
    ?>

    <div class="wpuf-label">
        <label>A demo field</label>
    </div>

    <div class="wpuf-fields">
        <input type="text" name="my_custom_field" value="<?php echo esc_attr( $value ); ?>">
    </div>
    <?php
}

add_action( 'my_brand_new_hook', 'your_function_name', 10, 3 );

/**
 * Update the custom field when the form submits
 * 
 * @param type $post_id
 */
function update_my_brand_new_hook( $post_id ) {
    if ( isset( $_POST['my_custom_field'] ) ) {
        update_post_meta( $post_id, 'your_meta_key', $_POST['my_custom_field'] );
    }
}

add_action( 'wpuf_add_post_after_insert', 'update_my_brand_new_hook' );
add_action( 'wpuf_edit_post_after_update', 'update_my_brand_new_hook' );

The post Action Hook Field appeared first on weDevs Documentation.

Called at top of the form in front-end.

Accepts 2 Parameters.

• $form_id (integer)
• $form_settings (array)

The post wpuf_add_post_form_top appeared first on weDevs Documentation.

If you like Pronamic Google Maps and want to use along with WP User Frontend PRO, then there is a solution. You can still use the WP User Frontend’s Google Map custom field and using the function below, that would also update the pronamic plugins google map latitude and longitude and will work seamlessly.

function wpuf_pronamic_location( $post_id ) {
    $custom_field = 'address';

    if ( !class_exists('Pronamic_Google_Maps_Post') ) {
        return;
    }

    if ( isset( $_POST[$custom_field] ) ) {
        $address = $_POST[$custom_field];

        list( $def_lat, $def_long ) = explode( ',', $address );

        if ( $def_lat ) {
            update_post_meta( $post_id, Pronamic_Google_Maps_Post::META_KEY_LATITUDE, $def_lat );
        }

        if ( $def_long ) {
            update_post_meta( $post_id, Pronamic_Google_Maps_Post::META_KEY_LONGITUDE, $def_long );
        }

        if ( $def_lat && $def_long ) {
            update_post_meta( $post_id, Pronamic_Google_Maps_Post::META_KEY_ACTIVE, true );
        }
    }
}

add_action( 'wpuf_add_post_after_insert', 'wpuf_pronamic_location' );
add_action( 'wpuf_edit_post_after_update', 'wpuf_pronamic_location' );

The post Pronamic Google Maps appeared first on weDevs Documentation.

Integration between Good Writer Checkify.

function gwc_add_post( $form_id, $post_id ) {

    if (!$post_id) {
        $post = new stdClass;
        $post->ID = 0;
        $post->post_title = '';
        $post = new WP_Post( $post );
    } else {
        $post = get_post( $post_id );
    }

    Good_Writer_Checkify_Options::gwc_print_div_carousel( $post );
}

add_action( 'wpuf_add_post_form_bottom', 'gwc_add_post', 10, 2 );
add_action( 'wpuf_edit_post_form_bottom', 'gwc_add_post', 10, 2 );

The post Good Writer Checkify appeared first on weDevs Documentation.

This is an integration with WP Geo plugin.

Paste this snippet in your themes functions.php and insert a google map field with meta key location_map. If you want to put geo title, insert a custom text field with the meta key geo_title in the form.

function wpufe_update_wp_geo( $post_id ) {
    if ( isset( $_POST['location_map'] ) ) {
        list( $lat, $long ) = explode(',', $_POST['location_map']);

        update_post_meta( $post_id, WPGEO_LATITUDE_META, $lat );
        update_post_meta( $post_id, WPGEO_LONGITUDE_META, $long );
    }

    if ( isset( $_POST['geo_title'] ) ) {
        update_post_meta( $post_id, WPGEO_TITLE_META, $_POST['geo_title'] );
    }
}

add_action( 'wpuf_add_post_after_insert', 'wpufe_update_wp_geo' );
add_action( 'wpuf_edit_post_after_update', 'wpufe_update_wp_geo' );

The post WP Geo appeared first on weDevs Documentation.

Q. I get the message: “I don’t know how to edit this post, I don’t have the form ID”

Ans: When you create a post with the new version of WP User Frontend, a form ID is being attached to that post. It’s needed because you might have 10 forms and it doesn’t know which form should be used to edit that post.

For this problem with older posts, one thing you need to do. If you go the those posts edit screen in backend, you’ll see a meta box “WPUF Form”, select the form that should be used to edit the form.

Q. Where does the user registration and profile information saves?

Ans: It’s just the standard user meta fields. They are saved with meta_key you provide. You can pull the informations by this: <?php echo get_user_meta( $user_id, 'meta_key', true ); ?>

Q. How do I show the images/files in my theme?

Ans: Just use this snippet:

$images = get_post_meta( $post->ID, 'mey_key_name' );

if ($images) {
    foreach ($images as $attachment_id) {
        $thumb = wp_get_attachment_image( $attachment_id, 'thumbnail' );
        $full_size = wp_get_attachment_url( $attachment_id );

        printf( '<a href="%s">%s</a>', $full_size, $thumb );
    }
}

Q. What if I buy the personal package and use it on unlimited site?

Ans: You can do that, we’ll not restrict you to use it on several sites. But depending on the package you purchase, you are given a license code. The license code is neccessary for to receive auto updates and support. If you use it on multiple sites, you’ll not receive any further updates and support.

Q. Whats the facility of the developer package?

Ans: Using the developer package, you can use it on unlimited sites, priority support and free add-ons.

Q. Whats the license of WP User Frontend PRO?

Ans: We are using the same licensing policy as WordPress offers, GPLv2 (or later).

Q. What happens after 1 year period?

Ans: You are buying the plugin with 1 year free support and updates. After 1 year, depending on your purchased package, to get update and support again, you’ve to renew your license each year. The renewal fee for personal package is $29, business: $49 and developer license is $79.

The post FAQ appeared first on weDevs Documentation.

version 2.1.9

date: 9 January, 2014

 * [fix] PayPal payment problem fixed.
 * [updated] New version of Settings API class

version 2.1.8

date: 18 September, 2013

 * [new] associate uploaded images to post area
 * [new] tags autocomplete 
 * [new] default post form assignment
 * [new] taxonomy exclude/include/child_of feature
 * [new] free subscription option
 * [new] new edit post status "No Change"
 * [new] delete transaction option
 * [new] signup page override redirection
 * [new] insert photo: image size selection
 * [new] insert photo: type of image selection
 * [new] "pending" post edit enable/disable option

version 2.1.6

date: 22 June, 2013

* [fix] rich textarea post draft bug fix
* [fix] checkbox help text was left out
* [fix] help text for radio field
* [improve] map short code updated and separated to user and post map functions
* [new] non hierarchical taxonomy update support
* [new] theme my login custom email notification action hook fire
* [new] wp cli compatibility
* [new] hidden custom field
* [new] custom taxonomy text input field type added

version 2.1.5

date: 22 May, 2013

* [fix] Comment form fix in dashboard
* [fix] Google map fix in admin edit post area
* [fix] insufficient arguments in admin profile area
* [fix] feature image delete bug in edit post area
* [improve] multisite license notice fix
* [new] dashboard unauthorized message
* [new] not logged in message in user profile form
* [improve] updated language file

version 2.1.4

date: 27 April, 2013

* [bugfix] edit post permission checking
* [bugfix] WYSIWYG Text cut off after using "&"
* [improve] user avatar image url changed from relative to full url. fixes multisite bug
* [improve] `wpuf_can_post` filter gets more parameters
* [improve] repeatable fields separator changed from comma(,) to pipe(|)
* [improve] featured image in dashboard is now linked to posts
* [new] google map autocomplete address feature
* [new] file links added in admin panel post edit custom fields area
* [new] payment gateway bank added
* [new] validation filter added on new/edit post: `wpuf_update_post_validate`, `wpuf_add_post_validate`
* [new] private post status added on dashboard query
* [new] dashboard table hooks added: wpuf_dashboard_head_col, wpuf_dashboard_row_col
* [new] post draft option added. posts now can set to draft for later usage
* [new] default post category option
* [new] dashboard query filter added: `wpuf_dashboard_query`
* [new] teeny rich textarea added

version 2.1.3

date: 18 April, 2013

* [bugfix] comment issue fixed
* [bugfix] date issue fixed
* [bugfix] post author changed
* [new] taxonomy ORDER option
* [new] taxonomy ORDER BY option.
* [new] post format support
* [new] user registration filter
* [new] user registration after filter
* [update] file upload size changed to KiloByte

version 2.1.2

date: 5 April, 2013

* [bugfix] post edit area captcha fix
* [bugifx] Featured default image path fix
* [new] Show post status filter added
* [new] Dashboard query filter added
* [improve] *From* typo fix in editor
* [improve] It won't slow down your site now.

version 2.1.1

date: 23 March, 2013

* [bugfix] License check bug fix

version 2.1

date: 22 March, 2013

* Subscription feature put back
* Auto update feature

The post Changelog appeared first on weDevs Documentation.

The post Setting up the plugin appeared first on weDevs Documentation.