John

— SOLVED —

The issue was with cache + CDN from the old site.

Thanks for your reply.
I now realize that I mistyped the PHP version, sorry about that.
The current PHP version of this site is 7.4 and now I also updated WP to 6.7.2.
This error appeared only recentlyand your plugin was running without problem since long time already.

Anyhow, I updated this morning and I still have nothing showing up.
Will keep you updated if this error appears again, thanks.

Many thanks for your kind feedback.
I confirm, I did that and switched to 8.3 and those notices stopped and everything woks fine.
I also learned that WP 6.7.1 latest version is not yet fully compatible with version 8.4.

Great, many thanks!

Please note that the current WP version 6.7.1 is not yet fully compatible with PHP 8.4 and this is, I think, scheduled for the next version. So maybe this issue is related.
Also, I tested with PHP 8.3 and those deprecation errors do NOT exist anymore.

“the backup process has been?streamlined to reduce complexity?and make it easier to manage”

No need to invent fairy tales, just tell the truth…
The boat is sinking and everyone is leaving because you wanted to reduce complexity? In fact you just reduced your users count.

“We understand that this change impacts some workflows, and we’re actively gathering feedback to refine the experience.?“

You really have a strange sense of humour.
Problem is the biggest impact will be on the future of your plugin. RIP

You really found the best way to kill an excellent plugin, congrats.

… and why I’m not able to edit my existing jobs?

All this sounds like a joke. Unfortunately you seem to be serious.

Just to be sure I understand correctly before I move elsewhere:

Do you clearly mean that I can NOT edit existing jobs anymore and that I cannot create any new jobs other than the templates you provide AND you cannot have a backup that includes both files and DB and that I need to follow the nonsense of your default templates and run 2 different jobs for the same result I was getting previously with a single job?

Many thanks for your replies.
I’m on shared hosting.
I also understand that current WP version is not fully compatible with 8.4 so I’ll wait a bit or simply re-test with version 8.3.

Many thanks, well noted.

@saranshwpm

What do you mean by “new default backup jobs (Files & Database Backup) were added automatically“???

Will those jobs be running without the site’s admin consent or are they just inactive jobs?

And where are they, cannot find them. And why cannot select a backup location for new jobs?
Guys, are you serious?

Yes, I see. That’s why we get this 10%.

Many thanks for your feedback.

This is a shame because we are asked from all developers to update to PHP 8.xx and when we test nothing works… I have a bunch of sites still running fine on PHP 7.4 and I see less and less reasons to do so as about 1/3 of installed plugins generate huge amounts of deprecation errors that heavily flood the error logs and makes them unreadable when something goes wrong.

I contacted other plugin developers and most say, yes no problem if the site still works fine as those are just deprecations… I now understand why so many people still stick with PHP 7.4!

Thanks anyway.

Thanks but deprecations fill the site’s error.log for sure and that’s where I found them. Problem is they flood this file and it becomes bigger every single day. So, now Yoast pretends that this log may contain reports of things happening that are not errors, right?

So, instead of correcting the etymology I would rather expect you tell us when and if you are planning to correct this. Thanks.