mainwp

Once you change the name via FTP you can change it back and it will remain disabled at which point you can upgrade the plugin to work again work with PHP lower then 5.3

Thanks we are also looking into the Dashboard queries pointed out by ctalkington in this GitHub post https://github.com/mainwp/mainwp/issues/14

This should be addressed in the latest version for you.

Version 2.16 of the MainWP Child plugin has addressed the issue.

Joe, can you check what version of PHP you are running on that child site? Is it lower then PHP 5.3?

If it is The problem was caused by a block of code was introduced that requires PHP 5.3 or higher. Unfortunately, we didn’t have a check to verify the PHP version before running that block and that caused the crash.

When version 2.16 of the Child Plugin is released in a few hours it will contain the checks.

After discussing the issue with the Dev team it was decided to set Autoload off since about a year ago it was causing issues with some users on smaller hosting packages.

It’s always hard to decide what the best approach should be in cases like this. We decided to go with no autoload after the performance issues we had previously (loading all options all the time).

We will enable the autoload property on the options that are always used in our next version to speed up the page load as much as possible without affecting the smaller hosts.

I’ll send it over to the Dev team to review.

We have an update due within 48 hours so if/when they confirm the issue we’ll try and get it in that update.

This was determined to be caused by disabled SNI support for the cURL in the host environment.

We added a work around for hosts with this issue in Dashboard version 2.0.14

It looks like your Dashboard may be having an issue passing through the Sucuri Firewall, if you can open a ticket on the MainWP Support portal we’ll be happy to look into it for you.

We have released Dashboard and Child version 2.012 which should resolve the issue for you.

We have found the issue and are currently testing it with a couple of users also using BackupBuddy.

If you would like to also test the update, please open a ticket in the MainWP Support Portal, if not the update should be available within a few days.

Since the Sucuri Extension is non-www.remarpro.com Extension please open a support ticket in the MainWP Support Portal

That’s a great follow up question, your MainWP Dashboard is consistently doing checks for updates and scheduled backups.

The easiest way to see this in action is to append the following URL to your Dashboard’s domain /wp-admin/admin.php?page=ActionLogs in the Status drop down select “info” press save and then wait about an hour. This will allow you to see what your Dashboard is doing in the background.

If that seems like to much for your server you can turn it off by going to MainWP Settings Global Options page and setting “Use Wp-Cron” to No. You can then set your own crons to run when you like by following the directions in this help doc Disable WP-Cron

If you have any additional question feel free to ask in the MainWP Support Portal

The basic answer is it really depends on your server and what you are doing.

Your MainWP Dashboard performs a lot of operations and each one of them uses a different amount of resources depending on what they are doing.

For example, if you are updating 40 plugins at once across your network it will use more resources then just updating 4 or if you have a scheduled backup for 10 sites it will use more resources then one scheduled 2 sites.

If you are concerned about resource usage there are a couple of features built in that could help:

1. Turn on “Optimize for Big Networks” which enables a caching function. I recommend this option if your Dashboard is on a shared host or you have a large network. If enabled (Set to YES) updates will be cached for quick loading. A manual refresh from the Dashboard is required to view new plugins, themes, posts, pages, comments and users from your Child sites.

2. Check your settings in the Advanced Options section. The Cross IP and Same IP settings allow you to set the Maximum simultaneous requests and Minimum delay between requests (milliseconds) when you are syncing or updating. The Dashboard comes with a basic setting that works for most hosts but if you are running your Dashboard on a shared host you may want to slow things down or on the other hand if you are on a VPS you may want to speed things up.

Details on both these settings can be found in the MainWP Settings Overview help doc

If you have any additional questions on how these settings work please open a ticket in the MainWP Support Portal

I’m going to mark this as resolved since we can not duplicate the issue, if you are still having this issue can you please open a ticket on our Support Desk so we can take a look.