Debug information is very valuable information. The information gives an in-depth look into what is happening inside the program. Troubleshooting problems is made a lot easier as the programmer can see step by step what the program is doing.
It can happen that the import crashes and no log details are stored, the debug log is still created but need to be retrieved from the server. The debug logs are stored in the folder tmp/com_csvi/debug. Find the last created file in this folder and that will be your debug log for your last import.
Debug info is enabled on a per template basis. To enable debug info collection take the following steps:
Debug information collects a lot of info, it is advised not to use it with large imports, rather use a small sample of a few records.
The debug output has changed in version 2.1. In version 2.1 you can download the debug log by going to:
Any older version of CSVI VirtueMart can use the following procedure:
The debug output will be shown at the bottom of the page after the import is complete. The output looks like:
Using template: Product Import
Using delimiter: ^
Using enclosure: ~
Not skipping the first line
Not skipping default value
Use column headers for configuration
Doing a regular import
Using the first line to setup the required fields
Going into normal upload
Check if the product exists: Show/hide query
SELECT product_id FROM #__vm_product WHERE product_sku='prod003'
Updating the product with new data: Show/hide query
UPDATE #__vm_product SET product_desc = '<hr2>HR-028-R2</h2><h5>© 2008,
Mankaho</h5>DESCRIPTION', product_full_image = 'poali003_Promo1.jpg', product_name =
'HR-028-R2', product_publish = 'N', product_s_desc = 'HR-028-R2', product_sku =
'prod003', product_special = 'N', product_thumb_image = 'prod_Thumb.jpg', mdate=
UNIX_TIMESTAMP(NOW()) WHERE product_sku='prod003'
Once the debug output is generated it is ready for analysis and can be posted on the forum along with the description of the problem.