Search results

And "Expected behavior" can mean that Smart Updates is NOT updating the premium plugins like Elementor Pro. I don't understand why this is such a taboo subject?

The big question that continues to be unanswered is "Will Smart Updates update a premium plugin like Elementor Pro?"

Still no answer from Plesk on this?? I forgot about this thread and am having the SAME problem.

Believe me I've tried with a very similar scenario to the previous post. All they will say is 'that's the expected behavior' with nothing to back it up like logs. That's why I posted this in the forum to see if anyone else had a better answer.

Here's a perfect example that just happened. I get an email from WordPress stating: 2023-11-01 11:57AM These plugins are now up to date: - Elementor (from version 3.17.1 to 3.17.2) : Elementor Website Builder – More than Just a Page Builder - Elementor Pro (from version 3.16.2 to 3.17.0) ...

Yes I did, they responded with 'If you have Smart Update turned on then that is the expected behavior'. And they said the log only shows what it found to be undateable not what it updated. None of which really answers my questions with certainty. I want to be absolutely sure that Smart Update...

Because the Plesk documentation says it won't update premium plugins like Elementor Pro. Unless that has changed? And then I get an email from WordPress saying that Elementor Pro has been updated. So I'm not sure what to believe. Also why is there no log as to what Smart Update had updated...

Another piece of information that makes be believe that it's WordPress doing the updating and NOT Smart Updates is that it's been said that Smart Update will NOT update a premium plugin like Elementor Pro due to the licensing? However I routinely receive emails like this: These plugins are...

Nobody knows?

I want to make sure this is normal behavior for Smart Updates: I receive many emails from WordPress that "some plugins and themes have automatically updated to their latest versions..." and then the list of what was updated. In WPTK I have it turned on and set to auto-update. Is that email...

Yes all of the above. Can't clone despite switch PHP to every version. Can't use Smart Update - give same error Can't login through WP Tool Kit - JSON error Emails stating "Failed to reset cache..." This can't all be related to Elementor Pro??

Having the same problem. Messages set to forward to email account on same server get discarded when p=quarantine. Method 1 in the document worked. Bad problem because you don't know if your email is being discarded or not. This one started with a dk_check which failed: DKIM verification...

I'm using WHMCS with additional separate Plesk servers for a web hosting company. Is it possible to maintain a specific service plan (service plan ID) across multiple servers?

That's for the help! I do have Plesk store backups locally and on remote storage but that's what I've always done. I also have backups set to run individually for each client, in addition to the full server backup but that's what I've always done. I do have the option set to store locally if...

I'm attaching a screen shot of the disk usage. Nothing had changed with this server, no new accounts, etc. but around Apr 26 the disk usage started to spike. I believe it's from the backups? If I look in the /var/lib/psa/dumps directory there are 53387 files. does that sound normal? I almost...

Happy to report that update worked! It auto-installed yesterday morning and today had no problems with DropBox backups.

Now I'm seeing this error message every day. :( Reason: 2023-04-30 06:25:18 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2023-04-30 06:25:20 ERROR: E:The repository 'https://download.imunify360.com/ubuntu/20.04/slot-6 focal Release' does not have a Release file...

Yes, hopefully very fast as my clients get a bit unnerved when they continue to see the email with the error.

I received this from tech support: This issue was confirmed by our developers, and it's identified with the ID EXTPLESK-4582. At this moment, there's still no ETA to fix this.

Just to add to this but I'm experiencing the same problem. It seemed to start when I upgraded to 18.0.52 just a few days ago. My license is from a reseller so I will have to try the 30-day support trial.