FSS Feed Creator: A Complete Beginner’s Guide

Troubleshooting Common FSS Feed Creator Errors and Fixes

FSS Feed Creator simplifies generating product feeds, but errors can interrupt exports or cause malformed feeds. This guide walks through the most common FSS Feed Creator issues, why they happen, and clear fixes so your feeds stay valid and your channels receive accurate product data.

1. Feed generation fails with a generic “Export error”

• Cause: Insufficient memory, timeouts, or server permission issues during export.
• Fixes
  1. Increase PHP limits — raise memory_limit (e.g., to 512M or higher) and max_execution_time in php.ini or your hosting control panel.
  2. Check disk space — ensure enough free space for temporary files and the generated feed.
  3. Run export manually — trigger an export from the plugin UI while monitoring server logs; note any specific error messages.
  4. File permissions — ensure the feed output directory is writable by the webserver user (e.g., chmod ⁄₇₇₅ and correct ownership).
  5. Use smaller batches — if the catalog is large, enable batch exporting or split the export into smaller date/product batches.

2. Missing or blank attributes in the feed (e.g., missing price, title, or GTIN)

• Cause: Mapping misconfiguration, missing product data, or conflicts with other plugins that alter product fields.
• Fixes
  1. Verify attribute mapping — open FSS Feed Creator mapping settings and confirm each required destination attribute is mapped to the correct source field.
  2. Fallbacks/defaults — set sensible default values or fallbacks for optional fields (e.g., “N/A” or 0) when source data is empty.
  3. Check product data — confirm the product in your store has the field populated (price, SKU, GTIN, etc.). For variable products, ensure child variations have required values.
  4. Plugin conflicts — temporarily disable plugins that modify product data (caching, price modifiers, custom fields) and regenerate a feed to isolate the conflict.
  5. Custom fields — if using custom meta keys, ensure the mapping points to the correct meta key (watch for prefixes like _ or different meta names).

3. Invalid XML/CSV structure (bad encoding, malformed tags)

• Cause: Special characters, incorrect encoding, or malformed template logic produce broken feeds.
• Fixes
  1. Set UTF-8 encoding — ensure exports are encoded in UTF-8 without BOM. Confirm server headers and file output use UTF-8.
  2. Sanitize special characters — strip or escape problematic characters (ampersands, angle brackets). Use built-in escaping options or a sanitation filter on mapped fields.
  3. Validate template syntax — if using a custom template or conditional logic, verify template tags are correctly closed and follow FSS syntax.
  4. Run XML/CSV validation — paste the feed into an XML validator or CSV linter to locate exact line/column errors.

4. Feed missing products or lower-than-expected counts

• Cause: Filters, exclusions, or status visibility settings removing items from the export.
• Fixes
  1. Check export filters — review product selection rules (category, stock status, visibility). Disable filters to test a full export.
  2. Product status & visibility — ensure products are published and catalog-visible; exclude drafts, private, or hidden products if not intended.
  3. Stock & availability rules — confirm whether out-of-stock items are excluded. Adjust