I am running Beaver Builder (Standard Version) 1.6.4.6 and I’m trying to update to version 1.6.4.7 via the WordPress admin but when I try to I get the message ‘Update Failed: Plugin update failed’. I have entered my licence key under the page builder settings so this is not the issue. This is happening on several of my installations where I have had no problem updating other plugins, premium or from WordPress.org.
Hi David,
Not sure if you have got the version numbers mixed up, but 1.6.4.6 is the latest version, there is no 1.6.4.7 ?
If you are possibly referring to 1.7 - that is in beta and is only for testing and providing feedback and does not have auto update until released
HTH, Dave
Hi Dave,
The WordPress admin plugins page is telling me that 1.6.4.7 is available as of January 10th and shows the changes that were made in this version. Could this be related to the issue described here: http://forum.wpbeaverbuilder.com/support/q/download-for-1-6-4-7-not-available/?
Thanks,
Michael.
Hey Michael,
Yes, there is a new version available as of last night. We are aware the downloads page reflects the incorrect version at the moment and will get that updated asap!
Best,
Billy
Unfortuantely I’m still getting the error ‘Update Failed: Plugin update failed’ when I try to update to 1.6.4.7 via the WordPress admin. I have just updated Advanced Custom Fields Pro via the WordPress admin without an issue so I think my configuration is okay. Is there a way of seeing more information on the cause of the failure? I have WP_DEBUG enabled but this isn’t showing anything in the admin.
Hi David,
Any possibility the issue is one of resources?
The BB plugin is a fairly large plugin, and it maybe a memory problem or other resource problem is the sticking point!
Are you able to update the plugin manually using FTP ?
HTH, Dave
The error I’m getting is as follows:
An error occurred while updating Beaver Builder Plugin (Standard Version): Could not create directory. bb-plugin/includes/vendor/campaign-monitor/class
I have had no problems installing and updating other plugins on this site so I don’t think it is a file permissions issue.
I have checked the directory permissions and can confirm that PHP is able to write to the wp-content/plugins directory.
I can update it via FTP but I’d rather not have to because I manage all other plugin upgrades across a range of sites using iThemes Sync and would like to be able to update Beaver Builder this way too.
Hey David,
Sorry about the delay here. Would you mind shooting us the site url as well as temp admin access via private reply?
Best,
Billy
[Content Hidden]
Hey David,
Is this the first time you’re updating the BB plugin on your sites? Or did it update before and just stopped now? I tried adding a Pro version of the plugin seeing if it makes any difference but it gave out an error after the install.
Can you try adding this line define('FS_METHOD', 'ftpsockets'); to your wp-config.php file and see if it works? You can check the codex below for more info about it. 
https://codex.wordpress.org/Editing_wp-config.php#WordPress_Upgrade_Constants
If it still doesn’t work, we may need FTP access so we can have our lead dev check in on this.
Ben
[Content Hidden]
[Content Hidden]
Hey David,
Yes, the contents should still be there even if the plugin was removed. Sorry I removed your version of the plugin. I tried placing another version seeing if it made any difference. Anyhow, we’ve released the 1.7 version of the plugin so you can install 1.6.4.7 and try updating it.
Ben
Hi Ben,
Where can I get version 1.6.4.7 from? Under my BB account I can only see a link to download version 1.7.
Thanks,
Michael.
Hey Michael,
Ah! I thought you had downloaded one beforehand. Let me just see if we have an old copy of the standard version.
Ben
Hey Michael,
Do you already have the fs_method stuff in place? So I can install the plugin, once I get it, and try updating it?
Ben
Hi Ben,
I have added that code to wp-config.php so you can go ahead and try the update. Thanks.
Hey David,
Sorry, should have thought of this before. Do you mind sending FTP access to the site instead so we can do some more testing?
Ben