Testing and Troubleshooting
Troubleshooting by product is the fastest way to correct output:
- Test output of a product
- Correct configuration and start over.
To track down issues through your full feed:
- Generate the feed
- Check feed logs and feed output by accessing the feed file URL.
- Submit the feed file to marketplace and check feedback.
- Correct configuration and start over.
Testing output of a product
In the feeds management screen look for the Test feed button on a feed row. A similar button is found in the feed configuration screen. (see Fig 3.9)
Fig 3.9 Test feed button
Using the Test Feed button, a dialogue will open, asking you to input the product's SKU or ID. Fill in the SKU and hit the Test Feed Now (see Fig 4.0)
Fig 4.0 Test feed dialog
The feed output will be displayed in a table where each row will represent a feed column and the value for the tested product.
If the value of the product for a column is not what you were expecting, check the following:
- You are using a correct attribute / directive in Columns Map.
- You are not using Product Filters the wrong way.
- The Product has the correct data saved.
At the bottom of the product output there's also a snippet of the logs generated for this product, there will be logged any skipped products in case of complex products like configurable, bundle, etc. (see Fig 4.1)
Fig 4.1 Feed output
Check Logs
Logs are created by default, make sure the [magento_root]/var/log directory is writable.
Checking logs is useful to spot unintentional skipped products, or to see the reason why the feed failed processing
In the feeds management screen, click on View Logs link for feed. This will open a new window where you can see logs of today's processing.
If you need to see previous process logs you'll have to download the full log, use the Download Log button.
For a clean test, you should use the Clear Log button before processing the feed. This way only entries from last processing will be shown. (see Fig 4.2)
Fig 4.2 Feed log
How to read logs lines
- Each log line starts with date & time, and they are ordered chronologically.
- Batch ID XXX, acquired lock. Offset 0, Limit 50
Your feed is being processed in batch mode (in packs of products, 50 products per generation, from given offset) - product id 399 product sku hde012, skipped - REASON
The product is skipped because one of the product rules/limitations. Check Product Filters {{Skip Products with empty}} section - Items: 88 added, 0 skipped | in file /path/to/magento/root/media/feeds/feed_ID.txt
The info line which gives you information about how many products were added/skipped.