Plugin

Migrating a WordPress Website In Under 10 Minutes: The Ultimate Guide To The Duplicator Plugin

Thinking about migrating your WordPress site?

Most people aren’t aware of how they can migrate their site and then upon searching, they come across so many complex ways that they decide to not to do it altogether. But, then there are a few ways that can help you in moving the site to the server easily and that too within a matter of a few minutes. One such way is to use the amazing ‘Duplicator Plugin’. It not only helps to backup your site but works excellently when it comes to moving the WordPress site to a new server.

The most common issues that people tend to face when moving their WordPress site are permission errors, database import and export errors, file path issues and many others. Also, with new plugins, the issue of installing and setting them up is a huge roadblock. And this is where the Duplicator plugin stands out.

Rather than you having to do everything manually, the plugin does everything for you. Right from backing up the images, content, database, plugins etc, the Duplicator would literally do everything for you. The icing on the cake is the fact that the plugin is absolutely free to use.

Table of Contents

  1. What Does Duplicator Enable You to Do?
  2. Downloading, Installing and Activating the Duplicator Plugin
  3. Create a Site Package
  4. Preparing the New Server for Migration
  5. Installing the Package
  6. Troubleshooting

What Does Duplicator Enable You To Do?

With the help of this plugin, you can:

  • Move, clone or migrate a WordPress website between hosts and domains
  • Improve your workflow with the help of pre-bundled sites
  • Pull down a live site for the purpose of development to local host
  • Choose to manually backup a whole site or certain parts of it
  • Migrate a WordPress site entirely without having to struggle with almost incomprehensible import/export SQL scripts

Of course, it is quite easy to use the plugin but, for a first time user, the thing might get a bit baffling. Listed below are all the steps that you would need to follow so as to properly migrate your WordPress site to a different server.

1. Downloading, Installing and Activating the Duplicator Plugin

The Duplicator plugin can be installed directly from the dashboard of WordPress. Just visit your WordPress dashboard and under the plugin section, you would need to click on the ‘Add New’ button. There you would find the Search bar, wherein you should type ‘Duplicator’ there. The first search result that you get would most probably be the right one. Click on ‘Install Now’ and the plugin would start to download. Once it is downloaded, click on ‘Install now’. After that, ‘Activate’ the plugin.

2. Create a Site Package

migrating a wordpress site

After the plugin has been activated in the dashboard, you would be able to find a new option named ‘Duplicator’. Upon clicking on this, a setup screen would pop up with a  message saying that you haven’t created any packages yet. You would need to click on ‘Create New’ option which would allow you to create site packages.

However, there are certain requirements that need to be fulfilled before you can actually create a package. Most of them would have a pass but, in case it isn’t, you can click on to find out about the issue. Now, the name of the package would be pre-filled which you can change. Other than that, you could also create some notes about the package.

In the archive section, you would find a drop-down option from where you can change the file format. Below that, in the Installer section, you would have to mention information regarding the server that you would be moving your site to. You may or may not fill these right now as it is possible to edit the details later on.

migrating a wordpress site duplicator plugin

Now you would be directed to the ‘Scan’ option, which you may choose to skip. But it is good to scan as you would be able to know about the problems in your package. As you click on the next button, the plugin would scan the files, database and server. It is compulsory for all the checks to pass. As soon as the scan is complete, you can click on ‘Build’. This would back up your entire site including the pages, themes, posts as well as media. 

Once the build is completed, download buttons for the archive you created as a zip file and for the installer would show up. You would be required to download them. Once downloaded, the site package would be listed on the tab for packages along with the information related to date and size.

The process of backing up your site is done completely. Now, if you wish to migrate your site to another server, you would need to follow the below-listed steps.

3. Preparing the New Server for Migration

With the Duplicator plugin, you wouldn’t need to install WordPress on the new server. The plugin would do this for you and you would only be required to create a new user and database. The server that you want to move your WordPress site to would need to be connected via FTP and the installer along with the archive file in the zip format to be uploaded.

This would be done at the root location of your domain on the new server. However, you would need to manually set up the database for your new website. The process of doing this would be dependent on your web host. You would need to refer to their guide to finish creating a database. Once the database is created, you will have to add a user to the database with complete privileges.

Once all that is done, make sure that you note down your database host, username, database name and password as all these things would be required in the next step. Note down the database host if you are on a different server as that of your website.

4. Installing the Package

In your web browser, access your installer script by entering the URL of the new website. This URL would be followed by /installer.php. For instance, if the name of your new website is www.myWordPresssite.com, you would enter https://www.myWordPresssite.com/installer.php. 

Something like this would pop up and you would need to fill in all the information regarding the database that you just set up. You could also change the fields in the settings option if you wish to. After you have filled everything up, click on the ‘Test Connection’ option which would help in ensuring that the script can connect properly to the database. If everything is fine, you would notice a pop-up message that would tell you that the server has been found and that the script was connected to the database successfully.

In case, it doesn’t connect, you would need to contact your service provider or follow the instructions present under the common connection issues section. The next step would be to check the box that says that you have read all of the warnings and notices. Click on Install Now and wait for the Installation to be completed.

Once the installation is completed, the old and the new path would be displayed on a page. Here, you can create a new admin user and even add a page title if you want to. Click on the ‘Run Update’ button so as to update the database and finish the installation process. The final page would have a report consisting of the error and warning messages along with some steps that need to be finished before you can proceed to use your newly created site.

Finish off all the steps and delete the contents of the wp-snapshots in the source site. With this, you have now managed to successfully move your WordPress site to a new server.

5. Troubleshooting

If at the first time, the Duplicator doesn’t work, try to run it again. At times, the plugin might not work on the very first time but does work perfectly fine in the second time. Your experience of using this plugin would be dependent on the size of your WordPress site and database.

You can also try the Duplicator version if you feel that the free version has worked fine for you. The premium version is an advanced one and has scheduled cloud backups along with several other impressive features. The free version does work excellently well in duplicating and migrating your WordPress site to a new server.

How was your experience with the Duplicator plugin? Would you like to suggest some other ways to migrate a site? Share your thoughts with us below.

This post was written by Dev Sharma. He is the founder of WPKube, one of the world’s most popular Web Development/WordPress blogs. His work has been featured in numerous publications, including Social Media Examiner, Smart Insights, Virgin, Forbes, TNW, SEJ, Huff Post, Woorank, and many more.

The post Migrating a WordPress Website In Under 10 Minutes: The Ultimate Guide To The Duplicator Plugin appeared first on SpyreStudios.


SpyreStudios

7 Keys to Creating a Successful WordPress Plugin

wordpress plugin keys to success

If you want to build a software business, there are a lot of advantages to the world of WordPress plugins.

To begin with, you have a built-in audience of committed users. That audience is massive — around a quarter of the planet’s websites use WordPress. And that number is growing every day.

But we all know that “Build it and they will come” is a myth — for software or any other business.

There are tens of thousands of plugins with just a few downloads, and a few successful standouts.

Here’s how to put your awesome plugin in the second category.

#1: Start with the user experience

User experience should drive your code, not vice versa

Successful plugins are built on a foundation of excellent user experience.

WordPress expert and evangelist Chris Lema sees an awful lot of popular plugins.

He had this to say in his article on The one thing many WordPress plugin developers seem to forget:

“… Most developers seemed to think about the user experience only after most of the development of their plugins was complete.” – Chris Lema

His recommendations include:

  • Getting users involved early on — don’t try to design your plugin in a vacuum
  • Measuring the number of clicks to complete each main task — keep tasks as simple as possible
  • Designing the screens and experience before you write your code — experience should drive your code, not vice versa

Sometimes technical folks are tempted to start with the functionality first, then “figure out the user experience part” later. That’s a recipe for expensive mistakes and a less-than-awesome plugin.

#2: Design matters

Successful plugins leverage great design.

Starting with the user experience will get you a good way down this road, but if you aren’t a strongly visual person yourself, make sure you get one involved.

Even if your plugin works perfectly, it only makes it harder to get traction if it’s ugly and visually disorganized or cluttered.

It’s not about eye candy for its own sake — it’s about careful design thinking that reinforces your plugin’s functionality and makes it a pleasure to use.

#3: Serve a real need (or want)

Successful plugins address a real-world user problem or desire.

If you’re not building something WordPress publishers actually want, you’re going to have a tough time.

You may have a highly technical improvement that you’re sure all WordPress publishers should add to their sites. But if it’s solving a problem they don’t care about, you’ll never get any traction.

Get to know lots of WordPress users and you’ll quickly learn what they want from their sites. Great plugins usually make WordPress simpler or more powerful.

Some examples include:

  • More easily customizing the look of the site
  • Improving the site’s SEO
  • Enhancing the audience experience with community-building elements
  • Reducing spam
  • Adding a complex and desirable feature, like a membership site

If your plugin is on the technical side, remember to translate the benefits for non-techie users.

A plugin that “improves origin caching” is great, but make sure you also translate that to: “Makes your site load a lot faster.”

#4: Have skills (or know where to get them)

Successful plugins have rock-solid code.

If you’re new to programming, working on plugins can be a fun and interesting way to get better.

But if you want to create a truly great plugin, you need to pay your dues and become an excellent coder. (And no, this does not happen overnight.)

If that isn’t you yet, you can shortcut this by partnering with an excellent coder. You might supply the vision, the marketing mind, and the business knowledge, and they bring their sweet dev skills.

Solid developers don’t just write great code, they also work within a defined process to make sure they’re releasing a quality product.

“Beyond your standard programming best practices, I think the best thing to do is to test, test, and test. Keep up your code. Have development environments with commonly found themes and plugins. Test against different configurations. If it’s a commonly used theme (like Genesis), make sure it functions as expected and if not, see what needs to be done before releasing it.” – Andrew Norcross, founder of Reaktiv Studios

#5: Carve out your position

Successful plugins stake out clear positioning in the WordPress marketplace.

Just like any other software product or service, your plugin needs to occupy a well-defined position in the market.

You need to be able to communicate in an instant:

  • What your plugin does
  • Who it’s for
  • What specific and remarkable benefit it brings to sites

Keep the simplicity factor above in mind, if your plugin is intended to reach a broader audience than the most tech-savvy users.

#6: Consider working within an ecosystem

Successful plugins are part of a greater ecosystem.

Every WordPress plugin, of course, benefits from the overarching ecosystem of users and developers.

But in an era of so many plugins, many developers niche that down further, coding for a particular framework such as Genesis.

For example, one of Andrew Norcross’s most popular plugins is Genesis Design Palette Pro — that lets users change the look of their Genesis sites with just a click or two, without any coding.

You might think that working within a niche ecosystem would result in fewer users, but often the opposite is the case. You’ll stand out more easily, because you’re crafting more specific solutions to your users’ desires.

#7: Recognize the community

Successful plugin developers respect the WordPress community.

Along with the many benefits of the WordPress ecosystem, there are also community responsibilities.

Here’s how Andrew Norcross put it when I asked him about the importance of nurturing the relationship with the community:

“I firmly believe it means the difference between success and failure, overall. While you can easily make a living cranking out WP code in themes or plugins for clients or agencies, there’s a definite ceiling (in my opinion) with how far you can progress without being at least somewhat active in the community. More importantly, however, having a bad reputation can be a career killer. Many people put personal recommendations above all the marketing they see, and once someone develops a bad rep, it’s really hard to shake it. We’re beyond fortunate that at Reaktiv Studios, we have developed a solid reputation with our clients, in that many of our new leads are referrals from our previous clients.”
– Andrew Norcross, founder of Reaktiv Studios

Want some help with that?

cb-dca-wp

You may have seen Brian Clark mention last week that we have a brand-new course on how to create a successful WordPress-based product or business.

When we added this course to the schedule — even though we have a wealth of in-house WordPress knowledge — we knew we wanted Chris Lema to lead it for us. In addition to being a great teacher, Chris has worked with just about every significant WordPress company on the planet.

His detailed perspective on the WordPress premium market is even broader than ours, and his experience really shows.

Here’s what Chris covers in this brand-new course:

  • Understanding the Size of the WordPress Ecosystem
  • Determining Realistic Market Potential
  • Evaluating the Competition
  • Shaping Your Idea for the Win
  • Scoring Your Ideas for Validity
  • Understanding Estimated Cost and Potential Revenue
  • Building Your PR Channels
  • Finding and Hiring Developers
  • Buying a Product
  • Planning Your Launch

Snag the best price this week

Chris Lema’s course is just one of four in-depth courses in Digital Commerce Academy — with more courses to come, as well as case studies, group coaching calls, “cutting edge” sessions on new techniques, and more.

If you want to launch a digital business or grow the one you have, Digital Commerce Academy is the place to be.

You can get access two ways, both of which offer incredible value — but both of them are about to go away:

  1. Invest $ 395 for a year of full access to everything in Digital Commerce Academy. You remain at that pricing for additional years no matter how much the price rises and no matter how many new courses we add. Cancel any time and never be charged again.
  2. Register for our live Digital Commerce Summit happening October 13-14, 2016 in Denver, Colorado, and get your first year of Academy free. After the first free year, you’re grandfathered in at $ 395 for additional years no matter how much the price rises. Cancel any time and never be charged again.

On May 27, 2016, at 5:00 p.m. Pacific Time, the Academy-only price goes up to $ 595, and the free year of Academy bundled with the Summit will be eliminated. As always, we have a hassle-free and no-questions-asked 30-day money-back guarantee, so there’s no risk to you.

Want more details? Click here to get started.

The post 7 Keys to Creating a Successful WordPress Plugin appeared first on Copyblogger.


Copyblogger

This plugin for Chrome will shame you into ditching your Facebook habit


How often in a day do you find yourself mindlessly scrolling on Facebook when you could be doing something more productive, like work or sleeping? What exactly is it that we are all so enthralled by? Or is it just a habit we can’t seem to break. Some research even suggests that Facebook addictions trigger the same part of our brains as cocaine. So how do you break the habit? Well, have you ever thought about asking yourself why you open Facebook as often as you do? It’s a good idea and luckily, that’s exactly what the Focusbook Chrome plugin does.…

This story continues at The Next Web
Social Media – The Next Web

characterCounter: Building a Feather-Weight jQuery Character Counting Plugin

Have you ever received a long unwanted or overflowing email through your contact form? If yes, then no wonder you have either deleted it permanently or ignored it. Isn’t it a good idea that we allow our users to enter only an exact number of characters to keep their message concise? Just like Twitter, we can show them the number of characters entered so far, maximum limit of characters and even color when the user is near to the permissible limit.

The whole purpose of building this plugin isn’t to restrict users, rather to allow them to convey their thoughts within a certain number of characters. I bet that genuine user will definitely convey their message easily within the minimum characters.

How to Build a Character Counter Plugin

Benefits of limited characters

Get ‘to the point’ message, in this fast moving spammy world, we don’t have enough time to go through each and every email and read them line by line. Wouldn’t it be time-saving for both sender and receiver to write and read a brief and relevant email quickly?

It does not mean the end of long messages, if you are thinking that it will be the death of long messages then boy you are wrong. It will encourage users to show their creative side to put their point in a limited fashion and I’m sure that after receiving the message, your mode of communication will be direct rather than again using that form. So, at this point in time, you can start exchanging long emails (or essay in it :D)

This tutorial assumes that you have experience in integrating jQuery plugin as well as some knowledge of JavaScript and jQuery.

Let’s dirty our hand in code mud

For the sake of simplicity, I have divided the plugin into three parts viz. Properties (what a web developer will add), error handling (as a plugin developer, how will you handle errors) and finally visual feedback (what a user will see if she exceeds or gets near to the permissible limit).

I will walk through in the same order as we have discussed above. So let’s dive into the properties part first.

Properties

As a plugin developer, you should make fellow developers lives easy by sticking with development standards and keep things simple from the property’s names to their value.

As of now, we will talk about five important but essential properties. My plugin is available under the MIT license. Sorry for fancy word, let me simplify it. It means you can extend, break and play with my plugin and code without any restriction. So, this allows you to extend properties that may make sense in the future and distribute it. Let’s look at the role play by each property.

MaxLen [Mandatory]
As the name suggests, This mandatory property will be used to set maximum length. So, you can set to your own preference. You can take your lead from Twitter on your site by setting this to 160 characters.

warningLen [Mandatory]
This property will set visual feedback to numbers. So, if you have noticed on Twitter, it will show the remaining characters in rosewood color after 20 remaining characters (Ah, it mainly contains red color, what a fancy world). If you go to my personal website and check my contact form then you will notice that warningLen is 60 and MaxLen is 320 characters. Fair enough!

showMsg [Mandatory]
This is another mandatory property which is again useful for extra visual feedback. It basically allows you to set an alert message. It is directly associated with the next property i.e customMsg. If you set showMsg true, then you can set your custom alert message. Otherwise, it will take the default message.

Default message: “Oops, you are not allowed to enter more…”

customMsg [Optional]
Oh, finally an optional property. This will only work if you set showMsg true. So, now you have the power to add your own quirky message if you find my default message too boring.

separator [Optional]
This property will be used to separate the remaining characters with max length and purely for UI purposes. So, if you don’t set it then it will, by default use “|”, I call it a pipeline.

warningColor [Mandatory]
This last mandatory property will allow you to provide a color coded hint to your users. This is again for pure UI purposes. The nice thing is that you can use RGB, HEX or name of the color. It will work like a charm as far as jQuery supports that.

I hope you followed me so far. Let’s jump into the pure coding part. After reading the properties part, I know you are confident enough to put your hand more deeply into the mud (my bad, coding mud).

Error Handling

So I have divided this section into three parts from the variable declaration to sanity check to final execution.
So let’s set all the variables that we will get and use in this section from properties applied by the user in his document.

 (function ($  ) {     $  .fn.characterCounter = function (options) {  //variable declaration         var maxLen = options.maxLen;         var warningLen = options.warningLen;         var showMsg = options.showMsg;         var customMsg = options.customMsg;         var separator= options.separator;         var warningColor = options.warningColor; 

We have used the same variable name as the property name to avoid confusion. So, now we have captured all the values into their relevant variables.

Allow users to enter only characters specified in the maxLen.

 //set max Length to input box         $  (this).attr('maxlength', maxLen); 

Check if the separator is not defined in the options, if not then use the default one.

      //if separator is not defined then use below one                      if(!separator)                  {                     separator = "|";                 } 

Now, we will check the property for any errors and as a good developer, will give them errors on the console and on the document too where the counter will appear. Word of caution: All the errors are written in the fancy language, so better you avoid them by error-free integration.

 //checking properties of object         if (!options.hasOwnProperty('maxLen')) {             console.error("Defining maxLen is mandatory. Example: maxLen: 320");             $  ('#counter').text("Oops, Something is missing. Get hint from console!");         } else {             $  ('#counter').html(maxLen + separator + maxLen);         }          if (!options.hasOwnProperty('warningLen')) {             console.error("Defining warningLen is mandatory.This will give color coded hint to your user. Example: minLen: 60");             $  ('#counter').text("Err! Something gone wrong. Please check your console.");         }          if (!options.hasOwnProperty('warningColor')) {             console.error("Boy, Color is missing! Example: hexcode/rgba/name anything, you just name it!");             $  ('#counter').text("Color is missing. See console for details.");         }                  if (!options.hasOwnProperty('showMsg')) {             console.error("It's very simple, just set showMsg property TRUE or FALSE. Example: False");             $  ('#counter').text("Showing alert can be good idea to give extra information to user. See console brah!"); 

We have used hasOwnProperty to check whether the user has passed the mandatory property or not. According to MDN,

“The hasOwnProperty() method returns a boolean indicating whether the object has the specified property”

Now, we will put all our mandatory properties in an array and iterate it to check if they are present in our object options or not and if all are present then we will call keyup and update message length on every key up and calculate remaining characters by subtracting it from the max length.

Here I have used two IDs, #counter and #ccInvalid, So, you need to create one DIV with ID #counter. This DIV will show the character counter (only if you are lucky enough, otherwise you will get errors and instructions on the DIV).

      //procceed only if object has all properties          var propertyArray = ["maxLen", "warningLen", "showMsg", "warningColor"];         if (propertyArray.every(function (x) {                 return x in options;             })) {             $  (this).keyup(function () {                 var text_length = $  (this).val().length;                 var text_remaining = maxLen - text_length;    $  ('#counter').html("<span id='ccInvalid'>" + text_remaining + "</span>" + separator + maxLen);        var msg = "Oops, you are not allowed to enter more...";                 if (text_remaining <= warningLen) {                     $  ("#ccInvalid").css('color', warningColor);                 }                 if ((showMsg) && (text_remaining < 1)) {                     if (options.hasOwnProperty('customMsg')) {                         alert(customMsg);                     } else {                         alert(msg);                     }                 }              });         }       

Visual Feedback

We have used three types of visual feedback and one from which one is for developers to see errors if they integrate the plugin in an ill manner and the other two (color coded hint and alert) for the user who visits your website and fills in the contact form.

Full Code

Plugin (Example – characterCounter.js)

 (function ($  ) {     $  .fn.characterCounter = function (options) {         //variable declarion         var maxLen = options.maxLen;         var warningLen = options.warningLen;         var showMsg = options.showMsg;         var customMsg = options.customMsg;         var separator = options.separator;         var warningColor = options.warningColor; //set max Length to input box         $  (this).attr('maxlength', maxLen);         //if separator is not defined then use below one                      if(!separator)                  {                     separator = "|";                 }         //checking properties of object         if (!options.hasOwnProperty('maxLen')) {             console.error("Defining maxLen is mandatory. Example: maxLen: 320");             $  ('#counter').text("Oops, Something is missing. Get hint from console!");         } else {             $  ('#counter').html(maxLen + separator + maxLen);         }          if (!options.hasOwnProperty('warningLen')) {             console.error("Defining warningLen is mandatory.This will give color coded hint to your user. Example: minLen: 60");             $  ('#counter').text("Err! Something gone wrong. Please check your console.");         }          if (!options.hasOwnProperty('warningColor')) {             console.error("Boy, Color is missing! Example: hexcode/rgba/name anything, you just name it!");             $  ('#counter').text("Color is missing. See console for details.");         }         if (!options.hasOwnProperty('showMsg')) {             console.error("It's very simple, just set showMsg property TRUE or FALSE. Example: False");             $  ('#counter').text("Showing alert can be good idea to give extra information to user. See console brah!");         }          //procceed only if object has all properties          var propertyArray = ["maxLen", "warningLen", "showMsg", "warningColor"];         if (propertyArray.every(function (x) {                 return x in options;             })) {             $  (this).keyup(function () {                 var text_length = $  (this).val().length;                 var text_remaining = maxLen - text_length;     $  ('#counter').html("<span id='ccInvalid'>" + text_remaining + "</span>" + separator + maxLen);                 var msg = "Oops, you are not allowed to enter more...";                 if (text_remaining <= warningLen) {                     $  ("#ccInvalid").css('color', warningColor);                 }                 if ((showMsg) && (text_remaining < 1)) {                     if (options.hasOwnProperty('customMsg')) {                         alert(customMsg);                     } else {                         alert(msg);                     }                 }              });         }      } })(jQuery); 

JS (Example – script.js)

 $  ('#emailContents').characterCounter({                         maxLen: 15,                         warningLen: 5,                         showMsg: true,                         customMsg: "You have exceeded the permissible limit of characters..",                         separator: "/",                         warningColor: "#d50000",                                         }); 

HTML (Example-index.html)

 <textarea id="emailContents"></textarea> <p id="counter">15/15</p>  <!-- Javascripts --> <script type="text/javascript" src="jquery-1.11.2.min.js"></script> <script type="application/javascript" src="characterCounter.js"></script> <script type="application/javascript" src="script.js"></script> 

Conclusion

So the character counter can be very useful in many ways, a few of which we discussed in this tutorial. It can act as a first line of defense against spamming. Though, it is not foolproof to stop spamming, but it is definitely a good thing to integrate.

Did I mention that it is under the MIT license? So you can enjoy extending its functionality. I have tested it on Chrome and Firefox for both mobile and desktop.

You can download from here or check out the live demo.

I’m excited to hear your feedback on improving this plugin, or share the link to your contact page in the comments if you use it.


Onextrapixel – Web Design and Development Online Magazine

Write SVG: a PostCSS plugin

Here’s a cool PostCSS plugin that lets us write SVG directly in CSS with the rest of our styles:

.arrow {     @svg {         polygon {             fill: green;             points: 50,100 0,0 0,100;         }     } }

These values will then be converted into a data URI, like so:

.arrow {     background-image: url(data:image/svg+xml;utf8,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%3E%3Cpolygon%20fill%3D%22green%22%20points%3D%2250%2C100%200%2C0%200%2C100%22%2F%3E%3C%2Fsvg%3E) }

Like Sara Soueidan mentions, I’d love to see this in Sass.

Update: David Khourshid has just made sass-svg which lets you write SVG inside a mixin.

Direct Link to ArticlePermalink


Write SVG: a PostCSS plugin is a post from CSS-Tricks

CSS-Tricks

Bloom From Elegant Themes – The Opt-in Plugin to Grow Your Email List

Everyone wants more names on their newsletter or email list, but also, we want to know that we are sending the information out to people who really want it and are more likely to act upon it. That is one of the areas that the team at Elegant Themes have concentrated on during the development of their brand new opt-in plugin, Bloom. Including a host of features so that you can customize your pop-up or fly-in to your own requirements.

More About Bloom

Did you know that an email subscriber is 10 to 20 times more valuable than a Facebook fan or Twitter follower? I guess it is logical – your email will not be lost in competing posts on your followers’ timelines, at worst, it could be sitting in the middle of a bunch of junk or spam mail, but it is still easy to spot in an email inbox and is a direct line to your visitors, where you know they can read it at their leisure. So getting your campaign to increase your subscribers right is so very important, and this is where Bloom can help you out.

Email Software Integrations

The team have tried not to leave anyone unable to use this plugin, and have made it compatible with a huge list of Email Software providers such as:

  • MailChimp
  • GetResponse
  • Constant Contact
  • MadMimi
  • FeedBlitz
  • Campaign Monitor
  • MailPoet
  • iContact
  • AWeber

And you can expect there will be more, this list is just an example of the software Bloom will be compatible with. You can also create custom HTML forms.

Where and When Your Opt-In Form Appears

Here is another area of concern that has been addressed with this plugin. Many plugins offer the opportunity for the form to pop-up at a specified time after the page has loaded, but Bloom will give you complete control over where each of your opt-in forms appear. You can have as many or as few forms as you want, and you can target each of them to different posts, pages, categories or post types, and there are 6 types of forms to choose from.

FormTypes

Form Design

If you know Elegant Themes, you know that design is one of their top priorities, and that is not changing with the development of Bloom. Rather than static templates, you will be given design options so you can customize each form to your own requirements in an almost limitless manner.

Forms

Behind the Scenes

Once you have your forms in place, you will want to know how they are performing for you. The Admin section of this plugin will give you all that information, with stats and methods for testing and optimizing your campaign performance.

Dashboard

Find Out More

You can find out more details about the Bloom plugin on the Elegant Themes Blog Post on the subject.

How Can You Get This Plugin?

Getting hold of this plugin is easy – it is not free per se, but is included in both the Developer and Lifetime Access plans available from Elegant Themes.

With these plans you get access to all of the themes available on the site, and all of the plugins also. The themes are beautifully designed and the plugins are highly useful, so the whole package is well worth the relatively small outlay. The annual cost of the Developer plan is $ 89, and the one-time cost of the Lifetime Access plan is $ 249.

Here’s a video to explain further:

Conclusion

Elegant Themes has been around for many years, and I am guessing that over 260,000 members can’t all be wrong!

If you are not yet a member of Elegant Themes, and you struggle with meeting deadlines at any point throughout the year, it is well worth popping over there to take a look at what they offer. If you are a member, please share with us your experience with using their products in the comments section below.


Onextrapixel – Web Design and Development Online Magazine