Wordpress

Fix For WordPress Heartbeat and Cron

Here is some Fixes to try if  admin-ajax and wp-cron are consuming too much resources on your hosting account

Lately I have been getting 504 gateway errors when I am editing pages in my blog here.
It turned out they are caused by hostgator limiting the resources on my hosting account due to excessive CPU . The support team sent me information that showed which files were causing the excessive CPU and Memory usage.

Fix WordPress from consuming too many hosting resources

Fix WordPress

 

upon examining the information I could clearly see that 2 files were being accessed excesively which were wp-cron and  and admin-ajax.php

the issue is relatively easy to fix but requires some editing to some files..

Hostgator support took care of the first problem for me which was to disable wp-cron from automatically firing and setup linux based cron for me

here is what the support team said about it:

By default, every time someone loads your site, the wp-cron.php file is run.
Most of the time, this isn't harmful. But if your wp-cron.php file is set to do some intense tasks, this can drive up resource usage.

Thus, you should convert the wp-cron.php task into a Linux cron job.
This is actually easier than you think. You simply need to have the Linux cron job utilize wget once an hour on the file via your URL.

So let us say your URL is http://example.com . Then the URL needed to call would be http://example.com/wp-cron.php?doing_wp_cron .

Since you don't want a million emails letting you know it run, you want to add 2>&1 at the end. Then we just want to call that via wget quietly.

Since we only want it running once per hour,

the coding for the cron job becomes:
0 * * * * /usr/bin/wget -q -O - http://example.com/wp-cron.php?doing_wp_cron 2>&1 Add that as a Linux cron job,

then add the following to your wp-config.php file:
define( 'DISABLE_WP_CRON', true );

 Have a Heart WordPress

The second issue is about admin-ajax.php being hammered. researching this I found out that wordpress heartbeat is a problem. I have a habit of having multiple tabs open with various admin pages left open. it seems that means wordpress heartbeat is in action for every page consuming cpu even when nothing is happening.. I found this article about it http://www.inmotionhosting.com/support/website/wordpress/heartbeat-ajax-php-usage

which I have recreated here so that I have a reference handy if this issue should arise on any of my other wordpress sites:

 
Wordpress Heartbeat

Slow down your WordPress Heartbeat

 

Introduced in WordPress 3.6 the WordPress Heartbeat API allows WordPress to communicate between the web-browser and the server. It allows for improved user session management, revision tracking, and auto saving.

The WordPress Heartbeat API uses /wp-admin/admin-ajax.php to run AJAX calls from the web-browser. Which in theory sounds awesome, as WordPress can keep track of what's going on in the dashboard.

However this can also start sending excessive requests to admin-ajax.php which can lead to high CPU usage. Anytime a web-browser is left open on a page using the Heartbeat API, this could potentially be an issue.

WordPress Heartbeat API in action

Something handled by the WordPress Heartbeat API is the main WordPress admin dashboard page itself. If all you did was login to WordPress and then minimized that window and started working on something else, you'd see requests for admin-ajax.php in your site's access logs.

At [00:29:30] I logged into the dashboard, and you can see the initial GET /wp-admin/index.php request.

Then at [00:30:31] the WordPress Heartbeat API sends a POST /wp-admin/admin-ajax.php Heartbeat request.

With the WordPress dashboard in focus, a Heartbeat request should be spaced the max of 60 seconds that the API allows for. If the dashboard is out of focus, the Heartbeat requests space out to 120 seconds between them.

00:29:30 "GET /wp-admin/index.php "http://example.com/wp-admin/index.php"
00:30:31 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:32:03 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:33:03 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:34:03 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:35:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:36:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:37:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:38:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:39:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:40:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:42:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:44:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:46:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:47:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:48:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:49:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:50:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:51:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:53:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:55:08 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:57:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
00:59:04 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
01:01:05 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"
01:03:05 "POST /wp-admin/admin-ajax.php "http://example.com/wp-admin/index.php"

Now each of those POST requests had a corresponding PHP script execution on the server using CPU time:

php-cgi 0.26 secs Wed Feb 19 00:29
php-cgi 0.26 secs Wed Feb 19 00:30
php-cgi 0.23 secs Wed Feb 19 00:32
php-cgi 0.20 secs Wed Feb 19 00:33
php-cgi 0.22 secs Wed Feb 19 00:34
php-cgi 0.24 secs Wed Feb 19 00:35
php-cgi 0.20 secs Wed Feb 19 00:36
php-cgi 0.23 secs Wed Feb 19 00:37
php-cgi 0.23 secs Wed Feb 19 00:38
php-cgi 0.26 secs Wed Feb 19 00:39
php-cgi 0.22 secs Wed Feb 19 00:40
php-cgi 0.23 secs Wed Feb 19 00:42
php-cgi 0.22 secs Wed Feb 19 00:44
php-cgi 0.23 secs Wed Feb 19 00:46
php-cgi 0.25 secs Wed Feb 19 00:47
php-cgi 0.27 secs Wed Feb 19 00:48
php-cgi 0.23 secs Wed Feb 19 00:49
php-cgi 0.22 secs Wed Feb 19 00:50
php-cgi 0.21 secs Wed Feb 19 00:51
php-cgi 0.21 secs Wed Feb 19 00:53
php-cgi 0.21 secs Wed Feb 19 00:55
php-cgi 0.24 secs Wed Feb 19 00:57
php-cgi 0.25 secs Wed Feb 19 00:59
php-cgi 0.22 secs Wed Feb 19 01:01
php-cgi 0.23 secs Wed Feb 19 01:03

Having our dashboard open for over a half hour, generated 25 PHP script executions. With a total usage of 5.77 CPU seconds. Not terrible, but not great either, since we used up CPU essentially checking for nothing to happen.

Disable WordPress Heartbeat API

If you notice that you are having an excessive amount of admin-ajax.php requests, the WordPress Heartbeat API can be disabled to prevent this type of activity from happening automatically.

By default WordPress uses the Heartbeat API to manage things such as post locking so only one admin can edit a post at once, it's also used for auto saving. Going forward the API could be used more and more by WordPress developers to handle certain tasks, so keep this in mind if you choose to disable it.

Navigation:

Locate your functions.php script

To modify the behavior of the Heartbeat API, locate your WordPress theme's functions.php script.

I'm using the default twentyfourteen theme, so my path looks like:

/home/userna5/public_html/wp-content/themes/twentyfourteen/functions.php

Make a copy of this file, something like functions.php-BAK for safe keeping.

Disable WordPress Heartbeat everywhere

Towards the top of the functions.php file, add the highlighted code to disable the Heartbeat everywhere:

 * @since Twenty Fourteen 1.0
 */

add_action( 'init', 'stop_heartbeat', 1 );

function stop_heartbeat() {
        wp_deregister_script('heartbeat');
}

/**
 * Set up the content width value based on the theme's design.

Disable WordPress Heartbeat just on Dashboard page

To selectively disable the Heartbeat API on certain pages, you can use the global WordPress $pagenow variable to tell what page a user is on. Along with an if statement to tell WordPress if the Heartbeat API should be used.

You can check if the $pagenow variable is a specific page, and if so turn off the Heartbeat:

add_action( 'init', 'stop_heartbeat', 1 );

function stop_heartbeat() {
        global $pagenow;

        if ( $pagenow == 'index.php'  )
        wp_deregister_script('heartbeat');
}

Disable Heartbeat everywhere except post.php and post-new.php

You can also check if the $pagenow variable is not set to specific pages that you would still like the Heartbeat to happen on, such as post.php or post-new.php, and then turn off the Heartbeat on every page but those.

add_action( 'init', 'stop_heartbeat', 1 );

function stop_heartbeat() {
        global $pagenow;

        if ( $pagenow != 'post.php' && $pagenow != 'post-new.php' )
        wp_deregister_script('heartbeat');
}

Then just save your functions.php script, after choosing where you'd like the Heartbeat to be disabled.

Delay WordPress Heartbeat requests

You can also leave the WordPress Heartbeat API enabled for all of your pages, and just slow down the rate at which requests happen by modifying the WordPress Heartbeat JavaScript file.

This can be a great method to use if you'd still like to have all the functionality that the Heartbeat API provides by default, but still reduce the overall usage it requires to run.

Change the rate of the default Heartbeat requests

First make a backup copy of this file:

/home/userna5/public_html/wp-includes/js/heartbeat.min.js

Now it can get a bit tricky due to this JavaScript file being minimized, but essentially you want to find the 3 separate cases for request activity, 15 seconds, 30 seconds, and 60 seconds and increase the time of all of these.

In all the examples below, the ...'s indicate that there is other code you don't need to edit in-between the parts you do need to edit.

15 Second requests

To extend the default behavior of having a Heartbeat request every 15 seconds, you would look for this code:

B.mainInterval<15?B.mainInterval=15:...case 15:

Change it to something like 120 to extend Hearbeat requests out to 2 minutes by default:

B.mainInterval<120?B.mainInterval=120:...case 120:

30 Second requests

To extend the behavior of having a Heartbeat request every 30 seconds, you would look for this code:

case 30:...30,b=1>b||b>30?30:

Change it to something like 300 to extend Hearbeat requests out to 5 minutes:

case 300:...300,b=1>b||b>300?300:

60 Second requests

To extend the behavior of having a Heartbeat request every 60 seconds, you would look for this code:

B.mainInterval>60&&(B.mainInterval=60))...case 60:...mainInterval:60

Change it to something like 600 to extend Hearbeat requests out to 10 minutes:

B.mainInterval>600&&(B.mainInterval=600))...case 600:...mainInterval:600

You should now hopefully understand what the WordPress Heartbeat API is, and how you can control it in the event it's causing too many requests to your admin-ajax.php script.

How to Fix WordPress Blank White Screen | WordPress, blank white screen

So your WordPress site is suddenly Not Working,

http://blog.gameznet.biz/wp-content/uploads/wordpress_tips_full114.jpg

All Your seeing is a blank White Screen

Don't worry all is not lost!

These tips apply for all WordPress version. WordPress is one of the most used and powerful blog engines. And with the all community support, many plugins are developed to make WordPress more powerful and feature rich. But not all plugin developers code their plugins to WordPress standards and sometimes this will create problems with the most annoying problem being a blank page error.

No error message, just a white blank screen. The first tip is “don’t panic“.

Analyze your website in these steps:
1. Check your hosting server

The first step is check your hosting server by going to your server administration (usually cpanel). Check if that’s live or not. If not then contact your hosting server support.
If alive then the problem is likely to be on your blog.

2. Check wp-admin

Check your wp-admin folder by go to http://www.yoursite.com/wp-admin
See if it is alive and not blank.
If it is not blank, then your WordPress doesn’t have a problem.
You can check your themes and files on the root folder. If it is blank, then there are lot of possibilities, but most of the time it is plugins and themes.

3. Check for index.html and .maintenance files
Yes, check if there is a blank index.html in your root folder.
I know it seems odd but if there is a blank index.html in the root then it may be the culprit. Delete it and check your site again.

If your wordpress site is stuck with a "Maintenance Message" go to the root of your instalation and delete the file .maintenance and check your site again, that may fix the problem, if not keep going.

 

4. Check error_log

Open your favorite FTP client program then downoad error_log file at the root of your blog. Analyze it, see what make your blog errors. Usually i found out what make it errors in this file. Usually it will be a memory problem, file not found problem, and so on. Pay more attention to the error message and fix it.
5. Fix: WordPress Memory Exhausted Error – Increase PHP Memory

If you see sometimes a WordPress Memory Exhausted error showing up after activating or updating a new plugin or doing some other task. Usually the error looks like this:
Fatal error: Allowed memory size of xxxxxxx bytes exhausted (tried to allocate xxxxxx bytes) in /home4/xxx/public_html/wp-includes/plugin.php on line xxx

This error occurs as WordPress tries to access more memory then it is allowed to by the “Server PHP configuration” or “WordPress Setting”. Increasing the Memory Limit will solve it.

There are numerous solutions for it, but for this article lets just look at the simplest one of all. Open your wp-config.php which is located in the root WordPress directory.

Look for the following line: $table_prefix = 'wp_';

imediatly after that line add the following line:
define('WP_MEMORY_LIMIT', '64M');

(or higher value if required)

If you still get the error after this fix, you may have to contact your host and ask them to increase your memory limit.
This is not a complete fix since your blog will be using more resources than it should which if you have a lot of traffic may become a major problem and could get your hosting account suspended so it is best to resolve this issue properly. The memory problem is most commonly caused by a plugin so you might want to remove the last plugin that you installed by deleting the plugins folder from your wordpress /plugins directory or moving it temporarily outside of the plugin directory.

Next go back and change the memory limit back to 32 by commenting out the line you entered into your wp-config.php and then see if things work, if they do then it definately is that particular plugin giving you the memory issue. Best not to use it but also best to contact the plugin creator and let them know of the issue so they can work on it.

Depending on your needs, server condition, plugins installed, and size of your site, you could use 32M, 96M, 128M, 256M, 512M, 1024M, 2048M, 4096M.
Make sure your server allows you to use that much dedicated memory, if your unsure contact your host and ask.

If you have access to your PHP.ini file, change the line in PHP.ini
If your line shows 32M try 64M:
memory_limit = 64M ; Maximum amount of memory a script may consume (64MB)

If you don’t have access to PHP.ini try adding this to an .htaccess file:
php_value memory_limit 64M

If all else fails contact your webhost support or the person managing your server.

 

6. Rename plugin dir

To check if there is an error with any individual plugin, rename your /plugins/ folder and create a new empty one.
Now access your wp-admin. If the wp-admin show up, then it is definatly a plugin error. Now it’s your job to find out which plugin is causing the issue.
You can move your plugins back into the new plugin folder one at a time . Make sure its active and then check your site.

 
7. Check all the plugins

To check all the plugins, use cpanel to move all plugins into a temp directory.
(I usually just rename the plugin directory from plugins to plugins_OFF then create a new folder called plugins)
Now put them back one by one into the empty plugins folder, and check wp-admin each time until the blank page error comes back.
When it does you will know "that is the offending plugin"
Get rid of it, if you think you need it then contact the plugin creator for support.

So like i said please don’t panic, check all your installation, plugins and themes folder.
If it is still not working, contact your hosting support and ask them to help you.

Cannot Upgrade Plugins

If your having trouble Upgrading a Plugin and in particular getting an error when you run the automatic update feature for plugins and themes that says something like: could not create directory. /public_html
Try deleting the upgrade directory found within wp-content/upgrade and then recreate it manualy.
Also chmod wp-content/upgrade to 777 and see if that fixes the problem.

I have had to do this on several wordpress 3.0 sites, not sure why it happens but this has fixed the issue for me.

How to Fixing WordPress has_cap error notices | has_cap error,wordpress

 

http://blog.gameznet.biz/wp-content/uploads/error_button39.png

 How to Fix the common has_cap error notices in your WordPress site

A  common error that is popping up a lot with later versions of wordpress looks something like this:

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/xxxx/public_html/wp-includes/functions.php on line xxxx

this can usually be traced back to a plugin and  the error may only show when debug mode is turned on in your wp-config.php file

Often the recommended fix is to simply get rid of these errors by turning off debug mode but that does not fix anything, it just stops the error from being displayed on the site.

I prefer to leave debug mode on and actually correct any errors.

These kinds of errors seem to result as an incompatibility problem with some functions like "get_options" that are no longer  working correctly with wordpress 3.0. and above.
Perhaps the functions work ok but the parameters are no longer correct.

 

To find the solution we need to disable plugins one by one, until you find the one that is causing the warning. Then, find a call like "add_submenu_page" or "add_options_page" or similar, that is using a numeric user level instead of a capability name. Substitute the numeric user level with a compatible capability or user role and the warning should vanish.

Here is an example using WP v.3.2.1 and Audio-Player v.2.0.4.1 plugin which was giving this error:

To fix this problem you need to edit the plugin file, you can do this via cpanel by navigating to the file and using the cpanel file editor, or download the file and edit it in a text editor such as notepad or edit it directly from within wordpress which I find the quickest method.

go to line 176 of audio-player.php (/wp-content/plugins/audio-player/audio-player.php)

of course other plugins will require some searching to find the correct line but you will be looking for a similar line which starts with
"add_options_page" or add_submenu_page"  The line will look something like this: $pageName = add_options_page  

Moving on with the example...

Once you have the file open in your chosen editing method:
$pageName = add_options_page("Audio player options", "Audio Player", 8, $this->optionsPageName, array(&$this, "outputOptionsSubpanel"));

Change the 8 (a numeric user level) to 'activate_plugins' (single quotes included), so that the line looks like this:
$pageName = add_options_page("Audio player options", "Audio Player", 'activate_plugins', $this->optionsPageName, array(&$this, "outputOptionsSubpanel"));

 

so for a different plugin simply do a search for "add_options_page" and loog for a number value being used (8 in the above example)
change 8 to "activate_plugins"
..  save and hopefully your error has gone.

This is only one particular fix for the above specific plugin which was using the number "8" instead of "activate_plugins"  in relation to  add_options_page

------------------------------------------------------------------------------------------------------

Troubleshooting Other Plugins

The main issue seems to be a problem with defining roles and capabilities within WordPress.

When we register a new user we can define their roles (Admin, Super Admin, Editor, Contributor, Subscriber).
Each of these roles has different skills (reading a page / post, edit a page / post, add a page / post, etc)
To learn more about the roles and capabilities provided useful wordpress codex: http://codex.wordpress.org/Function_Reference/add_menu_page

If we have a plugin or template that generates a new menu in our back end functions such as safely used add_theme_page, add_menu_page, add_submenu_page, add_options_page etc

Consider the statement of one of these functions
<? Php add_menu_page ($ page_title, $ menu_title, $ capability, $ menu_slug, $ function, $ icon_url, $ position);?>

The third parameter, $capability, accepts as a value that defines the different capabilities of WordPress. This menu gives access to only users (roles) that have that capability.

The error in question is generated because we do not pass a value of type capacity, we offer a value of type User Level, the old system to limit user roles.

IMPORTANT: The user levels ceased to be used in WordPress 2.0 and in WordPress 3.0 they were completely eliminated.
If a plugin developer has not updated their plugin then you will get these errors.
Read more here: http://codex.wordpress.org/User_Levels

In case you do not understand much I'm posting a link which helped me to understand that this was the problem: fix-notice-has_cap-was-called-with-an-argument-that-is- deprecated-since-version-2-0-in-wordpress /

Using any numeric setting for the capability setting will cause the infamous error notice.

So for example, using 10 versus 'manage_options' will cause this same kind of error notice.

when troubleshooting your plugins use the table at the bottom of http://codex.wordpress.org/Roles_and_Capabilities#User_Level_to_Role_Conversion to figure out the right string value.

If you have shell access you can also run this command on your plugins directory to find all of the plugins suffering from the same condition:  

(change number values as required eg you may need to enter number 10 instead of 0-9 )

grep -HnR "add_[a-zA-Z].*_page.*, [0-9]*," ./

 I ran that command over my plugins directory and found 14 plugins using the old numeric role identifier :-/ .

I have come across this error in many plugins. Often reporting the error to the plugin developer will help them become aware of the issue and it is relatively easy for them to address it and bring their plugin up-to-date. otherwise you can fix it within your plugins yourself however do be aware that if the plugin later gets updated by the developer within the wordpress repository without the correct fix for this issue being applied and you then run the automatic plugin update then your fix will get overwritten and the error will return so it is always best to notify the plugin developer and get them to  fix their plugin at the source. You can always fix it yourself and then provide the developer with the information about how you corrected the problem manually on your own site and most developers will more than likely be grateful for you taking the time to notify them and make their job easier by even giving them a fix.  To do this you can visit the plugins page in the wordpress repository and visit the developers support  forum or send them an email.

 

What is Blog Curation

sensitive noise / obvious 2

The Question about what is Blog Curation can be easily answered by watching a master content curator at work.

 [youtube_1_simple_video refresh="never" keyword="Page One Curator Demo"]

Page 1 Curator

 

What is Blog Curation?

Problem: Getting rankings and traffic is the challenge of any one trying to sell online.  Almost all SEO relies on spammy techniques and strategies to get links and rankings.  Given the recent spate of Google de-indexing / Panda 3.2 / Penguin – there is huge pent up demand for for a new solution that is white hat and designed to last for the long term.

Solution: Instead of gaming Google – this plays by its own rules to get huge rankings for competitive words.  This method and software enables you to curate multiple blogs remotely and create whole empire of cash and traffic generating websites for passive income or to sell to investors.

Market: Curation is exploding as a technique to create authority sites for bloggers, SEO experts, niche and authority site builders and in fact anyone making money online.

Look at these:  

Drudge Report: $30 million per year.

Perez hilton… – worth 32 million

Huffington post – bought by AOL for $315

What do they have in common? .. none of their own content.. it was all curated.

 Page 1 Curator

The Products

Page 1 Curator

The App: The software on the front end is a desktop app written in AIR.  This app will search over relevant content sources based on your keyword, allowing you to CURATE a post that has text, video and images – together with the relevant backlinks that ensure the Google love.

The Course: Curation Masterclass – This is a comprehensive course on curation that caters for advanced curators and newbies.  It covers all strategies to enable an individual to create their curated blog empire.

Curation Mastermind Coaching; 1 to 1 Skype coaching on curation.

The WordPress Plugins:

SyndicatorPRO - this sits on the actual blogs themselves and automatically performs the manual tasks of social and web 2.0 bookmarking – so essential in todays post panda world.

PageOne LeadMagnet:  The optin plugin essential to capturing options on curated blogs.

The Forum: Already in use – this is where the action happens and where members can share their experiences.

Page 1 Curator

 

8 Tools for Managing WP Multisites | multisite

Here are some resources for anyone managing several websites or clusters of sites  worpdress multisite may be your ideal solution and there are plenty of tools to automate and streamline.

Not listed in any particular order or preference.

If you run more than one WordPress install, or if you have clients that run WordPress sites that you’re responsible for, then you know how much of a pain it can be to log in to each site every time you need to do things like update plugins, themes, or WordPress core itself.

With the release of WordPress 3.0, we now have the ability to create a network of WordPress sites with one installation through the multisite feature.

Managing multisite WordPress Domains is getting easier.

With the release of WordPress 3.0 and its multisite feature, you can run multiple sites from a single WordPress installation and create a network of sites. However, if you run several websites with a variety of requirements, your needs may exceed what multisite allows you to do. Fortunately, there are a number of available solutions.

Here is a list of tools for managing multiple WordPress websites from a central location. There are WordPress dashboards, as well as multisite tools to manage domains, themes, campaigns, and more. Nearly all of these tools have a free option.

1) WP Multi Network

WP Multi Network Plugin on WordPress.

WP Multi Network Plugin on WordPress.

WP Multi Network adds a network management user interface for super admins in a WordPress multisite environment. Turn your multisite installation of WordPress into many multisite networks, all surrounding one central user base. Create new networks of sites, allowing for many site, network, and domain arrangements. Price: Free.

 

2) ManageWP

ManageWP

ManageWP has an array of free features (e.g. one-click updates and a centralized admin dashboard). This tool allows you to manage up to five websites for free. There are also three premium plans that start at $4.00 (for up to five websites) that give you access to ManageWP’s premium features.

ManageWP.

ManageWP.

ManageWP is a WordPress management console that includes one-click access, monitoring, backup, deployment, publishing, and security features. Review which of your sites have themes and plugins that need attention. With one click, update all of your plugins, themes or core WordPress software. Get uptime monitoring, traffic alerts, SEO analysis, Google Analytics integration, and more. Manage your sites from your smartphone with the free iOS app. Price: Free plan for up to five websites; with paid plans, choose how many websites you want to manage

Here’s a video from ManageWP to help give you an overview of the tool:

ManageWP Free Features

  • One-click updates
  • All sites in one dashboard
  • One-click automatic login to your WordPress sites
  • Install and manage plugins and themes
  • Remove spam comments, post revisions, optimize databases
  • Pageview site traffic statistics
  • Email notifications for available updates
  • IP address access restriction
  • Two-factor login authentication via email

ManageWP Premium Features

There are three paid plans above the free plan. With each paid subscription plan, you can have as many sites as you like. The difference comes in the features available. Check out ManageWP’s plans and pricing web page to see the difference between subscription plans. (By the way, you can try all the features for free for thirty days.)

Below are a few of the more important premium features available.

  • Manage users
  • Bulk add new posts and pages
  • SEO analysis
  • Integration with Google Analytics
  • Uptime monitoring
  • Scheduled backups

 

 3) InfiniteWP

InfiniteWP

InfiniteWP is on a freemium model. (In other words, basic features are free, but you’ll need to pay for other feature upgrades such as auto-scheduling of WordPress site backups.)

Below is a video by the creators of InfiniteWP that will give you an idea of what the tool looks like:

InfiniteWP Free Features

The basic features of InfiniteWP are basic indeed, but they’re also pretty handy, and so many of us may not need the premium/paid features this plugin has. The basic features include the following:

  • One-click updates for the latest version of WordPress
  • Install and manage themes
  • Install and manage plugins
  • The ability to restore, download, and delete backups

InfiniteWP Premium Features

There are currently six available premium features available (with three more in the works). These are the currently available addons:

  • Install WordPress
  • Clone a WordPress installation
  • Schedule automated backups
  • Back up to repositories
  • Manage WordPress users
  • Save and run custom PHP code on multiple sites
  • Brand the InfiniteWP plugin with your company name or hide the plugin altogether

The premium addons currently in the works are the following:

  • Integration with Google Analytics
  • Manage posts and comments on multiple sites
  • Bulk create Posts, Pages, and Links

 

 

InfiniteWP.

InfiniteWP.

InfiniteWP allows you to manage multiple WordPress sites with single master login, one-click updating and managing for plugins and themes, and instant backup and restore. The basic features of InfiniteWP are free, but expanded features are available as premium add-ons.

Currently there are six add-on packages, with an assortment of features for multiple sites, including schedule backups, manage user groups across sites, run custom code snippets, and client plugin branding. Additional features are in the works, such as Google Analytics access, manage comments, and bulk pages and links. Price: Basics are free; add-ons start at $49.

 

4) WP Remote

WP Remote

WP Remote is a simple and free solution that will allow you to do a few basic tasks related to managing multiple WordPress sites.

While you do need to install the WP Remote plugin for each WordPress installation, your administration panel for managing your sites is in one central location on the WP Remote site.

Here’s a look at the simple control panel on the WP Remote site:

WP Remote Features

  • Bulk update all WordPress installations
  • Create off-site backups
  • Update plugins that can be updated via the WordPress plugin page
  • Update themes that can be updated via the WordPress themes page

WP Remote.

WP Remote.

WP Remote is a free tool to monitor and manage all of your WordPress sites. Add an unlimited number of sites. Organize sites into groups for quick search. Monitor and update WordPress, plugins, and themes. Backups are stored on encrypted servers. WP Remote site is now optimized for managing from mobile devices. Price: Free.

 

5) CMS Commander

CMS Commander

CMS Commander enables you to bulk manage your WordPress sites, as well as your Drupal, Joomla and phpBB websites. Manage comments, bulk create new users, install one-click updates of plugins and themes, and compare Google Analytics statistics. Automatically create and schedule backups of all your WordPress websites. CMS Commander also includes content generation tools and auto-posting features. Price: Plans start at $4.95 per month for up to five websites.

CMS Commander Features

  • Plugin management (update, activate and deactivate)
  • Theme management (update, activate and deactivate)
  • Automatically create site backups
  • Clone a site
  • Automatically insert affiliate links
  • Post management (view recent posts, approve/delete drafts, etc.)
  • Comment management (review, approve or put comments in spam)
  • User management
  • WP Settings management
  • Categories management
  • Autoblogging and bulk posting (not available for free accounts)

 

CMS Commander.

CMS Commande, in addition to letting you manage multiple WordPress sites, also lets you manage multiple Drupal, Joomla, and phpBB sites as well.

You can use CMS Commander free for up to five sites. After that, prices go from $9.90/month for 10 sites, all the way up to $64.90/month for 200 sites.

Here’s a video tutorial on how to add WordPress sites to your CMS Commander account:

 

6) Worpit

Worpit

Worpit allows you to manage a network of WordPress sites in one central location. A couple of Wordpit features are instant backup and recovery and bulk updating of WordPress plugins and themes.

You can manage one site for free with Worpit. There are six different paid subscriptions, ranging from five sites for $1.60/month, up to 500 sites for $160/month.

Below is a video of at Worpit in action:

Worpit Features

  • One-click login for each site under a single admin dashboard
  • Update your installations with the latest WordPress versions
  • Automatic daily backups
  • On-demand backup and restore
  • Built-in WordPress installer (install new sites in 60 seconds)
  • Auto-install your preferred plugins and themes to new sites

 

 

Worpit.

Worpit provides key solutions for WordPress and domain management. Manage all your sites in a single dashboard. Jump to each individual WordPress site admin at any time. One-click update plugins and themes. The premium product, WorpDrive, provides backup and recovery for your WordPress sites. Price: Plans start at $1.60 per month for up to five WordPress sites.

 

 7) WP Pipeline

WP Pipeline.

WP Pipeline.

WP Pipeline is another tool that allows enhanced multisite management from one location. Update or manage themes and plugins individually or for multiple sites. Manage groups of sites or users. Backup once or on a schedule from one central location. Price: $25 for up to 5 sites; $67 for up to 100 sites; $147 for unlimited sites.

8) xMark Pro

xMark Pro.

xMark Pro.

xMark Pro is a tool to manage all aspects of your WordPress sites, including mass posting, drip feeds, SpinTax integration, plugins, themes, categories, users, blog rolls, widgets, one-click login and more. Centrally create and manage hundreds of domains on multiple servers. View traffic reports and sales statistics. Centralize your promotional material and campaigns. Price: $49.95 per month.

--

 

Some of the materials in this post  are reproduced from publicly available syndicated RSS feeds.
The original sources for this article were:
http://www.practicalecommerce.com/articles/3872-8-Tools-for-Managing-Multiple-WordPess-Sites
http://sixrevisions.com/wordpress/tools-manage-multiple-wordpress-sites-one-location