Created by potrace 1.16, written by Peter Selinger 2001-2019

Miva Developer Docs

The feed file isn’t there after Process Now#

  • Check that file saving is enabled on the feed record, with location script and a file name.
  • A folder in the file name, such as /feeds/, must already exist in the web root. Miva doesn’t create it.
  • Check the feed’s scheduled task log under Scheduled Tasks for errors.

Columns are shifted or the header has more columns than the rows#

This happens with Use Value as Feed when the feed’s Header text and the Data Builder field’s mapping don’t match.

  • Compare the column line in the feed’s Header tab with the field order on the Data Builder field’s Mapping tab. They must list the same fields in the same order.
  • If the mapping changed, the stored rows still have the old columns until they’re recomputed. Run the field’s All Products task, wait for the Queued task to stop, then run the feed.

Color and size columns are empty#

  • The product needs variants, and the feed needs Include product variants as separate feed rows on. Attribute columns are only filled on variant rows.
  • The source= must match the store’s attribute codes. Check them under the product’s Attributes tab. A store that codes the attribute colour needs source="colour".
  • For a Data Builder field, turn on Store a value for each variant and run the All Products task.

Size shows a code like M882541 instead of 38#

The attribute column shows the option’s prompt, and falls back to the option code when the prompt is blank. Give the options prompts.

The variant row’s name in Data Builder is the variant part’s own product name, which may include codes. Map the master product’s name instead, or rename the parts.

  • Image URLs use the domain’s Root Directory for Graphics. Check it under Domain Settings.
  • Main Image uses one image type. If products have no image of that type, the column is empty. Check the type code, for example main.
  • Additional Images only includes the types you chose. Images added without a type need “Images with no image type”.

Sale price is always empty#

  • Sale Price is only filled when it’s lower than the price for a shopper without an account. A price group limited to customers who log in doesn’t count.
  • Basket discounts don’t count, because they don’t change a product’s price.

A Data Builder task keeps running after All Products#

That’s expected. The All Products task works for 4 minutes and starts the Queued Products task to finish. See How a refresh runs.

Stored values don’t change after a product edit#

  • The field needs a Trigger, and the Queued Products task needs the same Trigger name and must be enabled.
  • Some changes aren’t tracked, such as price group changes and category renames. See Change notifications.
  • The feed that writes the stored rows runs separately. Run it after the field’s task finishes, or give its task a trigger delay.

A provisioning import changed nothing, or emptied a feed#

  • Page_Update replaces every setting. A missing <FieldMap> leaves the feed with no fields. Send the whole block.
  • The page code must be FEEDBUILDER_<feed code> or FEEDDATAFIELD_<field code>.
  • Feed_Add for a Feed Builder feed needs a <Settings> tag, even an empty one, or the builder page isn’t created.
  • ScheduledTask_Add for a Data Builder task needs the field to exist first.
  • MivaLabs Feed Builder must be installed under Settings > Utilities before the import. An import doesn’t install it.

The module “is in use” and can’t be removed#

Uninstall it from the store first, then delete it from the domain. Delete the MivaLabs Feed Builder feeds under Marketing > Feeds and the scheduled tasks that use the module before uninstalling. See Uninstall.

“MivaLabs Feed Builder is not installed in this store”#

The module was uploaded to the domain but not installed in this store. Install it under Settings > Utilities. Miva lists every uploaded feed module under Add Feed whether or not it’s installed.

“Table s01_FeedBuilderRegistry already exists” when installing#

The module was removed without uninstalling it, so its tables were left behind. See Install the module.

Saving a feed’s settings does nothing#

Saving is refused when a field has no output name or source, a constant has no value, or a condition is missing its field or value. The settings page doesn’t always say which; check each field card for a red border.