Creating template overrides to support MageBridge - Yireo

Something does not work

In all cases, first upgrade Vm2Mage to the latest available version. The procedure of how to upgrade Vm2Mage in both Joomla! as Magento is available in our tutorial section.

When you need help, make sure you understand our support policy as described in these FAQ. Also, before posting to the Yireo Forum, make sure you have checked your Apache logs for any PHP Errors or PHP Warnings.

Failed to initialize XML-RPC

This error is given if the XML-RPC client within Joomla! is unable to contact the XML-RPC server of Magento. In most cases, you did not configure anything yet regarding the API. Make sure you configure the "Parameters" within Vm2Mage by filling in an API-host, API-user and API-key.

If the settings are right, you should be able to see dropdown-options under the "API Widgets" within the modal popup of "Parameters". If the settings are incorrect, these options will be regular input-fields, not selection-boxes.

Invalid API path

If the API-settings in the Vm2Mage "Parameters" are properly configured, you may still receive the error "Invalid API path". In this case, the connection to Magento is up and running, but within Magento the Vm2Mage API-path is unknown.

Make sure you have properly installed the Vm2Mage extension within Magento. Also, go to "System > Cache Management" and refresh the "Configuration" cache and the "Webservices Configuration" cache.

Invalid UTF-8 sequence in argument

If you receive a PHP Warning in your Apache ErrorLog mentioning something like "Invalid UTF-8 sequence" your VirtueMart installation is probably not encoded with the right characterset. Make sure all characters of product-titles, category-descriptions and so on, are displayed in the right way within VirtueMart, before migrating things with Vm2Mage. In most cases this can be solved by exporting and re-importing the MySQL database with the right encoding-settings.

This issue is not related to Vm2Mage, but to a corrupt VirtueMart installation.

Unknown API-response: 'No data received from server.'

When migrating products, users or categories, this message may appear. In this case, the migration might be succesfull, but some kind of PHP Notice or PHP Warning occurred. Check your Apache logs for more information on this matter.

Unknown API-response: 'Invalid return payload'

Most likely, some PHP Warning or PHP Error was thrown during migraton, which causes the API-output to be corrupt. Carefully check your Apache logs. If your Apache logs are totally empty, make sure you are actually using these logs. Also, checkout the other FAQ in this section, because they contain helpfull information for requesting support.

Unknown API-response: 'XML-RPC non-object value: 0'

Most likely, some PHP Warning or PHP Error was thrown during migraton, which causes the API-output to be corrupt. Carefully check your Apache logs. If your Apache logs are totally empty, make sure you are actually using these logs. Also, checkout the other FAQ in this section, because they contain helpfull information for requesting support.

Unknown API-response: 'Internal Server Error'

This error is generated by Apache, and tells you to inspect the Apache errorlog. Make sure that PHP error-logging is enabled and that Apache errorlogs are capable of receiving PHP Fatal Errors. If in doubt, contact the system administrator of your webserver. 

Other Unknown API-response codes

When Vm2Mage returns an error Unknown API-response, this means that the feedback received from Magento is not correct. Make sure to enable Magento debugging in the Developer-section, and make sure you also watch any errors in the Apache errorlog.

There are some status-codes generated by Vm2Mage as well: With code 731, the attribute-initialization failed in general, with code 732 the attribute-initialized failed for a specific attribute. With code 733, the migration of either a product, customer or category failed in general, with code 734, a specific migration failed.

How to debug a migration?

Within the product/category/user overview of the Vm2Mage component in Joomla!, you will find a small link on the right called "Debug". This information should only be posted to the forum if you have made sure all other FAQ and tutorials on the Yireo site do not help.

When you hit that "Debug" link, very technical information comes to your screen. Copy these messages to a textfile, ZIP this textfile and post the resulting ZIP-archive as attachment to your forumpost. Do NOT copy the messages as straight text into the forum.

Can you help me?

If you have purchased the Vm2Mage Professional version, you will get full support for any issue that may arise: Either through mail, or through our online forum.

If you are just using the Vm2Mage Standard version, our support is not automatically included. If you believe the problem you are having is related to a bug in Vm2Mage, please supply all the information you can, so that we can actually test things ourselves: Joomla! / Magento versions, VirtueMart versions, database dumps, PHP messages from the Apache ErrorLog, debugging information from within Vm2Mage. If you are unable to supply relevant information yourself, we advise you to either ask your developer, or upgrade to Vm2Mage Professional to receive full support.