Lost password?    Lost username?    Create an account
OverviewDownloadsForumSupport
CSV Improved

CSV Improved

How to collect debug information?

  • Print
Category: F.A.Q.
Published on Friday, 24 April 2009 06:10

Why?

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.

 

How to enable debug info?

CSVI 4/5

  1. Click on Process
  2. Select Import or Export
  3. Select your component
  4. Select the operation you want to perform
  5. Click on Go
  6. Under File set the Collect debug information option to Yes. So it looks like this:

    Collect debug information
  7. After the Import or Export, click on Show Panel
  8. Click on Log
  9. Click on the Import /Export you just did
    Click log
  10. See here the Download debug log link:
    Log details
  11. Click on the Download link and post the zip file in the forum for checking.
  12. Now you have a debug log.
Import crashes and no debug log

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.

CSVI 1.9

 

Debug info is enabled on a per template basis. To enable debug info collection take the following steps:

  1. Click on templates
  2. Select the template that is going to be used for import
  3. Click on Edit
  4. The following screen will be seen
  5. Select the last option on the screen Collect debug information
  6. Click on save

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.

Where is the debug output?

The debug output has changed in version 2.1. In version 2.1 you can download the debug log by going to:

  • Log
  • Click on the Action link
  • If Collect debug information has been enabled under Log details there will be a link called Download debug log.
  • Click on the link to download the debug log, this zipfile can then be attached to your forum post.

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:

Version: 1.6
Using template: Product Import
Using delimiter: ^
Using enclosure: ~
Not skipping the first line
Not skipping default value
Overwriting data
Use column headers for configuration
Preview used
Doing a regular import
Field: attribute_values
Field: product_sku
Field: manufacturer_name
Field: product_price
Field: product_name
Field: product_s_desc
Field: product_publish
Field: product_special
Field: category_path
Field: product_desc
Field: product_full_image
Field: product_thumb_image
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>&copy;&nbsp; 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'

What to do with the debug output?

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.