concrete5 Environment Information
# concrete5 Version
5.7.2
# concrete5 Packages
Block Designer (1.0.1.1).
# concrete5 Overrides
blocks/beverage_bot_zero_point_one, blocks/product_entry_zero_point_one, blocks/product_entry_zero_point_two, languages/de_DE, languages/it_IT, languages/nl_NL, languages/ja_JP, languages/tr_TR, languages/sv_SE, languages/da_DK, languages/fi_FI, languages/sl_SI, languages/ru_RU, languages/fr_FR, languages/el_GR, themes/theme_burke
# concrete5 Cache Settings
Block Cache - On
Overrides Cache - On
Full Page Caching - On - In all cases.
Full Page Cache Lifetime - Every 6 hours (default setting).
# Server Software
Apache
# Server API
cgi-fcgi
# PHP Version
5.4.36
# PHP Extensions
bcmath, bz2, calendar, cgi-fcgi, Core, ctype, curl, date, dom, ereg, exif, filter, ftp, gd, gettext, hash, htscanner, iconv, imap, intl, ionCube Loader, json, libxml, mbstring, mcrypt, mhash, mysql, mysqli, mysqlnd, openssl, pcre, PDO, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, Reflection, session, SimpleXML, soap, sockets, SPL, SQLite, sqlite3, standard, tidy, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend Guard Loader, zip, zlib.
# PHP Settings
max_execution_time - 30
log_errors_max_len - 1024
max_file_uploads - 20
max_input_nesting_level - 64
max_input_time - 60
max_input_vars - 1000
memory_limit - 512M
post_max_size - 128M
sql.safe_mode - Off
upload_max_filesize - 128M
mysql.max_links - Unlimited
mysql.max_persistent - Unlimited
mysqli.max_links - Unlimited
mysqli.max_persistent - Unlimited
pcre.backtrack_limit - 1000000
pcre.recursion_limit - 100000
pgsql.max_links - Unlimited
pgsql.max_persistent - Unlimited
session.cache_limiter - <i>no value</i>
session.gc_maxlifetime - 1440
soap.wsdl_cache_limit - 5
Hide Post Content
This will replace the post content with the message: "Content has been removed by an Administrator"
Hide Content
However, before porting I need to know what the core backup package will do. At the moment, core backup is just a placeholder in the 5.7 dashboard, so no-one has any idea of what the core backup will provide.
In the past the core team have subsumed functionality similar to popular addons into the core and I wouldn't want to put a whole lot of effort into porting Backup Voodoo only to discover the next 5.7 release already did some of that or completely cut my market from under me.
I will also need to be using 5.7 for my own customer projects. At the moment 5.7 is just too buggy and I will be starting new customer projects on 5.6 for a while yet. Once I actually have a need for Backup Voodoo on a 5.7 project of my own, then I will have a bigger reason to port it.
So, to summarise the preconditions before porting Backup Voodoo to 5.7:
- Developer documentation for 5.7 is much closer to completion.
- The functionality of what backup will be provided by the core becomes clear.
- 5.7 gains a worthwhile user base beyond relatively static brochure sites.
- 5.7 stabilises to the point that it is good enough to use for my own customer projects.