BobIMG

Our host offers PHP v5.6 and v7.2. We’d like to update to 7.2, but we get the error that mcrypt is not installed whenever this plugin is in use. What is the suggested way to utilize Members and v7.2?

Thank you team for rethinking things. We now seem 100%.

We customize Strong Testimonials for nearly all of our client site builds. This CSS change from our client’s perspective has broken 80+ websites. Unreal decision team.

This plugin was great … now all of the changes have left us with 90 websites that all need updates. What a poor move team!

Thank you for the insights and assistance.

Hi Dave,

I just did an experiment. I opened up a RAM usage graph supplied by SiteGround before logging into WF Central. I focused on our one server that has the most sites (83). These sites get very little traffic. As an illustration, this is how that graph peaked when I logged in: https://take.ms/XhrJt

For reference, this is what that server’s load has looked like for the past few days: https://take.ms/jGxkf . In other words, this peak is pretty significant and was caused when logging into WF Central. In the first illustration, note how after the peak the server returns to nearly normal levels. I stayed logged into WF Central during most of the duration after the peak on the above graph. While in WF Central I sorted by the “critical” option and then did some minor updates across 10 websites. I also removed a couple of websites that were not connecting and added another site. In other words, it seems to me that things work well with all but the initial login which is adding a significant resource usage.

As an analogy, I’m thinking about the Windows operating system. A few generations ago, Windows wanted to ensure they could advertise a fast boot time. One way that they achieved this marketing goal was to delay startup apps over the first few minutes while the machine was booting up. This kept the initial load lower and greatly decreased the start up times.

Can the same kind of principal be applied to WF Central? Maybe batch these initial calls over a longer period of time?

@wfasa this is super helpful information. I greatly appreciate it. We’ll review other plugins to see if we have a bug.

• This reply was modified 6 years ago by BobIMG.

Of note, we’re also seeing this error.

Also curious about this new error. Per the help article it sounds like the options page has an option for correcting this “issue”. But, I’m somehow missing that option. If I understand this correctly, I would think that the Live Tracking page would not have accurate IP Addresses on it, but it appears that these are all accurate based on a quick glance.

Daniel, did you ever find a fix for this. It has been driving me nuts for several months through several WP and Chrome (64 bit) updates. I have tried another computer with a similar setup and it didn’t have an issue. I even uninstalled and reinstalled Chrome. Same issue. Switching to Firefox to reorder images is not desirable ??

@adrianfx
Terrific suggestion! Thank you. Will try!

I have found that the only way to avoid this issue is to login via an incognito window …. update a few thumbnail images … close the browser (drops the cookies) and then repeat.

I have 90 galleries with ~30+ photos each. Is their a way via phpMyAdmin or via another setting that I’m not seeing which allows me to regenerate all thumbnails across all galleries in bulk so that I don’t have to go through this laborious process?

Tim,
I would like to be able to clear the Falcon cache for multiple sites via InfiniteWP. IWP has a “Code Snippets” feature where I can push PHP to multiple sites. I was inspired by your code:

<?php
include ‘wp-load.php’;
wfCache::clearPageCache();
?>

When I execute it, I get this error: “Parse error: syntax error, unexpected ‘<‘ in /home/intersec/public_html/wp-content/plugins/iwp-client/init.php(1523) : eval()’d code on line 1”

As I am not a PHP Guy, this could be a simple issue. Before reaching out to IWP for advice, I thought I’d check with you on whether this function you suggested a few months ago is still viable.

Thank you WFMattR. We’ll get to work….

@finestimaginary
Our robots.txt also disallows /wp-admin/