Now WordPress site can store all its content (pages and media) in cloud. This makes site powered by enormous scale and reliability of cloud storage.
WP2Cloud plugin for WordPress:
Not at all. Since cloud storage space is nearly limitless, you can use as much of it as you need. WP2Cloud can upload very large files as it uses multi-part upload and thus it is not restricted by the available memory on the Web server.
Media files are uploaded to cloud storage as fast as physically possible with the help of WebStor - high performance library for Amazon S3 and Google Cloud Storage.
Absolutely, your media experience is not affected by this plugin. You can change image, add title, alternative text, media tags - whatever you might need.
The actual deletion is intentionally delayed to account for caching latencies. For example, even though you deleted the image and removed the link from the page, the old page content might be still cached. The delay helps the old page to render correctly and show the old images.
If you still see a media file in the cloud after a couple hours have passed since deletion, please email us at email@example.com.
Yes, both domain-based and path-based multisite setup is supported.
Yes, WP2Cloud is compatible with W3 Total Cache. In fact, the latest WordPress-on-S3 AMI has W3 Total Cache plugin installed and configured.
Yes, just make sure you use ClouSE 1.0b.1.4 (or later) and WP2Cloud 1.2.0 (or later).
You can edit files in the File Manager module of the Webmin system administration console. Log into Webmin, select Others -> File Manager module on the left. The WordPress files are located in /var/www/wordpress. For information on how to connect to Webmin see this post.
Alternatively, you can use the Upload and Download module to transfer files between the instance and your computer. Log into Webmin, select Others -> Upload and Download.
For quick access to wp-config.php and .htaccess, log into Webmin, select Others -> Custom Commands.
Note: Webmin and phpMyAdmin are available in WordPress-on-S3 AMIs released on 01/31/2013 or later
Please refer to WordPress on S3: DNS and HTTPS configuration blog.
Yes, ClouSE for Windows is currently available to a group of limited preview customers. If you would like to sign up for the limited preview program please contact us.
Yes. Standard MySQL tools work well with ClouSE. For example, you can use mysqldump to export the whole WordPress database into a file. In fact, WP2Cloud makes data export easier and more robust, because the database dump now includes the media, so the dump fully represents all website's data.
Yes, you can configure WP2Cloud to use a separate Media Server. The configuraiton instructions are provided here. See also this post for information about how to install and configure MySQL as a Media Server on a shared hosting server.
The comprehensive documentation can be found here.
If you aren't able to find a resolution, please email us at firstname.lastname@example.org. The authors are available for professional consulting to meet your configuration, troubleshooting and customization needs.
Some Linux distributions have custom-built MySQL binaries that are different from the official MySQL builds available from http://www.mysql.com. ClouSE may fail to install with custom-built MySQL binaries, printing an error like "ERROR 1126 (HY000): Can't open shared library '/usr/lib64/mysql/plugin/ha_clouse-5.5.20.so' (errno: 13 undefined symbol: my_pthread_fastmutex_init)". In this case you need to install the official MySQL binaries from http://www.mysql.com. See this and this forum posts for more details.
The wp-smush.it plugin 188.8.131.52 requires a patch to work with WP2Cloud. Make sure that the Enforce image URL is same as Home option (Settings --> Media) is unchecked.
The wp-post-thumbnail plugin doesn't work with WP2Cloud. wp-post-thumbnail uses direct filesystem calls making it impossible for WP2Cloud to provide media file storage.
The existing media files are not automatically moved to the cloud when the plugin is activated. They need to be re-uploaded manually. Media migration functionality may be implemented in the future.
Requires: 3.3.2 or higher
Compatible up to: 3.9.1
Last Updated: 2014-7-2
0 of 4 support threads in the last two months have been resolved.
Got something to say? Need help?