Most likely you are exporting and importing some custom blocks or blocks provided by external packages. Above in this documentation, we explain the supported block types
The export and import can be fixed for most of the block types rather easily. Please take a look at our programming tips to learn how to fix these problems by adding a couple of lines of code.
In case some of your blocks are referencing some dashboard managed data, that data will not be automatically covered by this add-on. However, we have written the add-on in a way that utilizes to core's inversion of control container, allowing external developers to modify the export and import processes. Therefore, you are able to add your own data export and import functionality to the synchronization process. There are some comments about this in the code but in case you need more guidance, just contact us through the support forums.
If your local instance has multilingual sections while the remote does not, you must sync the default language section before or together with other sections, otherwise you might not be able to access multilingual global areas or stacks in the dashboard. This is an issue in the concrete5 core that relates to the system not finding the correct default multilingual setting.
Sometimes your local database might contain high resolution images. Unless you have ImageMagick installed on the importing end, the images are being tried to resize using the PHP’s GD image manipulation functions when they are being imported. This may consume a lot of memory with high resolution images on the importing end which might lead into PHP’s memory limit errors on your server in case it does not allow the PHP processes to consume as much memory as needed. You should look into your remote instance’s logs in order to find out whether this has happened to you. If you encounter this issue, install ImageMagick on the importing end for better optimized image manipulations.
The PHP error you should see in the logs at the importing end looks something like this:
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32620001 bytes) in /var/www/concrete/vendor/imagine/imagine/lib/Imagine/Gd/Image.php on line 617
In case you want to enable ImageMagick image manipulation for your instance, make sure you have this external application installed on your machine (you can see this through your instance’s PHP info) and after that, apply the following change to your configuration files:
<?php
// In /application/config/concrete.php:
return array(
'file_manager' => array(
'images' => array(
'manipulation_library' => 'imagick',
),
),
);
After changing the configuration, before you try the synchronization again, try uploading a large resolution image through the importing end’s file manager.
In case your process stops at 'prepare_payload' with the following message, you may be experiencing a zipping issue:
Mainio Sync encountered an exception in 'prepare_payload'. Refer to the remote server logs for more information.
In this case, you should be actually looking into the local instance's logs for the error. In case you see the following type of error in the concrete5 logs (Dashboard > Reports > Logs), your system is most likely not able to create the zip file that is needed for the file transfer:
exception 'Exception' with message 'Unknown ZIP-related problem'
This error happens in some edge situations when the PHP's internal ZipArchive class fails to create a zip file. This may be due to the zip file containing large files which can cause PHP to reach its memory limit or other issues during the zipping process. This problem is most likely caused by the PHP's "exec()" function being disabled in your environment because of which the operating system's own "zip" and "unzip" programs are not available for concrete5. To fix this situation, please make sure that the "exec()" function is enabled for PHP. Look into your "php.ini" configuration file for the "disable_functions" configuration and make sure "exec" is not listed there.
Please continue to read other parts of the documentation: