JoomlaCloner- Generating a Backup | |
There are 5 entries in the FAQ.
Pages: 1
Questions:
How do i handle backups over 2GB in size?
I am getting a blank screen when generating a backup, what should i do?
How do i allow my users to install clones i made for them?
How to i dump large tables using mysqldump?
How to i export my database with special characters?| Questions and Answers | |
| How do i handle backups over 2GB in size? | |
![]() | JoomlaCloner can create backups of any size, however PHP is limited by default to a 2GB file system! To fix this problem, you need to recompile PHP with this flag "-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" so the full configure comamnd looks like this "CFLAGS="-D_FILE_OFFSET_BITS=64" ./configure etc... " The full instruction list about this problem can be found here http://www.php.net/manual/en/ref.filesystem.php |
| I am getting a blank screen when generating a backup, what should i do? | |
![]() | This problem is caused either by your max_execution_time limit or memory_limit variables from your php.ini file! If your hosting provider allows it try to increase them!
Try to add in your Joomla .htaccess file these lines:
php_value memory_limit 32M php_value max_execution_time 3600 Please note that some providers don't allow these changes to be made through .htaccess, but they allow you to put a file called php.ini in the directory where you want to make the restore! So if the htaccess method doesn't work to change those values, try to create a file called php.ini, upload it in the same directory with the Joomla.Cloner.php and add in it these lines: memory_limit = 32M max_execution_time = 3600 So basically, you need to: Increare memory_limit to 32M or greater Increase the max_execution_time to 3600 seconds Also as we did some investigations into Joomla core, there seem to be some issues on some servers with Apache TimeOut variable and ob_start() php function! For this we would suggest you read the solution discussed here: http://forum.joomla.org/index.php/topic,99754.0.html and http://www.joomlaplug.com/Forum/func,view/id,1028/catid,12/limit,6/limitstart,18/ The solution mainly consists in adding this code in administrator/index.php file just before ob_start() line: echo " "; |
| How do i allow my users to install clones i made for them? | |
![]() | You need to go in your 'View Backups' screen and click the Frontend column image, this will publish your clone and users can access in your http://sitename/index.php?option=com_cloner location!
All they have to do is to provide their ftp details of where they want to move and restore that clone! |
| How to i dump large tables using mysqldump? | |
![]() | Dumping large tables can be a problem if you have time limitations on your host!
To fix this, you would need to support the mysqldump server utility and to replace in JoomlaCloner Configuration area your mysqldump configuration line with this
"mysqldump --quote-names --quick --single-transaction --skip-comments " |
| How to i export my database with special characters? | |
![]() | Often, international sites have special characters that need a special charset, by default all mysqldump exports are UTF-8 compatible, but if your site has characters different from that charset(example are hebrew sites), you need to add this in your mysqldump line in Configuration:
--default-character-set=your_charset_name_here example, for hebrew, it will look like this mysqldump --default-character-set=your_charset_name_here Note: if you have problems with mysqldump charset encoding, it's always better to uncheck the 'Active' checkbox near it in Configuration, so the database backup will get created by using the php functions! List of avalaible charsets: big5 1 czech 2 dec8 3 dos 4 german1 5 hp8 6 koi8_ru 7 latin1 8 latin2 9 swe7 10 usa7 11 ujis 12 sjis 13 cp1251 14 danish 15 hebrew 16 # The win1251 character set is deprecated. Please use cp1251 instead. win1251 17 tis620 18 euc_kr 19 estonia 20 hungarian 21 koi8_ukr 22 win1251ukr 23 gb2312 24 greek 25 win1250 26 croat 27 gbk 28 cp1257 29 latin5 30 latin1_de 31 |
Extensions FAQ 

