11 Features of World Class WordPress Backup Plugin

Search better

Hello World!
We just wanted to let you know that we have some interesting updates lined up for you.After three months of hard work, your favourite WordPress backup plugin has incorporated the Advanced Search feature!

Still, haven’t found what you’re looking for?

The Advanced Search option allows you to enter more specific search criteria about the websites you are trying to find in order to refine your results. Depending on the system's configuration, you may not need to enter minimum search criteria but if you do enter criteria, you will receive better results.

Organise your websites, the smart way.

You can use words or symbols called search operators to filter your BlogVault advanced search results. You can also combine operators to filter your results even more.You can now organise your websites present within BlogVault. This categorisation can be done according to your selection of WordPress core versions, plugins, themes, their versions, users or even tags. You can then make changes to the selected websites accordingly.

Helps narrow user searches

Do you have fifty or so websites using BlogVault for backup and other related services? How are you going to update a plugin installed on a few websites only? Maybe you want to check out websites with a particular tag name. 

Streamline bulk actions for web sites

Ever wanted to perform a single action like updating existing plugin on many websites at once? Now you can!

Next Steps >>

Check out how to use Advanced Search from here
Try Advanced Search from the Dashboard Now.
You can always get in touch with us from here or also email us at support@blogvault.net


The web hosting industry is incredibly competitive, so many hosting providers offer value-added services such as free backups to their customers free of cost as a means to differentiate themselves. And while some sort of a backup is better than no backup at all, it certainly doesn’t check all the boxes when it comes down to taking a complete, reliable backup of your WordPress website. So, do you really need to sign up for a premium backup solution if your hosting company already does regular backups? The short answer is: yes. And in this post, we’ll take a look at why you need a premium backup service for your site and what features it brings to the table. But before we begin, let’s take a look at the issues you can potentially run into if you go with web hosting backups.

The Problem With Web Hosting Backups

There are a number of different scenarios where you might find yourself needing a backup of your WordPress website. It may be because of a software-related issue during upgrades, host failures, or a simple case of human error. Whatever the case may be, when your site crashes, you need to restore a backed up version of it pronto. For this reason, it’s important that the backup solution provider you rely on is reputable, fast, and helps you restore your site from a backup. This, however, is not the case with the backup feature offered by web hosts. Here are some of the most common problems with web hosting backups:

  • Availability. Most web hosting companies offer free, automatic backups with their advanced hosting plans and charge a little extra for users on their basic plans. In addition to this, some of them will only backup your site automatically if it’s within their website size limit.
  • Coverage. WordPress websites consist of databases and files. It’s important to know exactly what your web hosting provider is backing up and whether or not you have access to it. This way, you’ll be prepared for when your site goes down.
  • Frequency. How often your site needs to be backed up varies from website to website. If your hosting provider takes a backup once every week then you could lose important data if your site crashes.
  • Storage. While web hosts claim to take regular backups of your site, not all of them store multiple versions of it. What’s more is that the backups they do store aren’t encrypted. This means that it’s entirely possible for your site’s backup to be tampered with in case of a security breach on your web host’s end.

With that out of the way, let’s take a look at why you might be better off with a high-end backup service for your WordPress website and what features you can expect to get from it.

BlogVault Backups vs. Hosting Company Backups

Even if your WordPress web hosting provider offers free, regular backups, you might find that it isn’t enough when your website actually gets hacked or crashes. For starters, web hosts don’t offer auto restore functionality. What this means is that if (or should I say, when) your site crashes, you’re left on your own to restore it. For those of you who aren’t particularly technically inclined or simply don’t want to have to figure it out on the spot, you’re better off with a complete WordPress backup service – like BlogVault. Here’s why:

BlogVault Is Optimised for WordPress

Many web hosts that offer free backups will create a backup for you without taking its structure into consideration. As you probably already know, WordPress sites are very organized on the backend and consist of two parts: database and files. And because of this, a WordPress site isn’t like any other site even if your web hosting provider thinks so.
BlogVault is designed to create complete backups of WordPress websites specifically. What you get are optimised backups that have everything you need and nothing extra. This is made possible because of BlogVault’s incremental approach to taking backups. Behind the scenes, the backup service identifies any changes that have been made to your site since the last sync and only stores those. The great thing about BlogVault backups is that they’re smaller in size and much faster to restore than those taken by your web host.

BlogVault Lets You Auto Restore and Test Restore Your Site

If your WordPress website ever crashes or is deleted by hackers then BlogVault’s auto restore functionality can help you get it back up in no time. What it does is it basically restores your site’s most recent backup to its hosting server without any manual intervention from you, the website’s owner.
In addition to this, BlogVault also offers a test restore feature that enables users to pick out a backup of their site and load it onto BlogVault’s test server to make sure it’s working properly. This way, if you accidentally crash your site during development then you can revert back to a fully functional version of it without any hassle.

BlogVault Offers Multiple, Encrypted Backups Stored on Different Servers

A major problem with having your web hosting provider store your site’s backup is that you’re left with little to no options if your server crashes. This is especially true for websites that are hosted on shared hosting plans.With BlogVault, however, you can rest assured that your WordPress site’s backups are secure since multiple copies of a single backup are stored in different locations – independent of your site or the server it’s hosted on. BlogVault stores encrypted copies of your site’s backups on their own servers and on Amazon S3 servers.


Having a high-end backup solution in place for your WordPress website is fundamental. All you have to do is set it up and then you can stop worrying about losing your site’s data once and for all.

Let’s quickly recap why you should go with a premium backup solution as opposed to your web host’s backups:

  1. It is optimised for WordPress and keeps your backup files manageable.
  2. You’ll have the option to auto restore and test restore your site.
  3. You can rest assured that multiple, encrypted backups of your site are stored on different servers.

Are you ready to make the switch from hosting provider backups to all-inclusive BlogVault backups? We’d love to hear from you so let us know by commenting below!

XML-RPC is a WordPress API that allows WordPress site-owners functionality, while on-the-go. But how does it affect WordPress sites’ security?

XML-RPC attack_WordPress mobile

What is XML-RPC, and why is it such a big deal?

The ‘XML-RPC’ is an API that enables developers create WordPress ‘apps’ (like clients, plugins and themes), that allow you to make remote HTTP requests to your WordPress site.

This means, as a WordPress site owner, if you used a plugin or client that had WordPress XML-RPC support, you would be able to perform a number of functions without actually logging in to your WordPress site.

Some of the functions you would be able to perform on your site with these plugins or clients would include:

  1. Post-related functions like creation, publication, edition and deletion
  2. Media-related functions that include uploading files, and viewing the media library
  3. User-related functions, such as editing your profile, getting a list of authors for a post, etc.
  4. Comment-related functions such as listing comments, and editing them

There are a number of Weblog Clients and WordPress plugins that allow you to do this. Some of the popular ones include the Jetpack plugin for WordPress.org, clients like rubypress, and WordPress Sharp; and even WordPress’ own app for both Android and iOS. Since all of these functionalities make life easier, WordPress has had XML-RPC enabled by default, since WordPress 3.5. (WordPress’ latest update was WordPress 4.6, so it’s been a while). Obviously these tools would still need you to input your WordPress admin username and password for them to work, so they seem safe.

How does it pose a security risk?

However,  anyone can use the XML-RPC API to make these requests. Using the API, a script can make multiple requests simultaneously to your site. This makes it a convenient choice for attackers who would want to launch a attacks against your site.

One application for this functionality, would be to try with different combinations of usernames and passwords while having substantially lower chances of getting detected. This makes XML-RPC  an ideal approach for Brute Force attacks.

Unlike hacks that focus on vulnerabilities in software, a Brute Force Attack aims at being the simplest kind of method to gain access to a site: it tries usernames and passwords, over and over again, until it gets in. Often deemed ‘inelegant’, they can be very successful when people use passwords like ‘123456’ and usernames like ‘admin.’

Even if you have passwords consisting of a minimum of 10-15 alphanumeric characters and special characters, there is one more threat – DDoS.

DDoS is a type of Denial Of Service (DOS) attack where many infected websites or systems are used to attack a single website and bring it down, by overwhelming the target website with requests. This results in the website’s server denying service, as a result of shutting down (… hence the term).

Actually, in March 2014, a number of WordPress sites experienced an attack involving ‘pingback’. Pingback, is an XML-RPC functionality (especially on WordPress), that allows you to see where links to your WordPress posts are used. This is done by the sites with shared links pinging the source of the link. The source site then replies (or pings them back) with the live link (so that if the post is taken down, it would show you a ‘404 error’, or if it’s been updated, the newer version of the post would be displayed). So when attackers used XML-RPC requests to perform the DDoS attack in 2014, they exploited the pingback functionality, and used thousands of other sites to ping victim sites. Once all the thousand sites starts pinging the victim site simultaneously, the server ran out of resources and the site went down.

Do you have to disable XML-RPC?

Well, it depends. WordPress identified the XML-RPC API abuse, and has made its laws stricter. Plugins like Akismet that help detect spam, have also gotten better at detecting attacks like the one involving pingback. But the bottom line is that there is no way to make your WordPress site 100% attack-proof.

So yes, an easy way to make your site safer, would be to disable the XML-RPC API. For this, one can use  security plugins, such as iThemes Security (formerly Better WP Security), or NinjaFirewall.

However, before making this choice,it is very important to understand that turning this API off can affect the functionality of some plugins and apps that you might be using in conjunction with WordPress. This will disable the WordPress mobile app and severely affect the functionality of plugins like Jetpack, from accessing your site.

This is why it’s always important to have several backups of your WordPress site before you test the change to see if you’re okay with it. If you’d rather keep the functionality on, you can choose from a previous version of your site, and roll back changes to a fully-functional version of your site.

Making an integral change to your site is never easy, but it’s always better when you have all the facts. Which choice have you gone with, on your WordPress site? Let us know in the comments!

At BlogVault, we recently spoke to Rahul Bansal, founder of rtCamp; Asia’s first WordPress.com VIP partner agency. He shares his convictions, struggles, the formation of rtCamp, the growth story that eventually led to this watershed achievement, and his thoughts on ethics & business practices.

India is waking up to the presence of WordPress in the digital landscape now. On the cusp of this realization, rtCamp has emerged to become the very first WordPress.com VIP Partner in Asia. It is a prestigious featured partner program that has till now picked only 12 agencies; including rtCamp, as partners worldwide.

To those in the Indian WordPress community this achievement is definitely a breath of fresh air, considering the unwanted reputation agencies from South Asia carry in global WordPress(WP) market.

As part of the same WP community, and as global leaders in backups & security, we at BlogVault wanted to record this achievement. The premier WordPress agency on the continent has definitely crossed a threshold and its founder joined us recently to trace his journey.

Rahul Bansal answers questions on his convictions, struggles, the formation of rtCamp, and the growth story that eventually led to this watershed achievement.

A Decade Ago: Building up Skills

Rahul’s journey started almost accidentally as he took up blogging during his engineering days, purely to follow a friend he looked up to. The rampant focus on remuneration packages instead of work profiles pushed him away from conventional job interviews during campus placement.

“I didn’t want to join any company; hence I took up M. Tech. It was essentially an escape”, says Bansal. Rahul says that he got more free time during his M. Tech.  He began to enjoy blogging; and the journey took an interesting turn as he discovered Google AdSense.

The revenues from AdSense were sufficient to convince Rahul that he could take up blogging professionally. It was this decision that would eventually take him away from blogging and towards developing on WordPress. But, more on that in a bit.


The Family Front: A Quintessentially Indian Story

Rahul was thinking of becoming a professional blogger in the India of 2006. That too, after his engineering. It is not an easy switch to sell to our parents even now, so it could not have been easy then!

Rahul admits this to be a tough period in his life. However, he found an interesting analogy to help him. “…I used to explain my profession to my folks, especially the older ones, with the analogy of a news agency. [the conversation would go something like this]”

“Do you read a newspaper?”


“How much does a newspaper cost?”

“1 or 2 rupees!”

“Is that enough to run a news agency?”

No! They make money from ads”

“I do the same thing. I run a newspaper online and make my money from ads.”

For the most part, that was that, and Rahul was a professional blogger. He suspects that the point that eventually convinced his parents was that he was no longer taking money from them.

The decision to turn a professional blogger also meant that he had to prepare to do the job well. As part of this project, blogger Rahul turned to WordPress to customize his site  and gain more control over his content and its presentation. This turn, which came out of a necessity, would lead him to be fascinated with WordPress, the CMS’ ease of use, and the many possibilities the platform presented. All of these factors planted the seed of freelancing as a WordPress web developer in his mind; although he wouldn’t give up blogging straight away (after all it was a steady source of income and his blog was growing in popularity).


The Freelance Route to the rtCamp Journey

Perhaps one could read into Rahul’s approach to freelancing, and see the success to come. He says, “I was already making money from the blog. It was because I wanted learn many things on WordPress that I began freelancing.” So, he says that he made a list of things he wanted to learn in WP and went after projects with “realistic challenges”, “realistic deadlines”, and “realistic value” that would help him learn those skills.

The blogging trails paid rich dividends during his freelancing days too. There cannot be a better example for how popular his blog- Devil’s Workshop, was at the time, and for how having rich content can help any business more than the following story. Rahul recollects that he was once awarded a project before the details were finalized. He was surprised and inquired the client. He says, “The client only said that You are running such a successful blog, you must be doing something right!” Rahul says, “On the internet, it is your skills, not your academics that speak for you. That is how the internet works.”

The blogging trail combined with his desire to learn and grow continuously meant that Rahul built a successful client base as a freelancer. His list included clients from around the world. Although, he is quick to point out that this diverse client base wasn’t planned; instead he says “I just went after projects and opportunities [which interested me].”

This approach proved to be financially successful as well. Rahul remembers how almost all of his clients wanted to work with him again after the first projects were completed. This ensured that the workload burgeoned to the point that he couldn’t handle it alone.

Rahul’s growth in his individual professional life coincided with the 2008 global recession. During this period many of his friends could no longer depend on the giants of the IT industry to guarantee them a job. He pitched the work he was doing to them and when some of them showed interest, he trained them. The burden of his workload decreased and the business expanded. This expansion would eventually be titled rtCamp but that was still a few months away.

So far Rahul’s decisions don’t seem obvious to anyone. Turning away from a career after engineering. Convincing his parents about becoming a professional blogger; and taking up freelancing projects as a web developer to learn a CMS that; in 2006-2008 India, was not nearly as popular as it is now.

Another one of such decisions was that, very early on, he decided that he would work solely on WP. This decision too was born out of his conviction, “I believe we should only develop on software we use.” “To date, even out of curiosity, I haven’t installed Joomla or Drupal” explains Rahul. Hence he was a WordPress freelancer much before the marketplace emerged for the title in the country. Following his convictions, as Rahul himself states was a “good decision [looking back].”


rtCamp: The Core Values

The more we spoke the more we realised that Rahul’s freelancing days would come to shape his own values and lay the groundwork for the path rtCamp would take. During his period as a freelancer, Rahul was not only fascinated with acquiring skills but was interested by the open-source platform; and the community that came with it.

In that period he participated in many meetups. The “un-conference” culture of the WordPress community and the open-source movement charmed him. Going along with this, he wanted a work environment where “everyone respects everyone”. The value he derived from camps, and his “hunger for equality”; as Rahul puts it, eventually led to ‘rtCamp’.

rt stands for roundtable, a reference to the famous roundtable of the noble knights in the Arthurian legend. The ‘Camp’ part comes from the desire to replicate the community driven culture around Bar/Word/php camps which Rahul used to attend- an environment where everyone participates, speaks up and takes ownership.  It was an idea he had come to cherish. “I liked the unconference culture and wanted the same in my organization. I believe everybody must speak and express themselves rather than simply taking orders.” says Rahul.

So it is not a hyperbole or an act of taking credit in hindsight when he says, “Looking back you can always connect dots. Our core values have made us the kind of company we are today. One who loves WordPress, open-source, and contributes to the community”

He says we always encourage all ‘rtCampers’ (as the people who work at the agency are called), to participate in the community, whether it is by attending WP meetups, WordCamps or by other means.

On Landing Big Clients:  The Case of Geometric

The points about the “un-conference” culture, and the encouragement for people to take ownership, shine through when you ask Rahul about how rtCamp landed its first big client- Geometric Global.

He began his response to us by crediting rtCamp’s then Head of Marketing, Gajanan Sapate.

Sapate suggested building rtCamp’s presence on LinkedIn as a WordPress Agency. Although Rahul wasn’t keen on the idea Sapate went ahead without his approval, Rahul recollects. “That is what the round table culture is all about,” he says proudly.

Around the time, Geometric Global were on the lookout for a WP agency. They are an MNC and as Rahul pointed out they have offices around the world. The website part of the business however was managed out of Hinjewadi near Pune. They wanted a local vendor to build their site on WP. Decisive on these two points- location of the vendor & the CMS, they went looking for a WP agency on LinkedIn.

This was around 2011-12 and Rahul suspects that Geometric Global’s search for a WP agency on LinkedIn resulted in only rtCamp’s name popping up as there were no other WP agencies at the time. Sapate’s initiative had paid off and only time would reveal how handsomely it had paid off.

For what seemed like a pleasantly fated start, the relationship between Geometric Global and rtCamp was anything but that. rtCamp at the time was a small agency. Despite its size, some members of Geometric Global were keen on working with them. The reason for this was once again; among other points, the Blog- Devil’s Workshop. Rahul remembers that some members of Geometric Global were already familiar with his blog when they approached rtCamp. Apart from this, rtCamp’s plugins on WordPress.org, open-source projects, and participation in and contribution to the WP community were all reasons in their favour.

Even today, Rahul suggests that younger agencies looking to build a reputation with WP must show their love for the CMS by making contributions to the community. This is not simply a pedantic statement. In fact, WordPress.com announced rtCamp as a VIP partner with an article, where rtCamp’s “record of community engagement” was specially mentioned as the reason for extending them VIP partnership.

While the above points were in favour of rtCamp, some other points were not. For starters they were not used to a seemingly long sales cycle of around 6 months. During that phase, Rahul recalls that most, if not all of rtCamps’ sales cycle lasted a maximum period of 2 weeks. This shift proved to be quite frustrating as Rahul mentions. Along with this, rtCamp was also not familiar with many processes that were required by enterprise level clients. They failed many checks like access control (magnetic strip cards) among others.



This meant that, while rtCamp was optimally placed to deliver a project which was based on WordPress for Geometric Global, they were not aware of many requirements and practices of enterprise clients. Both parties, Rahul admits, acknowledged these points. Rahul remembers being upfront in his approach when it came to selling to his first big client, and they eventually landed the project.



Even after this however, the demands of servicing an enterprise client was taking its toll on a small but growing agency. One of the reasons for this was that rtCamp billed Geometric Global like all other of their other clients. This was unsustainable as Rahul himself admits. Geometric Global’s value at the time was greater than the combined value of all their other clients. The demands were also greater to go along with this.

All these struggles meant that Rahul was unconvinced with the idea of taking on enterprise clients. He says that for about two years after signing Geometric Global he did not try to sign any other enterprise clients. During this 2 year period however, their relationship with Geometric Global evolved and stabilized. It wasn’t easy as Rahul recollects, “Even after [we signed them] there was steep learning curve.” Geometric Global’s willingness to work with rtCamp and train them on certain issues sustained the work Rahul recollects. In fact, the suggestion to increase the price too came from Geometric Global Rahul mentions. This maturing relationship eventually convinced Rahul that enterprise level clients were the way forward for rtCamp. It seems that rtCamp hasn’t looked back since.

Mission “WordPress.com VIP Partner”: A New Year’s Resolution

There is a diffident smile on Rahul’s face when he mentions that at an rtCamp New Year’s party he announced that the agency would become a WordPress.com VIP Partner. While he admits that he didn’t have very specific roadmap in mind then, he planned for it every day for the last 18 months.



Part of the plan was to deliver VIP grade code to their clients before they had contact with WordPress.com. Rahul surmises, “Most people change when there is a need to [do so]. We started coding at VIP standards when our clients were not asking for it.”

Such preparation has paid off very well. Rahul says that when they got their first VIP project from WordPress.com, “The code was approved in the very first round!”

However, if you ask Rahul why he aimed to become a VIP partner, then the story takes a more poignant turn. He had noticed how clients abroad would switch off when they knew an agency was from South Asia. Rahul recognised that it would be hard for everyone to go through rtCamp’s work. Having a symbol of quality would bypass some of these issues he though, and becoming the first VIP partner in Asia seemed like the solution.

Unique Growth Story of an Indian Agency: Way forward for Indian WP communities

The challenges were many and in that context the growth of rtCamp is surely a unique story. This is so, not just because of it has done but also because of how the agency has done it. It is one thing to come up with a name or a set of values, and another to thing to stand by and act according those convictions when you know they aren’t going to work in your favor. This is what Rahul has done.

He recollects a time when a Project Manager at rtCamp made an error in scoping the document. This led to a verbal commitment to deliver the project on a deadline. When the D-day neared, the error surfaced. Rahul recollects how he not only admitted the error straightaway to the client but resolved to work for the remaining duration of the project for free. “If we made a mistake, then we should pay for it. Why should the client suffer?”, Rahul asserts.


Although the client was very pleased with the results when the project was eventually completed and offered to compensate rtCamp, Rahul says that he refused. He reasoned that they might forget the lessons they learned if they accepted payment.

These actions though exemplary, almost drove Rahul to bankruptcy. The client was one of their biggest at the time and working for them at no cost meant Rahul had to pay a heavy price. If not for a friend who loaned him some money, Rahul would not have been able to even pay the salaries. These decisions are only more admirable because of the accompanying circumstances. Just before the incident came to light Rahul had got married. A new phase of his personal life began with a crisis in his professional one. Although it looks like he took a big gamble; and he did, Rahul simply says, “It was about doing the right thing.”

It is this combination of technical expertise, professionalism and a high level of adherence to their core values and ethical business practices that sets the foundation of rtCamp’s success. It is also a good sign-post for younger WP agencies to begin charting their paths.

The Future

“Becoming a WordPress.com VIP partner is the start of something,” Rahul says. He is not about to rest on his laurels but, “… everything we do must be better now … and we’re working harder to get everything right.” Rahul says he feels more responsible now as there is a sense of representing the Indian WordPress community.

At BlogVault, we wish Rahul and rtCamp all the very best and we look forward to seeing the next big thing from them.



Themeco Hosting users can now enjoy the premium WordPress backup service from BlogVault. This partnership allows all users of Themeco Hosting to utilize BlogVault’s expertise, at no extra charge.

As advocates for best practices in WordPress backups and security, we are certainly proud of this partnership with Themeco Hosting which makes professional backups a part of the hosting service.

BlogVault WordPress backup at no extra cost for Themeco Hosting users
Themeco Hosting users can now get WordPress backup by BlogVault at no extra cost


A Quick Intro to BlogVault

To all the new users, welcome!

Our service, stores up to 30 days of backups guaranteed. You can find all the versions listed in order with date, time and changes. So, when the time comes to restore or migrate your site, you can choose the desired version with ease.

Users will be happy to know that apart from backups following WordPress best practices, BlogVault’s service comprises one-click restores and one-click migrations along with a host of other comprehensive features that are intuitive to use.


A Comprehensive Dashboard

The dashboard is designed to be pain-free and is a single-point access to all options related to backups, restores, and security settings; so that you can focus on creating and managing content in a dynamic & creative environment.

You can login to your BlogVault dashboard anytime to find all your files and tables, & find out which ones are excluded from backups. In the same list, you can also add any excluded site to backups or download any on or all of the files/tables.

To do this simply click on the files/tables and at the end of the list click ‘Add to backup’. On the other hand you can select the files/tables with same method and at the end of the list click on ‘Download’. You have complete access to and control over all your files and tables.

With that we welcome Themeco Hosting users to BlogVault and look forward to a fruitful partnership.


About BlogVault, & Themeco

BlogVault is a Bengaluru based, five-year old tech company developing premium backup & security solutions.

Themeco Hosting is brought to you by the same people behind the creative WordPress theme- X, and the versatile page builder Cornerstone.

“Why do hackers hack websites?”, is one of the more philosophical questions of anyone with a website. Whatever the size of your WordPress site, protecting it from the common attacks against websites is definitely a concern.

Figuring out the best security option, (especially making the decision between a WordPress firewall and an antivirus) for your website requires a lot of research and technical know-how. But if you’ve decided on getting a WordPress firewall, NinjaFirewall is one of the options that you will have to consider.

This is why decided to test NinjaFirewall (v 3.2.4) for you, and to do it from a WordPress newbie’s point of view. We’ve pitted it against against the common exploits on WordPress sites to see if it stands our tests of fire.
A Web Application Firewall (or a WAF) provides customizable inspection and runs as an appliance, plugin, or a cloud-based service.


NinjaFirewall's logo
NinjaFirewall is a host-based WAF, that runs for WordPress.


Host-based firewalls on WordPress help protect against threats originating within the host (which, in this case, is your website). This means that they help reduce the risks of vulnerabilities in your website being exploited.


About NinjaFirewall

NinjaFirewall allows you to install and configure it just like a WordPress plugin, but it’s a ‘stand-alone’ plugin that intercepts all requests made to WordPress. The fact that it’s ‘stand-alone’ means it has its own settings, options, policies and rules that you can configure. If you’ve googled NinjaFirewall, you’d have seen phrases saying that the firewall ‘sits in front of WordPress’. This simply means that NinjaFirewall intercepts requests with the aim of alerting you of, and stopping any suspicious activity/requests before they affect your site.

There are also a few hiccups that you might face during installation, that the NinjaFirewall team has documentation for, which is great, if you aren’t a beginner with WordPress, and know the basics enough to understand code.


What NinjaFirewall Claims to Do for You

NinjaFirewall claims to intercept and determine which traffic to allow to your site. Upon installation, the firewall backs up your php.ini and .htaccess files and then modifies them to intercept every request made to your site. It then filters requests and traffic using extensive rules (and a whitelist), to separate good requests from malicious ones. The bad requests are dropped while normal requests are forwarded to your WordPress site. Its aim as a firewall, is to prevent your site from getting hacked, by avoiding bad requests from the get-go.

NinjaFirewall has a lot of features, that help towards this end, and many varied security functionalities to your site.



NinjaFirewall has a lot of features, that help towards this end, and many varied security functionalities to your site.  Each feature of NinjaFirewall has different options and settings, and we hope to explain the most important ones below:


NinjaFirewall has a great-looking set of features
NinjaFirewall has a great-looking set of features


        1. Firewall Options

          This is where you enable or disable NinjaFirewall. You can also customize the error messages to be displayed on your site when the firewall detects a bad request.


          Firewall Options

          If you’ve got NinjaFirewall installed on another site and have configured it according to your needs, you can import it to a fresh installation in the Firewall Options section. The only requirement is that both sites should have the same versions of NinjaFirewall.
          Importing another configuration of NinjaFirewall will override any firewall-related rule, option or configuration that exists on the site you’re importing to.

        2. Firewall Policies
          Most of the options that control how NinjaFirewall works, are in the “Firewall Policies” section.
          None of these options are customizable though: the majority of them are Yes/No options, or have check-boxes. The first few options let you decide whether you only want traffic with an SSL certificate or you’re okay with traffic that comes from other sources. Since a lot of hacks originate from file uploads, the firewall also allows you to choose whether you want to allow them or not. These first few options are easy enough to configure:Firewall Policies for traffic and uploadsBut as you scroll down the list, they get more and more complex. Some options even caution the user to not click on them if the user doesn’t understand what they entail. NinjaFirewall has documentation to explain all of these options, but some of them might still need some technical knowledge. This is why we’re going to try and break it all down for you.The HTTP variable is what requests information from a web page.
          Scanning it for dangerous values is a great move, especially since hacks depend on GET, POST and REQUEST variables.
          Sanitizing these variables makes sure that the website interprets strings as such, and not as commands.Scanning and sanitizing the HTTP variables can keep you from a number of attacks
          These options keep out suspicious bots from crawling your site:


          NinjaFirewall tries its best to keep suspicious bots from your site.
          The HTTP response headers help in protecting your site from other hacks that originate from the browser’s end.

          These settings help NinjaFirewall help protect you from attacks that originate from your browser.

          There are also a few options that are unique to WordPress:


          These options help protect against SQL dumping, and a number of shell scripts.

          These help protect your site from SQL dumping ( i.e. creating a snapshot of and storing all of your website’s database files); as well as a number of shell scripts.When a hacker tries to attack your site, they make a number of attempts, and depend on error messages to determine whether their attack worked or not. NinjaFirewall has the following options to not let your site display revealing error messages:


          These options prevent hackers from using PHP wrappers to pass GET and POST requests. They also hide error messages.

          And then there are other ‘various’ options that you can enable:


          And then there are other 'various' options

          NinjaFirewall also has options that control the requests made to and the access to WordPress core files and directories:


          Options that control how the WordPress directories are handled

          This section is also where you can modify the firewall’s white-list:


          There are also options to control your WordPress site's whitelist



          1. File Check
            This feature helps create a ‘snapshot’ of files changed by comparing original files (or existing ones) against modifications. Once you create a snapshot (that you can later download or delete), it allows you to scan your site for file changes. You can not activate this scan before you create a snapshot.The File Check feature


          1. Anti-Malware
            The NinjaFirewall also has an Anti-Malware feature, that allows you to scan for hacks. According to NinjaFirewall’s documentation, this feature doesn’t alert you of spammy links, (like those that might redirect your visitors to porn sites). However, it does alert you based on signatures of malware, that could damage your site. This isn’t a great way to go about scanning sites though, especially since hacks are complex.This is probably why this is the one feature on NinjaFirewall that allows you to add custom rules or signatures, for malware or suspicious activity.

            NinjaFirewall has an interesting feature called Anti-Malware, that allows you to add custom malware signatures.
            NinjaFirewall has an interesting feature called Anti-Malware, that allows you to add custom malware signatures.


            NinjaFirewall has handy documentation for how to go about this. You will need to understand what to create signatures for, in order to make use of this feature.
            The Anti-Malware feature poses a couple of issue though. More on them here.

          2. Event Notifications
            The firewall logs any suspicious activity in the Firewall Log section, but you can set how often it alerts you, and what to alert you of:You can see exactly what triggers alertsThis way, if the Firewall blocks any attacks, you can see what happened, from the Firewall log. It’s always good to examine why/how it blocked the attack.and how often they come in.



          1. Login Protection
            Brute Force Attacks are a different thing altogether- NinjaFirewall has a separate option to help protect against these attacks: Login Protection.The option asks for HTTP authentication credentials, without which you can’t enable this option. You can also set the message displayed when the firewall blocks such attacks.
          2. Firewall Log
            It is what it sounds like: a log of everything NinjaFirewall found unusual, according to the rules you set in Firewall options. So if you’ve asked to be notified about any plugins updated, deleted or created, this log will contain all the details.
            NinjaFirewall's Firewall Log
          3. Live Log
            This feature monitors HTTP and HTTPS traffic on your site, so it aims at protecting against any traffic related attacks (like Brute Force, DDoS, or weird IPs trying to access your site.)
          4. Rules Editor
            NinjaFirewall has a set of ‘rules’ according to which it operates.NinjaFirewall has a list of in-built security rules.These rules are mostly signs, or signatures of attacks that it tries to prevent. According to NinjaFirewall’s documentation, the rules are downloaded from the WordPress.org repository, and the plugin doesn’t contact NinTech’s servers during the update process.The list that NinjaFirewall follows


            You can’t add your own rules, but you can modify them in the Firewall Policies section, if they’re greyed out in the drop-down.

          5. Updates
            This feature allows your installation of NinjaFirewall to be up to date. Setting the firewall up to check for security rules is a tradeoff between choosing your custom configuration, and keeping your site secure.
            Of course, you could ask to be notified about the changes and then go back to fix the changes so they suit your requirement though.
            This option checks for NFW updates



    What we tested it against

    We ran a series of tests to evaluate first-hand, the efficiency of NinjaFirewall, against some of the common attacks WordPress sites face. For this, we created a test-site (which would be the stand-in for your website): vulnerabilities we tested the firewall against were:

    1. SQL Injection

    The Firestorm real-estate plugin (actually v 2.03), is one that contained a vulnerability that allowed for SQL Injection. This plugin allows you to add real estate listings to your WordPress site.

    Testing NinjaFirewall against SQL Injection

    To exploit this vulnerability, we tried accessing entering SQL code into the Firestorm plugin to get data from wp_users. (For those of us who don’t know what wp_user actually does, it allows you to get data from, and modify both the roles and capabilities of WordPress users other than the admin.)

    Here is the SQL code we used: UNION SELECT 1, user_pass, 3, 4, 5, 6, 7, 8 from wp_users.

    Because this version of the plugin in vulnerable, it will execute the code to try and select the user credentials from users 3, 4, 5, 6 and 7.

    We used this in our browser’s address bar.

    (Note: This is why for this attack and the couple others following, we’re going to ask you to look closely at the address bar.)

    Running the test in the address bar

    Once we entered the same code into the address bar of the browser, this is what showed up on the test site (look at the address bar carefully, please):


    NinjaFirewall doesn't take entering SQL code into the address bar very lightly.
    NinjaFirewall doesn’t take entering SQL code into the address bar very lightly.


    But how did things work out behind the scenes of the attack?

    Firewall Log for SQL Injection

    This is what NinjaFirewall’s Firewall Log had to show us:

    How NinjaFirewall logged the SQL Injection attack


    Looks like the firewall had this exploit already in its list in the Rules Editor section, and hence it detected the exploit and prevented it from occurring too.

    2. Arbitrary File Upload and Local File Inclusion (LFI)

    There were a couple of vulnerable plugins that came to mind when we thought of Local File Inclusion. One was Slider Revolution (v 3.05), and the other was Gravity Forms (< v 1.8.19).

    We chose Slider Revolution though, because it allowed to make both exploits, and because more than 100,000 sites were attacked in 2014 through this plugin.

    Testing NinjaFirewall against Local File Inclusion

    The Slider Revolution plugin was used to perform Local File Inclusion on vulnerable websites in the following manner:

    Say the vulnerable site was called ‘victim.com’.

    The vulnerability allowed attackers to request the RevSlider plugin on the vulnerable site to show the images in the slider. Once it did that, the attackers would also try to figure out the structure of the WordPress directory. They would then get it to include files on the website’s local server (like the wp_config files) to the files it revealed. So the final URL entered on the site would be something like:


    We used a very similar approach to try and get the plugin to include the wp_config files of the website, and to reveal them.

    Here is how NinjaFirewall reacted:

    Running the test


    NinjaFirewall on Local File Inclusion: You shall not pass!
    NinjaFirewall didn’t let us perform a Local File Inclusion.


    Since the action got blocked, we just checked out the Firewall Log.

    Firewall Log for Local File Inclusion


    What NinjaFirewall's Firewall Log registered the LFI attack as
    This is what NinjaFirewall had to say about the attempt to include a file locally to the test-site.


    Testing NinjaFirewall against Arbitrary File Upload

    Again, trying to get to two attacks with the same plugin, we tried uploading random (or arbitrary) files to the test site. If the attempt is successful, the damage to the site would depend on the kind of file uploaded, and what it was intended to do.

    Take a look at the address bar to see what we’ve tried to do.

    Now don’t get confused… We named the files to be uploaded as “revslider” so that it would be accepted more easily by the plugin.

    Running the test


    NinjaFirewall successfully blocks Arbitrary File Uploads.
    We used Google Chrome’s extension to test the Arbitrary File Upload exploit. The exploit was unsuccessful


    Again, we only checked out the Firewall Log, since this attack was unsuccessful.

    Firewall Log for Arbitrary File Upload

    Here is what the Firewall Log said:


    The Firewall Log for Arbitrary File Uploads
    The Firewall Log for Arbitrary File Uploads


    3. Brute Force Attacks

    As mentioned earlier, to protect against Brute Force attacks, NinjaFirewall has a separate option called Login Protection.

    Testing NinjaFirewall against Bruteforce attacks

    Just to test its effectiveness, a colleague of mine, Vijay, tried launching a Brute Force attack against the website using Hydra, a tool that helps test websites and crack admin credentials.

    Running the test

    We launched a Brute Force attack against the site when we’d set the “Enable Brute Force Attack Protection” to “No”. This is what Hydra got us:

    Hydra was able to get the admin credentials from the site


    As you can see, the attack was successful, and Vijay was able to get the site admin’s login credentials.

    Then, we went ahead and enabled the Login Protection feature:
    Setting Login Protection to 'Yes, if under attack'
    Vijay then launched the attack again. This is what Hydra’s log said:

    Hydra was unsuccessful


    Firewall Log
    A quick look at how the attack was reported in NinjaFirewall’s Firewall Log (this shows how the attack was let through, and then stopped):

    the Firewall Log for Brute Force Attacks


    4. Remote File Inclusion (RFI), Arbitrary Code Execution, and Backdoors (a custom hack)

    We used TimThumb because it was a plugin that was widely used, and exhibited a vulnerability that allowed for millions of WordPress sites to get hacked. This test was therefore meant to check the basics of the firewall.

    Testing NinjaFirewall against Remote File Inclusion and Arbitrary Code Execution

    For this, we used the (currently defunct) Pict.Mobi widget, that used TimThumb (v 1.28) on the test site. Obviously since the RFI exploit would need a hackfile to be included from a remote location, we also created another site that would host the bad file.
    We took the approach a hacker would: we first confirmed that the (test) site used TimThumb, and that it used a vulnerable version.


    "Does this site have TimThumb?"- An optimistic hacker
    Most hackers looks for vulnerable plugins on your site.


    Then selected a very small file (in this case, it was a 16X16 .png icon), and modified it to contain PHP code.


    Modifying a small image to contain malicious PHP code
    Modifying a small image to contain malicious PHP code


    Next we used the TimThumb vulnerability to include the file remotely to the test site. Note that the file was PHP, which means that any time it was accessed, it would run.


    Including the malicious file remotely to our website
    Including the malicious file remotely to our website (notice the address bar!)


    Sure, it was an image file, so it could easily bypass the site’s usual sensors, but the PHP code could still be accessed, and executed.

    Testing NinjaFirewall against Backdoors

    We wanted to kill three birds with one stone, so we made sure to create an encrypted shell for the PHP code on the image before we uploaded it.

    Running the test

    We then extracted the code from the hackfile shell, just like a hacker would:


    Extracting code from the hackfile's shell
    Extracting code from the hackfile’s shell


    And then ran it.


    Executing the code. A three-in-one attack.The website gave us what we wanted.
    Executing the code. A three-in-one attack. The website gave us what we wanted.


    NinjaFirewall didn’t stop the attack.

    We think it was because NinjaFirewall has a list of rules for what attacks should look like, in a section called Rules Editor.


    A look at NinjaFirewall's Rules Editor
    A look at NinjaFirewall’s Rules Editor


    Click on the drop-down, and you see the list of rules that NinjaFirewalls follows:


    The Rules Editor has an extensive list
    The Rules Editor has an extensive list


    These rules are internal to NinjaFirewall, so you can’t see what exactly each rule entails.

    The attack we performed though, didn’t exactly go by the rules of how the attacks worked.
    The results of the tests are as follows:

    Firewall Log

    The log didn’t pick up on the hack. In fact, it only listed the backdoor we’d tested it for.


    The Firewall Log only registered the backdoor.
    The Firewall Log only registered the backdoor.


    File Check

    The firewall didn’t detect changes in files. We were still able to list the files in the WordPress directory.


    The firewall didn’t detect changes in files. We were still able to list the files in the NinjaFirewall's File Check resultsdirectory.
    What NinjaFirewall’s File Check showed up



    We didn’t expect this feature to remove the malware, because it’s only a scanner.

    Unfortunately, it didn’t find the infected files. We were under attack, and this is what the anti-malware feature said:

    What the Anti-Malware feature said
    What the Anti-Malware feature said

    Live Log

    No blips on this feature either.

    The results on Live Log
    The results on Live Log

    Unresolved issues with NinjaFirewall

    Since this is a review of the entirety of NinjaFirewall, we didn’t only test it against vulnerabilities. We also checked for issues other than those of protection. Most of these issues are documented on NinjaFirewall’s forum on WordPress, or on its online documentation.

    ● Anti-Malware scans time out

    The Anti-Malware feature on NinjaFirewall allows you to scan files in a particular directory for your site for malware (by default this is/var/www/html/wordpress/).

    The thing is, by default, this feature scans your site for malware in files that have been created or changed in the last 7 days. You can change the time period (or Timestamp) or even make it zero, in which case it scans your whole site.

    The options that Anti-Malware shows you
    The options that Anti-Malware shows you

    However, when if your website is on a shared host, there is one major problem you could face: the Anti-Malware scan timing out.
    The feature stops scanning your site after a certain time period that is set by your web host. This means that if you have too many files on your site, the scan will get cut short. Your site could never get fully scanned, unless you try some workarounds, (like this one suggested by the NinjaFirewall team). This is probably why NinjaFirewall’s Anti-Malware feature also has the two options of “Ignore file extensions” and “Ignore files/folders”:

    Working around NinjaFirewall's time-out issue
    Working around NinjaFirewall’s time-out issue

    While there isn’t anything NinjaFirewall can do to change the timing out of the scan, it is a huge drawback for users who want to scan their sites.

    ● The Anti-Malware feature uses only signatures to detect malware

    This is a widely-used method to identify malware and viruses, but it doesn’t catch everything. This is why most security scanners use it in combination with other approaches. Hacks utilize vulnerabilities on your site, but how bad code is run on your site depends completely on how hackers want to carry out the attack. So the ‘signature’ of malware could always be altered in small ways so as to escape detection. This is why, as we explained earlier, our exploit of the vulnerabilities in the Pict.Mobi plugin allowed for RFI, Arbitrary Code Execution and Backdoors on our test site.

    ● The firewall modifies .htaccess files

    NinjaFirewall backs up the PHP INI and .htaccess files that it has to modify, but modifying the .htaccess file in itself can wreak a lot of havoc on your site. The .htaccess file controls a lot on your WordPress site. One of its more obvious functions is access control (i.e. which users are allowed to your website), but it also dictates how files with certain extensions run on your site. This is why any minor slip-up with this file could cause your server to majorly malfunction. Just to be on the safer side, we recommend that you perform a backup of your entire site rather than just the .htaccess file. That way even if something breaks, you can always roll back to a working version of your site.

    ● Modifying the .htaccess files and php.ini files slows down your site

    .htaccess allows you access to the configuration of directories on your website even if you don’t have your hosting server’s (eg: Apache) main configuration file.

    This means, when your site is configured to direct traffic based on the modification made to .htaccess, Apache has to look for, and load all the .htaccess files on any request made to your site. As a result, your WordPress site’s load time increases.

    It’s a good way to direct traffic when your main server configuration file isn’t accessible, but otherwise it isn’t a great thing.

    ● The firewall interrupts backup operations regularly

    NinjaFirewall triggers false alarms when WordPress backup plugins are run, sometimes doesn’t allow backup plugins to backup the site. The firewall also has to be disabled before migrating your site to a new IP address.

    ● Can’t manually install NinjaFirewall

    As mentioned earlier, NinjaFirewall might log you out of your WordPress site and deny you access if you use an FTP client to make changes to it, or even uninstall it. Anything that you need to do with respect with this plugin has to be done from your WordPress dashboard.


    The NinjaFirewall seems like a powerful tool against known attacks that occur according to their signatures. But the thing is that most hackers know these signatures, and know that most security measures protect against these signatures. So they modify the signatures to perform more successful, and at times, most devastating attacks.

    Alerting of attacks after they’ve taken place isn’t something a lot of website owners can afford, especially with the damage hacks can wreck. However, having a hack-cleaner might help you scan for, and remove malware that causes the damage. In any case, it’s always important to have a dependable backup service for your WordPress site.
    Did you like this review of NinjaFirewall? Would you like to see other firewalls tested too? Let us know in the comments!

Permalinks, or permanent links, are the URLs that point to specific web pages on your WordPress site, be it individual posts/pages or category/tag archives. They are meant to remain the same, indefinitely. Permalinks are what people enter into their browsers in order to view your web pages, to read your content. They are what search engines (and other websites) use to link to your site. One can therefore say that permalinks are the gateways to your website that play an important role in overall site optimization.


The Default WordPress Permalink Structure

WordPress, by default, uses a permalink structure that takes the form of a URL followed by a query string that identifies the pertinent post ID. For instance, if N is the post ID number, the default WordPress permalink structure would be www.websitename.com/?p=N.

This default permalink structure is unreadable to humans, and hence, is termed to be ‘ugly’. Ugly permalinks are neither user-friendly nor search engine friendly. It is therefore recommended that you switch to a more SEO friendly WordPress permalink structure.

Other ‘Pretty’ Permalink Structures in WordPress

In addition to the default permalink structure, WordPress offers the following permalink structures for you to choose from:

Day and Name: Here, your page URL will include the year, month, and date that a post was published, followed by the post name.
Month and Name: In this case, your page URL will be two characters shorter than the previous case, as it includes only the year and month that the post was published, and of course, the post name.
Numeric: Here, your page URL will simply include the ID of the post (again, not very SEO friendly).
Post Name: Here, your page URLs will include the post name alone, making them short and memorable. And so, most WordPress users prefer to use this permalink structure for their websites.
Custom Structure: Here, you get to create your very own permalink structure by making use of one or more of the following structure tags:

%postname% – stands for the post slug
%post_id% – stands for the post ID
%category% – stands for the category the post was published under
%year% – stands for the year the post was published
%monthnum% – stands for the month the post was published
%day% – stands for the day the post was published
%hour% – stands for the hour the post was published
%minute% – stands for the minute the post was published
%second% – stands for the second the post was published
%author% – stands for the name of the author who published the post

Out of the structure tags mentioned above, the first six are more commonly used than the rest.


The above permalink structures are better organized than the default one, making it way easier for both visitors and search engines to navigate to your content. They help optimize your SEO and attract more and more users to your site. These permalink structures are often referred to as ‘pretty permalinks’.

Some Permalink SEO Tips

  • Include the post name in your permalink; it is what matters the most – from both SEO and user perspective.
  • Use simple and short permalinks that are less than 100 characters in length. So even if your article title is longer than usual, remember to cut it short in the URL, so that it falls within the 100-character limit (it’s best to use 3-5 words in the URL slug).
  • While it is advisable to include a keyword in your permalink, refrain from stuffing it with keywords (that’s just shabby).
  • Avoid using stop words (like a, the, is and are) in your permalinks. For instance, if your article title is ‘Stop using stop words in your permalinks’, you can leave out ‘in’ and ‘your’ from your page URL.
  • Use hyphens as separators, not underscores. So, for the article title mentioned above, a good page URL would be: www.websitename.com/stop-using-stop-words-permalinks.

Changing Permalinks on a Live Site

It is wise to choose a permalink structure for your WordPress site at the beginning itself. Changing the permalink structure of a live site, especially one that’s been running for more than six months, can drastically affect your SEO rankings. If you want to change your permalinks and avoid antagonizing users and search engines, here’s what to do:

  • change the page URLs from the back end
  • 301 redirect all the previously used URLs

To ensure that you don’t mess up, it’s a good idea to make a complete list of the previous URLs as well as what they’ll be redirecting to. And if you don’t want to get your hands dirty, you can always hire a professional to setup the redirects for your site. In spite of all this, you’ll still be losing all your social media share counts though, no changing that.

Wrapping Up

A pretty permalink structure is no doubt more user-friendly and SEO-friendly than the default one WordPress provides. It is always advisable to define your website permalink structure right at the beginning of your WordPress journey. However, if you should ever reach that point on the road where updating the permalink structure of your site means better SEO, then go for it! Just make sure to properly redirect your old URLs to the new ones.

And yeah, do remember to keep your site completely backed up before changing the permalink structure on your live site.



We at blogvault arrived at a situation where we needed to convert some of our pages into posts. One’s common sense will tell to create a new post – copy everything from content to title as in page to the new post – delete the old page and finally publish the post! This should work great is your permalink is set to wordpress default (or you have some custom setting that handles it somehow using the id). But in our case our permalink setting was:


Post namehttp://


So when we visited the new (post) link after deleting the old page, we got 404 – Page not found!


Understanding the issue

As you can see the same thing works for a particular permalink setting but fails for another. This can be explained as – wordpress maintains a common (database) table for both post and page under the name ‘wp_posts’. As each entry in the table has its own unique id, when we try to locate them using id in permalink (as wordpress default) we face no problem.

However its not the same with our permalink setting. Due to some reason, on deleting a page (or post) from admin panel, wordpress does not immediately remove their corresponding entry from the database. So when resolving the address by post name, wordpress finds the earlier entry (page in our case) which is marked deleted, hence giving the 404 not found error.



One simple solution is using plugins exclusively made for this purpose. Some of them are:




However incase you don’t mind getting your hands dirty and saving your site with the load of extra plugin, you can follow these steps (with extreme precautions).

  • Get access to your wordpress database. You may use phpmyadmin for that.
  • Open the wp_posts table.
  • Locate your post entry and replace its ‘post_type’ from ‘page’ to ‘post’ or vice versa.


Incase you already created a new post as in our case and are now getting the 404 error, simply delete your earlier (deprecated) entry.

SQL query for same will be:

Post to page

UPDATE wp_posts SET post_type=’page’ WHERE id=<your_post_id>;

Page to post

UPDATE wp_posts SET post_type=’post’ WHERE id=<your_post_id>;


Hacked - A Perspective
Image Credit: Johan Viirok Creative Commons license BY 2.0

Couple of days earlier, a team member pointed out to a discussion in a WP community on Facebook. The lady in question had suspicious files in her site due to a broken plugin. She poured out her doubts, feelings as well as queries for the fix she needed through multiple posts. That underlying feeling of being trapped, of being cheated was unmistakable. It was akin to having someone break into your house whilst you are still there and enjoy your property at your expense, unknown to you. She admitted to feeling bad and understandably so.  Since the only alerts that she was used to, were plugin updates, the shock of it all was only too imaginable.

What had happened, in brief was, that on logging in, she noticed a security alert, which she verified with another security check. One can only imagine that she was sincerely hoping and praying that the worst was not true and it was just some overlooking on her part.

That was however not the case. She quickly started posting on what she thought were the options open to her.

Image Credit: Berishafjolla licensed under Creative Commons Attribution-Share-Alike 3.0 Unported license. Source:http://www.knowledge-commons.de/en/the-non-experts-are-the-real-experts-open-innovation-talk-at-republica/
Image Credit: Berishafjolla licensed under Creative Commons Attribution-Share-Alike 3.0 Unported license.

The first option was to review logs for which each entry would have to be checked from the back-end so as to find the issue at hand. This could be impossible if there is too much data to go through or limited information at hand. There are cases where the logs are lost or may be difficult to decipher.

Secondly, she could backup, do away with the contents of the problem site and restore. However, what if the backup also had the hack? How does one be sure that all contents of the backup are clean? The only way to do this, would be to run a security check after restoring.

It was only too obvious that she was thinking loudly through her posts and that  these were the multiple thoughts running through her mind. The community reached out to her. Common solutions given were:

a) to back up everything- this is useful especially since a backup can save much time and effort in restoring a site.

b)  update all plugins – Often older versions of plugins contain vulnerabilities which are exploited by hackers. Hence it is advised to update the plugins to their latest versions.

c) clear cache.

d) look in Temp folder – Hackers at times upload malware in the temp folders and hence cleaning them is advisable.

e) Look for files with suspicious code. Malware at times contain certain strings like base64_decode or eval. Searching for files with such code can help identify malware too.

  Image Credit : Zsolt Biczo/Shutterstock
Image Credit : Zsolt Biczo/Shutterstock

The above mentioned are good points to follow. Read up to know more on what to do  when your WordPress site gets hacked.

The lady got back shortly with a second post wanting to know if she should access files through FTP or SFTP or take backup and restore her site. One suspected malware and she double checked every move she made. Loss of faith would be the natural thing in such cases, it is after all a breach of security.

She was unsure whether she should access the WP admin or not. One needs to be wary of logging into the admin when hacked since the hacker might have left some code to track the password used to login. The above is a possibility. For safety in such cases, the password can be changed using phpMyAdmin or FTP before logging into the WP Admin.

She got helpful responses for her second post as well. It was really heartening to see so many people reach out to someone, eager to help out. That set the ball rolling. She posted each step of action taken, waited to hear back on comments so that she could gauge her way out of the mess her site had become.

She was not only somehow wanting to fix the issue but also keen to find out where the issue started first. She seemed to be taking notes on what to do and what not to do going forward. The nomenclature of the diseased plugin seemingly added to the confusion and frustration. The site appeared to have been affected by the Slider Revolution hack

At the end of the week, when it was thought that an issue had been solved, lessons had been learnt, she posted again. She had received an alert about the installation of a plugin that her host had added to her freshly cleaned site. Clearly, she had hit the panic button hard. Help was at hand, so was empathy. The community member who had suggested she check changes on her site with her host, also posted that he imagined being in her shoes and it was not a good feeling. She stated that her host provider was frequently updating plugins without permission. While that may be part of the problem, it is not the core issue.

Though she had zeroed in on the folder with the malware, the key concern would be to find out  how the break in happened and fix it accordingly. Frequent security checks and identifying possible hacks can save you from a lot of grief.

All in all, a scare, though very unpleasant to recount, does keep us on our toes. So, how do you protect your site?

WP to Twitter

As soon as you have a new post ready on your website, it would be great to update your twitter followers so that they can read the post. It is very convenient to be able to do this automatically whenever you have a new post. There are several WordPress plugins that provide this functionality. Let us take a look at one such plugin –“WP to Twitter”. This plugin can be searched and installed from the WordPress plugin repository.

This plugin connects your WordPress website to your twitter account so that a new post can be automatically tweeted. Once installed and activated, this plugin is ready to be configured with your Twitter API keys and Access tokens by creating a Twitter application.

WP to Twitter options

We shall see how to obtain the keys from thetwitter applications registration page. Fill in the application name and your website URL (the Callback URL also needs to be the same) to create the twitter application.

Create an application

Your Twitter consumer keys will now be created. Please note that it should not be shared with anyone.

Twitter App settings

Here you can see that the default Access Level is “Read-only”. If you want your Website to post to Twitter automatically, you will need to have “Read-Write” permissions. Change this by clicking on “Change App Permissions” link or button above. Or you could do it from the “Permissions” tab as well. You can then create the access tokens by using the button – “Create my access token” at the end of the page.

Create Access Tokens

You will get the tokens displayed on the next page. This again should not be shared with anyone. Make a note of these tokens and keys and enter them on the WP to Twitter plugin settings on your dashboard.

Connect to Twitter

You have now successfully connected your website to Twitter. There is an option to shorten URLs as well. There are also advanced options to set up Google analytics, Add custom texts before or after tweets, chose not to send tweets by default etc. You can also select which category of posts you would like to publish.

Once the settings are saved, you will now see your posts beings updated on your Twitter account.

You can also change the settings using the metabox available on the right sidebar of your post editor. You can customise your Twitter post, or chose to not tweet this particular post.

sidebar options