Support

Akeeba Backup for WordPress

#37318 Akeeba Backup Corrupts Elementor

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

WordPress version
6
PHP version
8
Akeeba Backup version
7.6.6

Latest post by nicholas on Monday, 20 June 2022 08:42 CDT

DToolsWhitchurch

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 10MiB, please upload it on your server and post a link to it.

I posted a question in the Elementor Facebook page as follows:

"I have several times now had problem with Elementor getting corrupted when restoring a site using Akeeba back up. The only cure was to delete elemeentor plug in and then reinstall. Then pages are still there but much page content is lost so one has to go all through the site putting back in pics etc. Is there a way to use Akeeba that will not corrupt Elementor.? OR Is there a way to delete/reinstall elementor without loosing content set up?"   Do you have any suggestions to answer this issue.   I am using a fully updated site with PHP 8 previously have been using PHP 7.4 and fully updated versions of Admin Tools Pro and Akeeba Pro.. The attached pic shows what the menu looks like until I reinstall elementor after deleting the plug in so causing much of site set up to be lost.     I got two answers (see attached snip)   The first said: Nicholas Zein Moderator Group expert Just remember that when you restore Elementor from a backup in another website, you need to perform the Replace URL procedure. Here, check this article to know more about site migration: https://elementor.com/help/site-migration/   That is not relavant as there was no change in URL although it might have been previously when I was moving from a test URL.   The second was a biog surprise it said this implying that there is some fundamental issue with Akeeba on Wordpress.  I see you posted something aout the Wordpress Plug ins being delisted in 2015 but no update since.

Anne-Mieke Bovelett Moderator Group expert in Global Accessibility Awareness I have never heard of Akeeba. They’re not to be found in the WordPress plugin directory, which, to me, is a red flag. I recommend you use a more generic one. Here’s a great list: https://wpastra.com/plugins/best-wordpress-backup-plugins/ and this article is kept up to date.  

 

 

nicholas
Akeeba Staff
Manager

The answers you got are idiotic which is par for the course for the sewer that's the WordPress Plugin Directory.

We explicitly asked that Akeeba Backup be removed from the directory for the following reasons:

  1. The only way to publish a plugin to the directory is using the old, slow, and problematic Subversion (SVN) versioning software. The entire world has moved to Git some 14 years ago... except WordPress. Subversion always performs operations directly on the centralised server, it is prone to merge conflicts and messes up files without a warning. Since they are idiotically using the subpar Subversion to magically create releases it was impossible for us to do any kind of pre-release quality control, leading to one every three releases being broken because of Subversion messing up our files. We consider it unacceptable that an enforced use of subpar tooling reflect badly on our software development proficiency.
  2. The directory DEMANDS that all software published in it offer free support through it. We had been very upfront that we do not do free support due to the very technical nature of the product and the need to have access to privileged information which cannot of course be published on a public forum. The directory officials considered it fair that we'd get downrated for their inability to provide a helpdesk suitable for providing the support they were forcing us to provide.
  3. The directory considers obviously fake bad reviews to be "the subjective user's experience" and not be removed (unless, of course, the software is written by Automattic, see Gutenberg and the directory officials unashamedly removing any negative review and banning the user!). The straw that broke the proverbial camel's back was a blatantly fake review which claimed that the person had contacted us and we demanded that he pay 50 British Pounds to give him access to the software to restore his site. First of all, Akeeba Backup already informed the users that restoring a backup is free and easy by using the free of charge Kickstart Core, with a link to its download! Second, at that time (2015) not only we were only charging in Euros as we've been doing since this company existed, but the price for Akeeba Backup Professional for WordPress which would give you access to Kickstart Professional (that the reviewer did not need) was 40 Euros which translated to 28 British Pounds. We reported that to the Directory and we got the asinine reply that it's the user's subjective experience and the review stands. Last I checked, if I go to a grocery store I cannot tell the cashier "my subjective client experience is that you are giving food away for free so I am choosing not to pay", I'll be arrested for theft. Likewise, if I publish an article where I claim that a free offer costs money I will be sued for libel. Not in the idiotic Directory; it's a land of no laws. That's why I asked for our software to be unlisted.

So now the same people who demand developers to provide free work using subpar tools and endure blatantly fake reviews which accuse them of things they have never done have the gall to talk about red flags?! Maybe they should take a hard, cold look at their crappy software, Soviet-style Directory and dysfunctional community first.

Now, let's get to the technical support part of your issue.

We have plenty of users using Elementor and I have used it myself in some of the sites I used for testing without observing any problems. I will work with your backup and let you know what I find. I am scrubbing the URL to the backup since this is a public ticket.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

nicholas
Akeeba Staff
Manager

Now I can tell you that the problem is not with Akeeba Backup, it is with Elementor, as I suspected. Namely, the way it handles images in its "effects layer".

First of all, Elementor requires a per-domain license to use. When you are restoring to a different site the license is invalid. That could be the reason why you think that Elementor itself is broken upon restoration. I did not see anything like that BUT I also only know what the free of charge Elementor looks like as I've never bought their paid version.

Anyway, this is not the real problem here. The real problem is that for each article Elementor creates CSS files with hardcoded full URLs under the folder wp-content/uploads/elementor/css. Full URLs seem to only be used if you put an image in its effects layer. Inline article images have their URLs stored in the database where they are of course replaced by Akeeba Backup — something that many backup plugins fail to do correctly.

No backup software replaces hardcoded URLs in arbitrary files. Not Akeeba Backup, not Updraft Plus, not XCloner, not any other backup or data replacement plugin which currently exists for WordPress. The people who told you that it's Akeeba Backup's problem and other backup products would work have absolutely no idea whatsoever what they are talking about. They just need to be hit with a libel lawsuit to maybe learn to think twice before making false assertions about a paid product in a public forum.

As I said, the URLs in database data ARE replaced by Akeeba Backup... but they are not used by Elementor for images in the effects layer. I actually had to replace the hardcoded URLs in the files under wp-content/uploads/elementor/css. When I did that then in fact Elementor DOES indeed see the correct background image in its editor area on my locally restored site — a site otherwise restored using the default options. You can see that in my attached image. No need to re upload any images, they all work fine.

The only solution I can imagine is adding explicit support for Elementor's CSS files, replacing any hardcoded URLs in there. This is something which we will add in an upcoming version of Akeeba Backup. Why not? It's a popular enough plugin to warrant a special exception. An exception that other backup plugins won't even consider.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

DToolsWhitchurch

Thanks, i acceept all that which is very usefull and arms me with info needed to do some tests on my server so as to be ready and confident to use Akeeba when needed.

Also a most usefull insight into the significant cultural differences between Wordpress and Joomla, was forced to use Wordpress for this site ( with the charity paying someone else to design site)  having used your products on Joomla for years.

 

 

nicholas
Akeeba Staff
Manager

The WordPress community is… weird. You know how you go to a Joomla event and people you have never met welcome you like an old friend? It’s the exact opposite with WordPress. I’ve sponsored events and I was still treated like I didn’t belong there. Um, okay, I guess that’s one way to make friends… not? :D

Anyway, check the CSS files I told you. I see that before the site you backed up from you were using another site and its URL is still in those CSS files. In case you were wondering why you’re missing an image :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!