- Home
- What's New
- Advanced Product Feeds for Magento 2
🎯
Feature Spotlight
Overview
60 releases in the last year
Each square is a week. Pick one to jump to its releases.
Less
More
November 2026
Nov 20
1.17.8
Nov 20
Improved
-
⚠️ Constructor changes for code that extends the feed repository or the filter conditions text —
Mirasvit\Feed\Repository\FeedRepositorynow also takesMirasvit\Feed\Service\Feed\FilenameService, andMirasvit\Feed\Service\Rule\ToStringServicenow also takesMagento\Framework\Escaper. Code that extends these classes or passes their arguments in its owndi.xmlneeds to be updated.
Fixed
-
Security improvements — A feed filename may no longer contain line breaks, slashes or the characters
< > & ? #, and the feed form reports such a name before it is submitted. Liquid tags and filters stay allowed. A feed saved earlier with one of these characters keeps saving until you change its name.
Nov 18
1.17.7
Nov 18
New
The ChatGPT feed template exports OpenAI's variant and review fields
The bundled ChatGPT template now has the four columns OpenAI's Commerce platform reads to group variants and show ratings:
listing_has_variations, variant_dict, review_count and star_rating. The same values are available as the product attributes Listing Has Variations, Variant Options (JSON), Review Count and Star Rating (0-5), so they can be added to any template.
Fixed
-
Virtual products that belong to a configurable are now treated as variants — The configurable attributes of a product (
product.configurable_attributesin a template pattern) were filled only for simple children, so a virtual child of a configurable exported them empty. They are now exported for virtual variants as well.
Nov 16
1.17.6
Nov 16
Fixed
- Security improvements — The attribute library page in the admin declared the escaping of one line in a form Magento's security check does not recognise, which blocked 1.17.5 from being published on the Adobe Commerce Marketplace. It now uses the recognised form. The page renders exactly as before.
Nov 13
1.17.5
Nov 13
Fixed
-
Simple products that belong to a configurable and a grouped or bundle product export the configurable as their parent — A simple product can be a configurable variant, a grouped product member and a bundle selection at the same time. The feed took whichever of these parents Magento had created first, so when the grouped or bundle product was older than the configurable,
product.parentpointed at it and the shipped templates exported its id asitem_group_id. Variants of one configurable were then split across several item groups or mixed with unrelated products in shopping channels. The configurable is now always preferred, then a grouped product, then a bundle, soitem_group_idgroups the variants of the same configurable. The same parent is now used for the product URL with preselected options, the configurable attributes, and the Parent Status, Is Salable and children-count filter conditions. A simple product whose only parent is a grouped or bundle product still gets that parent, as before. On Magento Commerce and B2B the parent is also resolved correctly when the product has staged versions.
Nov 13
0.0.6
Ai Core
Nov 13
Fixed
- The temperature an AI feature asks for is now always sent to OpenAI and Grok. Before, a temperature equal to the store's Default temperature was left out, so the provider's own default applied instead (1.0 for OpenAI).
Nov 10
1.17.4
Nov 10
Fixed
-
⚠️ Saving or duplicating a product filter no longer fails on stores upgraded from old versions — On some stores upgraded from old versions of the module, the
mst_feed_ruletable still carried the leftover columnsactions_serialized,created_atandupdated_at. The module has not used them for years, but because they are required columns with no default value, every attempt to save a new filter or duplicate an existing one was refused with "Column 'actions_serialized' cannot be null" (or the same error forcreated_atorupdated_at), so filters could not be managed at all. An upgrade patch now drops all three leftover columns when they are present. The patch does nothing on fresh installs or on stores that already lack the columns. Runbin/magento setup:upgradeafter the update.
Nov 6
1.17.3
Nov 6
Fixed
-
Bundles whose children are all out of stock are no longer exported at price 0 — Magento prices a bundle from its in-stock selections only, so a bundle whose enabled children had all gone out of stock exported Final Price, Regular Price and Min Price as 0, and
g:pricein the shipped templates with it. These bundles are now priced from their enabled selections regardless of stock, the same way configurable and grouped products already were: the price after the bundle's own special or tier discount, with each selection taken at its configured quantity so a child's tier price counts, as on the storefront. Regular Price stays the undiscounted price, so a sale on such a bundle remains visible, and both are in the store's display currency. - The "Final Price" product filter reads the exported price — A bundle, configurable or grouped product whose children are all out of stock reports a raw final price of 0, so a filter such as Final Price > 0 dropped it from the feed although the feed exported a positive price for it. The filter now checks the same price the feed exports, so the filter and the feed agree.
- Security improvements
-
⚠️ Constructor change for code that extends the feed filter condition —
Mirasvit\Feed\Model\Rule\Condition\Productnow takesMirasvit\Feed\Export\Resolver\Product\PriceResolver. Code that extends this class or passes its arguments in its owndi.xmlneeds to be updated.
Nov 6
0.0.5
Ai Core
Nov 6
Fixed
- Some AI provider error messages were shown as raw JSON. They are now shown as plain text.
Nov 4
1.17.2
Nov 4
New
Bundle Final Price attribute
A new Bundle Final Price product attribute (
bundle_final_price) gives a bundle's price after discounts: its default selections at their default quantities, each at the guest price, with a dynamic bundle's own special or tier percentage applied the same way as on the storefront. With no discount it equals Bundle Regular Price. Before, the only option was Final Price, which for a bundle is the cheapest single-unit combination with no quantities. A template comparing it with Bundle Regular Price therefore flagged every multi-quantity bundle as on sale, which triggered Google Merchant Center "price mismatch" disapprovals. Use Bundle Final Price as the bundle sale price in your templates.
Improved
- Faster feed exports — Product attributes that are not prices (SKU, name, description and so on) no longer run the guest-price check. That check ran a catalog price rule database query and switched the customer group for every attribute of every product, which cost about a third of the export time on templates with many attributes. Prices are still always exported as the guest (NOT LOGGED IN) price.
-
⚠️ Faster feeds grid when feeds have large validation results — The feeds grid counts each feed's validation errors and warnings on every load. On large validation results this took seconds per feed and could make the grid time out. A new
(feed_id, severity)index on themst_feed_validationtable speeds up this count (about 2.0 s → 0.37 s on 524k rows). Runbin/magento setup:upgradeto add the index.
Fixed
- Feed admin pages check admin role permissions — Any admin role, whatever its permissions, could load 17 feed grids and forms, including the feeds grid, which contains FTP/SFTP passwords. Each now requires the matching feed permission. Pages under Filters now check the Filters permission, the same as the menu, so a role that has the feed section but not Filters no longer opens pages whose grids then refuse to load. The Feed report now checks the Feed report permission. Check your admin roles if some users need to keep access to these sections.
- Feed admin actions require the admin secret key — Opening a link was enough to trigger Preview, the template library, validation, dynamic variable validation and dynamic attribute actions, bypassing Magento's secret key check. They now require the secret key or form key like other admin actions. The Preview and Validate popups now send the form key, so they keep working.
- Feed templates are limited to product and store data — Template expressions can now read only data values, such as attributes, prices and store settings. Expressions that tried to reach Magento internal objects now return an empty value. Update to this version to close this security issue.
- Dynamic variable codes are limited to letters, digits, "_" and "-" — Codes with any other characters are now refused on save with a translated message, and an existing variable with such a code no longer loads its file. Update to this version to close this security issue.
- Preview errors are shown as plain text — Preview returned the error from a broken template tag as HTML, so markup inside the tag could run in the browser of the admin opening the preview. The error is now logged and shown as a translated plain-text "Preview failed" message.
Nov 3
0.0.4
Ai Core
Nov 3
New
Modules can set their own time limit for a single AI request, so a feature that has to answer quickly is not held up by the store-wide request timeout.
Fixed
- A Grok request with an attached file no longer hangs when xAI cannot be reached: the file upload now gives up connecting after a few seconds, like the request itself.
October 2026
Oct 29
1.17.1
Oct 29
Improved
-
⚠️ Old feed files are cleaned up per feed, not by a cron sweep — When a feed publishes under a new name (renamed, dated filename, changed type, compression or JSON framing), its previous file and JSON sidecar are removed once the export completes, and deleting a feed removes its file, sidecar and previews. A file that another feed of the store still publishes is kept, and a file that cannot be deleted (for example an S3 error) is logged instead of failing the export or the delete. The
feed_clean_filescron job is removed, because whenmedia/feedis shared with another Magento installation (such as one S3 bucket) the sweep deleted the other installation's live feeds. Files left over from earlier versions can still be removed withbin/magento mirasvit:feed:cleanup, which now warns that it also removes another installation's files in shared storage. TheMirasvit\Feed\Cron\CleanupOldFeedFilesCronclass is removed. -
⚠️ Constructor changes for code that extends the feed —
Mirasvit\Feed\Cron\ExportCronnow takesMirasvit\Feed\Model\ResourceModel\Feed\CollectionFactoryinstead of the feed collection,Mirasvit\Feed\Model\Feed\ExporterandMirasvit\Feed\Repository\FeedRepositorytakeMirasvit\Feed\Service\PublishedFileCleaner, andMirasvit\Feed\Export\Resolver\Product\PriceResolverandMirasvit\Feed\Model\Rule\Condition\Producttake the newMirasvit\Feed\Service\GuestPriceService. Code that extends these classes or passes their arguments in its owndi.xmlneeds to be updated.
Fixed
- Disabled feeds are no longer exported on schedule — A feed that was disabled, or had its cron schedule switched off, could still be generated by cron: the export cron could reuse an already-loaded list of all feeds, and a feed queued while active and disabled before the queue ran was exported anyway. Both cases are fixed: the export cron now reads the feed list fresh on every run and re-checks that a feed is enabled and scheduled, and a queued generation of a feed that has been disabled since is skipped and marked as failed.
- Feeds always export the guest (NOT LOGGED IN) price — A feed generated while a customer was logged in, or filtered on Final Price, could use that customer group's tier price or catalog rule price instead of the public price shopping channels must see. This affected simple products, configurable, grouped and bundle products (including the min_price of their children). Prices and the Final Price product filter now always use the guest price.
- Scheduled feeds no longer skip a time slot around midnight — When a long export delayed a feed past midnight, a time slot configured late on the previous day was lost until its next scheduled day. That missed slot now runs late instead, and only when the feed's last run was yesterday, so a feed is never generated on a day it is not scheduled for.
- Feed validation works for feeds migrated from older versions — Validation rules of migrated feeds were stored in the wrong format, so every such feed reported "Valid" whatever its content. An upgrade patch repairs the stored rules of existing feeds and templates, one record at a time, and leaves correct rules untouched. After the upgrade these feeds are validated for the first time, so they may show validation warnings or errors they did not show before.
- FTP/SFTP password is no longer autofilled with the admin password — Browsers filled the feed's FTP/SFTP password field with the saved admin login, silently storing the wrong delivery password. The field now opts out of credential autofill. If a feed's delivery stopped working because of this, enter its FTP/SFTP password again.
- Logo upload on feeds and templates — A logo is now saved only when its file was actually written, and the previous logo is kept otherwise. If the logo cannot be saved, the feed or template is still saved, the previous logo is restored, a clear error is shown instead of "You saved…", and you stay on the edit form.
- Category mapping files no longer flood the log — Every complete read of a category mapping file was logged as a read failure; it is now logged only when a file really cannot be read. Mapping files stored on Amazon S3 are read reliably.
- Shipped templates lock Framing and Marketplace — These two fields could be edited on a shipped template and the save was then refused; they are now locked like the template's other general fields.
Oct 26
1.17.0
Oct 26
New
Feed is listed in the Core AI settings
Advanced Product Feeds now appears in the "modules using AI functionality" list of the Mirasvit Core AI settings, using the default AI provider configured there.
Improved
-
⚠️ Requires Mirasvit Core 2.0 — The module now requires
mirasvit/module-core2.0.0 or later and the newmirasvit/module-ai-corepackage. Composer installs them with the update; runsetup:upgradeafterwards. Code that extended or injected the Core helpers the feed no longer uses (Mirasvit\Core\Helper\Io,Mirasvit\Core\Helper\Image,Mirasvit\Core\Service\SerializeService,Mirasvit\Core\Service\YamlService) needs to be updated. -
Image resizing works on remote media storage — The
resizefilter in feed templates now uses Magento's own image processor and works whether media is stored locally or on Amazon S3. Resized images are cached underpub/media/mst_feed/cache, so their URLs in the feed change once. Two exports resizing the same image at the same time no longer clash, temporary files are always cleaned up, and an image that cannot be resized is exported at its original URL and the failure is logged. -
The feed export lock is kept on the local disk — The per-feed lock file now lives under
var/instead ofpub/media, so locking works the same when media is on S3 or a network drive. Reset on a feed now removes this lock file too. - Older product filters keep working — Feed product filters saved in the old storage format, or imported from older YAML files, are still read correctly. A filter that cannot be read is logged and skipped instead of breaking the export, preview or filter form, and saving such a filter shows an error message instead of an error page.
Fixed
- Out-of-stock products no longer appear as "in stock" in feeds (MSI) — With Multi-Source Inventory, a product whose source was flagged In Stock with quantity 0 and backorders off was exported as in stock, and the Is in stock (inventory) filter kept it. This most often affected configurable products whose only variants were in this state, and sent unsellable products to Google and Facebook. Stock status and the filter now use Magento's salable check, based on the stock assigned to the feed's website. Filtering for out-of-stock products in the default fast mode no longer drops products that should be kept. The stock is looked up once per store instead of once per product.
-
A duplicated feed gets a sensible filename — Duplicating a feed named its copy after the internal working file, so it published as
mst_feed_4.xml_copy.xml. The copy now takes the original's filename with_copy, or_copy2,_copy3and so on if that name is already taken. - Two feeds can no longer publish to the same file — The duplicate-filename check on save compared internal names and never found a match, so two feeds with the same filename and type could overwrite each other's file. Saving a feed that would publish to the same file as another feed (same filename, extension and compression) is now refused. A feed with an empty filename is not checked.
- CSV feed validation without a delimiter — Validating a CSV feed with no column delimiter set could crash on PHP 8 or pass a file it never checked on PHP 7.4. It now stops with a clear message asking you to choose a delimiter, translated into every supported locale. The tab delimiter is also recognised reliably on every PHP version.
- AI profiles with a blank name — An AI profile could be saved with an empty or whitespace-only name through an update, the REST API or an import, leaving it with no label in the admin. A blank name is now refused on save, and an existing unnamed profile is shown by its code.
- Fixed an error when the feed edit form was built outside a regular browser request, for example from the API or command line.
Oct 23
0.0.3
Ai Core
Oct 23
Improved
- The list of AI-enabled modules on the Core AI settings screen is shown as styled cards again.
Fixed
- An AI request no longer hangs indefinitely when a provider cannot be reached: the connection now gives up after a few seconds even when the request timeout is left disabled, so a blocked or unreachable provider fails quickly instead of stalling the admin action, cron, or page.
Oct 21
1.16.0
Oct 21
New
Parquet feed type
Choose Parquet in the Type selector of a feed or template to publish your catalog as an Apache Parquet file, the columnar format read by data warehouses and analytics tools. Columns and their types (text, numbers, prices, lists) come from the template's declarations, and each value is converted to its column's type. The file is written in row groups across the export's passes, so large catalogs export without hitting time limits, and the output is checked against files written by the standard pyarrow library.
New
Parquet preview
Previewing a Parquet feed shows its column schema and a table of the rows it will write.
New
Parquet validation
bin/magento mirasvit:feed:validate checks a Parquet feed's file structure, and your field validation rules are applied to the rows of the file the feed published, read back row group by row group.
New
Custom JSON and Custom Parquet starter templates
The Custom Feeds block on the New Feed screen now offers blank JSON and Parquet templates alongside Custom XML, CSV and TXT, with typed price and weight fields and a list of additional images ready to edit. Existing stores get them on
setup:upgrade.
New
Schedule a feed by cron expression
The feed's Scheduled task section has a new Schedule mode: Fixed times (the existing days-and-times picker, still the default) or Custom cron expression, which takes a standard five-field cron expression such as
*/15 8-18 * * 1-5. The expression is required in this mode and validated on save with the wrong field named, and a plain-language preview of when it will run updates as you type. The next run time is shown for both modes, and the schedule wording is translated into every supported locale.
New
Bundle Regular Price attribute
A new Bundle Regular Price product attribute exports a bundle's regular price calculated from its default selections, converted to the store's display currency like the other prices.
Improved
- JSON Lines is now part of the JSON type — The standalone JSONL type is no longer offered in the Type selector; choose JSON with its "one object per line" framing instead. Existing JSONL feeds keep working and are shown as JSONL (legacy), but a new feed can no longer be created from a JSONL template, either in the admin or through the REST API.
- Faster exports for feeds using attribute set, dynamic attribute, dynamic variable or category mapping values — These were loaded again for every product (a category mapping alone could cost over 20 database queries per product). They are now loaded once per feed export and reused, and an edited category mapping is picked up on the next export instead of an outdated copy being used.
- Scheduled feeds start on time — The feed export cron job now runs every minute instead of every 30 minutes, so a cron-expression schedule fires in the minute it matches. A check that finds nothing due writes no history entry, and a feed that is still generating is skipped instead of being logged as an error. Looking up the last cron run is also a single lightweight query.
- Google Merchant Center upload is offered only for CSV, TXT and XML feeds — The Google Merchant options no longer appear for JSON and Parquet feeds, which Merchant Center does not accept.
-
⚠️ New columns
cron_mode,cron_expressionandcron_started_atin themst_feed_feedtable, added bysetup:upgrade.
Fixed
-
Two exports of the same feed can no longer run at once and corrupt the file — On shared filesystems without file locking (NFS, AWS EFS), the per-feed export lock silently did nothing, so two exports of one feed could interleave their output (for example, duplicated
<?xml?>headers). The lock is now held in the database and works on every filesystem. It is also released correctly when the lock file cannot be opened, and it nests safely on Magento 2.3, which allows only one database lock at a time, so scheduled and queued feeds keep exporting there. - A scheduled feed whose run failed or was stopped is no longer restarted right away — It now waits for its next scheduled time.
- Feed prices are in the store's display currency and labelled with it — A configurable product's regular price and the price of products whose variants are all out of stock were exported in the base currency while other prices were converted. Every final price and regular price the feed outputs is now converted, and the bundled templates name the display currency next to them (Ceneje now fills in its currency code and regular price, and Fyndiq's old price reads the regular price).
- Bundled templates no longer hardcode a currency — Fourteen templates printed a fixed code such as USD or RON, or left the currency empty, so stores with another base currency published mislabelled or unpriced feeds. They now use the store's base currency (Rozetka keeps UAH, its only currency).
- Prices in bundled templates are rounded — The Ceneje, Kwanko, Fnac and VidaXL templates, and the new Custom JSON and Custom Parquet templates, printed converted prices unrounded (for example 24.0278 instead of 24.03). They now format them as prices, which also keeps Parquet price columns from coming out empty.
- Custom JSON and Custom Parquet logos now match the style of the other Custom template logos.
- Dynamic Variables are validated correctly — The syntax check reported every variable as invalid, including ones with correct code. It now checks the PHP code properly, without running it.
-
A missing Dynamic Variable file is reported instead of exporting a blank value — When a variable's PHP file is missing (for example after a server migration that did not copy
var/), the feed exported the value empty with no warning. The export now finishes with a warning naming the affected variables, and the problem is written to the log. This check no longer re-reads the file for every product. - Saving a JSON or JSONL feed or template from the admin form no longer loses its content.
- The XML editor of a JSON feed shows and saves the template you wrote, not its compiled internal version.
- A feed validated with both field rules and declared-type checks no longer fails its export.
- Parquet reliability — An interrupted Parquet export no longer publishes wrong rows; a number too large for a 32-bit float column is written as empty and reported instead of being stored as infinity; a damaged or truncated Parquet file is reported as a validation error instead of passing as clean; and a file the validation cannot read is written to the log instead of being silently ignored.
- Fixed a PHP 8.5 deprecation notice caused by a template element without a declared type.
- Fixed the AI Clear values confirmation ignoring its "overridden values" checkbox when the checkbox ID contained special characters.
Oct 14
1.15.16
Oct 14
New
"is not" condition for multiselect attributes in feed filters. Product filter conditions on a multiselect attribute (for example Activity or Material) now offer the is not operator. With one or more values selected, it keeps only products that have none of them: "Activity is not Hike, Sports" drops every product tagged Hike or Sports. Left empty, it keeps products that have any value set for the attribute and drops those where it is blank, which was not possible before. The filter gives the same result whether products are checked one by one or filtered directly in the database, and an unexpected stored value is safely ignored instead of being treated as a match.
Fixed
- The Library of Patterns in the feed template editor no longer fails to open. Depending on which other scripts happened to load first on the admin page, the widget could stop with a "_ is not defined" error in the browser console and stay unusable. It now loads the library it depends on itself, so it works on every page load.
Oct 6
1.15.15
Oct 6
Fixed
-
A replaced feed or template logo now shows the new image straight away. Each logo is stored under the same file name every time you upload one, so the admin's link to it never changed and the browser or CDN kept showing the old, cached picture after a replacement. The logo link now changes whenever the image does, so the new logo appears at once. Clearing or replacing a logo also used to leave the old file behind in
pub/media, and that stale picture could come back on the next upload; the old file is now deleted. This works on remote media storage such as Amazon S3 too. - Duplicating a feed or template no longer puts the original's logo at risk. A duplicate pointed at the same logo file as the original, so saving the copy or clearing its logo deleted the original feed's or template's logo as well. A copy of one of the bundled templates could delete the bundled logo (for example the Bing logo) in the same way. A duplicate now gets its own copy of the logo, and saving a feed or template only ever deletes a logo file that belongs to it, which also protects copies made before this update. Re-saving an existing feed also no longer replaces its own logo with a template logo of the same name; a feed takes its logo from a template only when it is created from one.
-
A
{% capture %}block that loops overcontext.productsnow renders its content. A product loop placed inside a{% capture %}(for example, to compute a timestamp shown in the feed header) was mistaken for the feed's main product loop: once it had gone through the products it stopped the whole export, so the captured value and everything after it came out empty on every run. JSON Lines feeds built from column patterns were hit the same way, because each column is wrapped in a capture. Loops inside a capture now run through to the end and the rest of the feed renders normally; the main product loop works as before. - Products are no longer silently missing from a feed when an export is split into several runs. A large export pauses when it reaches its time limit (or is stopped) and continues in the next run. If that pause happened while a product loop nested inside the main product loop was running, as it does in JSON Lines feeds built from column patterns, the product being written at that moment was skipped and never appeared in the feed. Only the main product loop can now pause the export, and it does so between products, so every product's row is written in full.
Oct 6
0.0.2
Ai Core
Oct 6
Improved
- Updated the model lists for every provider to current families — Claude (Opus 5.5, Sonnet 5.5), Gemini (3.8 / 3.7 Flash), Grok (4.7 / 4.6 / 4.5) and OpenAI (GPT-6 and GPT-5.6 families); retired OpenAI models (gpt-4, gpt-4-turbo, gpt-3.5-turbo) are dropped from the list and a stored value for one is migrated to a current model.
Fixed
-
Reasoning / effort-controlled models no longer fail with "temperature is deprecated for this model": the
temperatureparameter is omitted for Claude 4.8+ and OpenAI GPT-5 and later (version-based, so new model generations are covered automatically). - Claude no longer rejects a request with "each stop sequence must contain non-whitespace": whitespace-only stop sequences (e.g. a bare newline) are dropped before the request is sent.
Oct 5
0.0.1
Ai Core
Oct 5
New
Initial release. The AI subsystem extracted from Mirasvit Core into its own package (
Mirasvit\AiCore): the provider integrations (Claude, Gemini, Grok, OpenAI), the request/response API with image-attachment support, request-header normalization, AI logging, and the admin provider configuration. Modules that use AI now depend on this package instead of carrying the integration in Core.
Oct 2
1.15.14
Oct 2
Fixed
- Configurable and grouped products whose variants are all out of stock no longer export a price of 0. Magento only counts in-stock variants when it works out the price of a configurable or grouped product, so once every variant sold out the feed's price, regular price and final price came out as 0. Google Merchant Center then suspended the item for a £0 price, and services that read the feed, such as Klaviyo, picked it up as a free product. When no in-stock variant is left, the price is now calculated from all enabled variants, ignoring stock, so the product keeps its real price in the feed. Products with at least one variant in stock are priced exactly as before.
-
Unexpected errors in the feed and AI profile admin screens no longer show database details to the admin. When saving an AI profile, clearing its stored values, previewing it, or previewing a feed's JSON output ran into an unexpected error, such as a database failure, the raw technical message was shown on screen, including the SQL error code and the full database query. The raw message is no longer shown on any of these screens. Saving an AI profile, clearing its values and the feed JSON preview now show a short, translated message saying what failed, and the full details are written to Magento's exception log (
var/log/exception.log) for your developer. Messages that explain what to fix in the form or template, such as "Choose a kind before previewing", are still shown as before. The new messages are translated into all 15 bundled languages.
September 2026
Sep 30
1.15.13
Sep 30
Improved
- Feeds that export category paths generate faster on large catalogs. The full category path (for example Men > Tops > Jackets) was rebuilt from the database for every product, even when thousands of products share the same few categories, so a large feed made one database query per product just for that column. Each path is now built once per category and store view during an export and reused for the rest of it. Category names still follow the feed's store view, and the output is unchanged.
Fixed
- AI optimization now works through products in a predictable order. Each AI run takes a limited batch of the products that still need work, but that batch was picked in whatever order the database happened to return rows, so which products got processed in a given run was unpredictable. The batch is now always the products with the lowest IDs that still need work, so the catalog is worked through steadily from one run to the next.
Sep 23
1.15.12
Sep 23
New
JSON is now a feed type. Pick JSON in the Type selector, next to CSV, TXT and XML, to publish a feed whose deliverable is the JSON file itself, with no XML copy alongside it. You still write the template as XML markup. It is compiled once into a template that prints JSON directly, so memory stays flat however large the catalog is. Attributes on the elements control the output:
xsi:type sets a value's JSON type (number, boolean, …), xsi:nil writes null, xsi:list makes an array, xsi:name sets the key, xsi:omitEmpty drops empty values, and xsi:record="true" marks the element that repeats once per product. Numbers keep exactly the digits your template produced, so a price of 34.00 is not cut to 34, and a value with broken characters is cleaned so the file still parses. If the template has no record element, has more than one, has more or fewer than one product loop, or has a key with an apostrophe, you get a plain message saying what to fix.
New
Choose how a JSON feed is framed: one document or one object per line. A new Framing option on the feed and template forms (shown for the JSON type only) switches between a single JSON document and JSON Lines, one record per line, which data pipelines read line by line. The file extension follows your choice:
.json for one document, .jsonl for one object per line. Templates keep this setting when exported and imported.
New
Values that don't fit their declared type are reported, not guessed. If a value in a JSON feed doesn't match the type declared for it, such as a price that isn't a number, it is written as text instead of a made-up
0. The feed preview lists each one (key, declared type and value), and the feed validation results name them too. Validation reads the feed using the framing set on the feed, so a one-record document and a one-line JSON Lines file are both checked correctly. The preview lays out a one-document JSON feed in readable, highlighted form without changing any value.
Improved
- The Generate JSON checkbox on XML feeds now says it is the legacy way to get JSON and points to the new JSON type. It still works and produces the same output as before.
-
⚠️ New column
json_framing(varchar(16), defaultdocument) in themst_feed_feedandmst_feed_templatetables. Runbin/magento setup:upgradeafter updating.
Fixed
-
Only admins with the Import/Export data permission can import or export feed templates. The actions that run a template import or export did not check the Import/Export data role permission (
Mirasvit_Feed::feed_import), which the Import/Export page itself already checks. So any admin user who could log in could reach them directly, whatever their role. They now check it, and admins without it are refused.
Sep 16
1.15.11
Sep 16
Fixed
- Feed cron no longer piles up idle PHP processes until the server runs out of memory. The feed cron group runs each due job in its own PHP process, and nothing stopped a second one from starting while the first was still working: an export that ran longer than its schedule interval was joined by a fresh process at every interval, and the one-minute queue job re-read the pending queue and started exporting the same items again alongside itself. Each of those processes costs 300–400 MB just to boot, so on a store with a long export they accumulated faster than they finished and the box eventually ran out of memory — the symptom was several feed processes sitting at 0% CPU and ~330 MB each. Both the scheduled export job and the generation-queue job now check whether a run is already in progress and simply do nothing until it finishes, and the marker is released even if a run crashes, so the next scheduled tick always gets its turn.
-
A feed that is already being exported now says so straight away instead of hanging, and a failed export no longer blocks the feed afterwards. When an export was already running for a feed, a second attempt waited on it indefinitely rather than reporting the feed as busy:
bin/magento mirasvit:feed:export --id=Nprinted nothing at all instead of "already locked by another process", and a fully booted Magento process sat idle for as long as the other export took. On top of that, an export that ended in an error left the feed marked as in progress, so the next queued generation of that feed waited on a lock that would never be released and the cron run stalled. A busy feed is now reported within a second, and the marker is always cleared when an export ends, successfully or not — so the run moves on to the next feed. Stores whose media directory sits on a filesystem without file locking (NFS, AWS EFS) keep generating feeds as before.
Sep 15
1.15.10
Sep 15
Fixed
- Admin pages belonging to other extensions no longer fail with "The element with the '…' ID wasn't found". To keep its own admin screens from tripping a PHP deprecation notice, the extension quietly gave a name to any admin panel that had been left unnamed — including panels that belong to other extensions. When such an extension later named that panel itself, Magento could not find the name we had invented and the page died with that error instead of loading; Firebear Improved Import & Export's import job edit screen was one of them. Naming is now limited to this extension's own panels, so everyone else's pages are left alone and load normally, while our screens stay free of the deprecation notice.
Sep 14
1.15.9
Sep 14
Fixed
-
A sale that is live on the storefront is now priced as a sale in the feed. The feed decided for itself whether a special price was still inside its from/to window, and it asked the server's UTC clock — while Magento judges that same window on the wall clock of the admin timezone, deliberately, so one special price means the same thing in every store view. The two disagree by exactly that timezone's offset, so on a store ahead of the server the storefront was already charging the sale price while the feed still published the full one, at every hour of the day. That is the "mismatched value" disapproval in Google Merchant Center and its equivalents elsewhere. The window is now Magento's to judge, so the feed and the storefront always quote the same price. An open-ended special (no end date) still applies, a window that has closed or has not opened still exports no sale price at all — not a
0, which would advertise the product as free. -
A fractional stock quantity is no longer rounded down. Quantity was exported as a whole number, so a product stocked by weight or volume — 0.5 kg of something, 2.5 m of cable — shipped a quantity of
0and read as out of stock in every channel that trusts that column. Fractional quantities, and the summed quantity of a configurable's or grouped product's children, now export as they are actually stocked. A whole-number quantity is unaffected:5still exports as5. -
{% if a and b and c %}now checks every condition in a feed template. A template condition joining three or more comparisons withand/oronly ever evaluated the last two — everything before them was silently discarded, so a three-part rule guarding a column emitted the wrong branch with nothing in the log. Conditions are now folded left to right across the whole statement. Two-conditionifs, which is what most templates use, behaved correctly before and are unchanged. -
The feed statistics chart no longer drops days with no traffic. A day with no recorded clicks was left out of the sparkline entirely rather than drawn as a zero, so three active days in a fortnight rendered as three adjacent bars and a sporadic feed read as one with steady traffic. Every day in the selected period now contributes a point, a quiet day as a genuine
0, so the shape of the chart matches the period it covers. -
Feed generation and AI optimisation survive a media mount that has dropped out. The advisory lock file that keeps the admin, cron and CLI export paths from colliding was created under
pub/media/feed/tmp, and the AI optimisation run kept its own lock in the same place. Where media is a remote or network mount (NFS, AWS EFS) that has lost its transport — after an OOM kill, say — opening that file failed before a single product was exported, and every feed on the store stayed broken until the mount came back. Both locks now live invar/mst_feed/tmp, next to the export's scratch and progress files, which already moved there: a transient coordination file has no business on shared storage. Nothing about how you use the extension changes; if a monitoring check watches for a stale.lock, point it at the new directory. - The AI profile template picker is no longer empty on stores that keep media on remote storage (Amazon S3 and compatible). The bundled profile templates ship inside the extension's own directory, but were being read through the remote-storage driver, which answers for a key that has never existed in the bucket with an empty file rather than an error. Every template then parsed as broken and was quietly skipped, so the picker offered 131 entries on an ordinary store and none at all on an S3 one, with no exception anywhere to explain it. They are now read from the local disk they actually live on.
- Google category mapping works again on PHP 7.x. An empty search was read as "match nothing" rather than "match everything" on PHP 7, so the taxonomy came back empty with nothing logged: the category-mapping autocomplete in the admin offered no suggestions when opened with an empty box, and validation rejected every real Google category as invalid. Both work as they do on PHP 8 now.
- A CSV template saved without a format no longer breaks the feed. A template is allowed to carry just a name and a type, and one saved that way reached generation with no column delimiter at all — a fatal error on PHP 8 and a run-together line on PHP 7. Such a template now renders with no separator rather than failing, and no delimiter is invented on your behalf.
- The feed history grid remembers your Columns choice. The Columns dropdown rendered and worked, but the selection — along with filters and page size — was gone on the next load, with no error and nothing in the log. The grid now saves its view the way every other grid in the extension does.
- An empty product selection no longer ends in a database error. Previewing a feed whose store view belongs to a website with no products assigned answered with a raw MySQL syntax error instead of an empty preview — the empty list of products was handed to the database as an empty condition. An empty selection is a legitimate answer and is now treated as one: the preview simply comes back empty. In the same vein, a feed left with no filter rule at all now explicitly clears its product set, so detaching the last rule no longer leaves the previous run's products attached to it.
- The Order # column in the SKU report resolves again. The column is now backed by a direct link from the report row to the order it was attributed to, so it shows the order number rather than nothing.
- Feed columns in the reports no longer go through a temporary table. The relationship between a report row and its feed was declared the wrong way round — the reporting engine believed one report row could have many feeds — so adding a Feed column pushed the data through a temporary table instead of joining it directly. Reports that group or filter by feed are now built with a plain join.
Sep 7
1.15.8
Sep 7
Improved
-
An empty feed now tells you it is empty. A generation that matched no products used to finish with a green Feed file was generated., a blank or negative Products in feed count and a stray Valid 0 — with an empty file and no hint as to why. Such a run now ends with a warning that names the usual causes (the product filter matched nothing, the chosen store view has no products assigned, the catalog indexes are invalid) and links the troubleshooting guide, and the count always reads as a real number, including a genuine
0.
Fixed
- Category filters now select the products they describe. With Enable fast mode filtering on — the default on every feed — four of the Category operators compared the single category id stored per product against the whole comma-separated list you picked, so Category is 5, 7, 12 produced an empty feed and Category is not 5, 7, 12 exported the entire catalog. Does not contain was wrong in a second way: it matched the ids as text, so excluding categories 3 and 4 also quietly excluded 13, 23, 30, 34 and every other id containing those digits. Is, is not, contains and does not contain now all ask the indexed category-membership question — a positive operator means "in one of these categories", a negative one "in none of them" — in both filtering modes, so saved rules match correctly and both modes agree. Is one of / is not one of are unchanged.
- A filter that combines conditions with ANY no longer empties the feed in fast mode. Fast mode narrows the catalog with a database query before checking each product, and a condition that has no database equivalent — Quantity, Is Salable, the image fields, a PHP condition and a dozen more — was simply left out of that query. Inside an ANY group that made the query stricter than the rule: measured on a 2,046-product store, Quantity is greater than or equal to 0 OR SKU is NO-SUCH-SKU kept all 2,046 products with fast mode off and exported none with it on, with nothing in the log to explain it. An ANY group is now used to narrow the catalog only when every condition in it can be expressed as a query; otherwise the feed checks the full candidate set — slower on such a rule than before, and correct, where before it was fast and wrong. Rules that are a plain ALL list of ordinary attributes, the common case, keep exactly the speed they had, and stock filters keep selecting the same products as always.
- Final Price filtering in fast mode is exact again. 1.15.7 started reading Final Price from Magento's price index to narrow the catalog, and that is not the same number the filter itself computes: on stock sample data 26 of 147 configurable products disagreed, and because the narrowing runs first, a product the rule keeps was never even looked at — Final Price is greater than or equal to 25 silently left out a product priced at 28.00. The index also holds enabled products only, and under a per-website or per-customer-group price index it can be empty altogether, which would have emptied every Final-Price feed. Final Price is now decided by the same per-product calculation the slower mode uses, in both modes, for simple, configurable, bundle and grouped products alike.
-
Filters left with an empty value now match exactly what they match with fast mode off. 1.15.7 gave three of them a fast-mode condition, and two of those did not agree with the slower mode: is not one of with nothing selected kept every product that has a value for the attribute, where the filter in fact matches no product at all — on the sample catalog that was 47 of the 81 products the admin preview offered for a rule that selects nothing — and is one of with nothing selected built no condition, so fast mode let the whole catalog through. Both now select nothing, as they do with fast mode off. Is not with an empty value — the "is not empty" filter — keeps its meaning and no longer drops a product whose value is
0. -
forloop.firstandforloop.lastwork in feed templates. Both were computed from the product's internal id rather than its position in the loop, so{% if forloop.first %}never once matched andforloop.lastfired on whatever product happened to carry the matching id — the documented way to write a feed-level value into a header produced nothing. Both flags, andforloop.notlast, now follow the loop's own position. -
A value captured out of the product loop now reaches the header and footer. The documented pattern —
{% capture %}around{% for p in context.products %}— came out blank: the end of the product loop stopped the rest of the document for that pass, so the field that reads the captured value was never rendered, and on the next pass the exhausted loop overwrote the value with an empty string. The captured value is now kept and carried between the passes of a chunked export, so a footer rendered only in the final pass still sees it, while a capture inside a{% for %}still recalculates per row. A capture interrupted part-way — by the export's time limit or by Stop — no longer publishes the half-built value it had accumulated, in a header, in an{% if %}/{% else %}branch or inside another capture: the field stays empty for the rest of that export rather than shipping a plausible-looking but truncated value. Very large captured values (over 64 KB) still reach the feed file in the pass that produced them, they are just not carried across passes. An export already in progress keeps running across the update. - The exported product count no longer goes blank on a store view that is not in English. The export runs in the store view's language and the count was looked up by the export step's translated label, so on a Spanish or Romanian store view — 42 of the 45 shipped locales translate the word — the Count column in the Feeds grid, the status bar and the generation panel all showed nothing, and a spurious Valid 0 appeared beside a green success. Verified on a store view in Spanish: a 346-product feed now reports 346. The lookup also keeps working when another extension plugs into one of the export steps.
Sep 3
1.15.7
Sep 3
Fixed
- A filter on Final Price is no longer ignored. With Enable fast mode filtering on — which it is by default on every feed — a condition such as Final Price is greater than 50 was silently dropped: the rule matched the whole catalog, so the feed shipped every product instead of the selection you asked for, while the same rule with fast mode switched off filtered correctly. Final Price is now taken from Magento's price index for the feed's store and website, and bundle, configurable and grouped products are compared against the same price the slower mode uses, so both modes now produce the same feed.
- Filters left with an empty value now do what they say in fast mode. Three operators built no usable condition when their value was blank, so instead of filtering they let every product through: is not with the value left empty — the "is not empty" filter — kept products that have a value and products that have none, the exact opposite of what it asks for; is not one of with nothing selected did the same; and does not contain with an empty value, which excludes every product, excluded none. All three now give the same result as they do with Enable fast mode filtering turned off.
Sep 2
1.15.6
Sep 2
New
See at a glance which feeds are switched on
The Feeds grid has a new Enabled column with a Yes/No filter beside it, so the list can be narrowed to just the feeds that are active or just the ones that are turned off.
Improved
-
⚠️ Feed generation can no longer be started from the storefront. The public address
mst_feed/export/executeran a complete export for anyone who knew it — no admin login and no permission check — and it could also be used to reset the progress of an export that was already running, or to have arbitrary code echoed back to a visitor's browser. That address, and the two controllers behind it (Mirasvit\Feed\Controller\ExportandMirasvit\Feed\Controller\Export\Execute), are gone; it now answers with a 404. Generation runs only through the admin — the Generate button, the feed's own schedule, orbin/magento mirasvit:feed:exporton the command line — and every one of those enforces the admin session and the Feeds permission. If anything on your side fetched the old storefront address to trigger a feed (a monitoring check, an external scheduler, a cron entry callingwget/curl), switch it to the command line. -
⚠️ The long-dead
typecolumn is removed from themst_feed_ruletable bysetup:upgrade. Nothing in the extension has written to it since 2022; on stores installed after that it never existed, so the upgrade is a no-op there. -
⚠️ Three unused classes are removed:
Export\Liquid\BlankFileSystem,Model\Config\Source\ArchiveSource, andModel\Feed\Copier, which had been marked deprecated — useMirasvit\Feed\Api\FeedRepositoryInterface::duplicate(), which the web API already exposes directly. -
⚠️ Two admin pages that nothing in the extension ever opened are removed: the feed history grid (
Controller\Adminhtml\Feed\HistoryGrid), which had been failing with a server error on every request since the block behind it was deleted in 2023, and the "new custom feed" action (Controller\Adminhtml\Feed\NewCustom), which no button or menu item ever pointed at. Nothing you use in the admin changes; both addresses now simply answer with a 404 instead of a broken page. - The extension runs on PHP 7.1 and 7.2 again. A number of places had picked up functions and syntax that only exist in newer PHP — FTP and SFTP delivery, product URL resolution, feed and template logo uploads, XML feed validation, the AI column filler, template export, the file-cleanup task and the HTML-content admin fields — each of which failed outright with a fatal error on an older store. They work on every supported PHP version now.
Fixed
-
Feed generation finishes again on stores that keep media on remote storage (Amazon S3 and compatible). The export writes a small progress file after roughly every product, and that file was being uploaded to the bucket each time — several seconds per product, so a generation started from the admin or by cron on a large catalog never realistically completed, while the same feed run from the command line finished in minutes. The progress file is now kept on the local disk (
var/mst_feed/tmp) alongside the export's own scratch file, so admin and cron generation runs at full speed. - A feed built from the bundled ChatGPT template is now accepted by OpenAI. Nine of its columns did not match what OpenAI's Commerce ingestion expects, so products came through without the flags that make them searchable and buyable, and OpenAI reported the feed as incomplete.
- Feed screens no longer answer with "Something went wrong" after an update. A progress file left behind by an older version — or one that had been truncated or garbled — could not be read back, and every admin action that touched it (opening a feed, generating, resetting) failed with that message and no way out other than deleting the file by hand. An unreadable or outdated progress file is now treated as "no progress recorded" and generation simply starts from the beginning.
-
The scheduled clean-up of old feed files no longer deletes files it should keep. On a store with no feeds configured it removed every feed file in
pub/media/feed/— which, where several environments share one remote storage bucket (S3 / MinIO), meant a staging or beta store with no feeds wiping production's feed files. With no feeds there is now nothing to clean up and nothing is removed; where feeds do exist, orphaned files are still tidied away as before. - Filters using is not one of or does not contain no longer drop products whose attribute has never been set. A rule such as Color does not contain "red" silently left out every product with an empty Color, even though the rule says nothing about requiring a value; those products are now exported, as the rule intends. This completes the same correction made for does not equal in 1.15.5.
-
A filter that lists several values no longer ignores the value
0. Where the option you picked is stored as0— Out of Stock in Quantity and Stock Status, the NOT LOGGED IN customer group, the default store scope, or any attribute option that happens to carry id0— that entry was thrown away while the list was being read, so the rule matched nothing and the feed came out empty or short. All selected values are now kept. -
Creating or saving a product filter no longer fails on stores upgraded from an older version. The attempt ended with the database error Column 'type' cannot be null, and the filter was not saved; stores installed more recently were never affected. Run
setup:upgradeafter updating and filters save normally again. - The Google Merchant Center setup guide link, shown in the error message when an upload fails because your Google Cloud project is not registered with your Merchant Center account, pointed at a manual page that no longer exists and returned a "page not found". It now opens the current page.
August 2026
Aug 27
1.15.5
Aug 27
Improved
-
A filter that fails on one product's value no longer stops the whole export. Whatever the reason — a value of an unexpected type, a division that cannot be done — that single value is now exported unfiltered, the product still ships, and the rest of the feed is unaffected. Each dropped filter is written to
var/log/mirasvit/feed.logwith the filter's name and the reason, so a filter that is failing on every row can be found instead of quietly producing a wrong feed. - A feed configured with an export step that is not a real step now fails immediately with a message naming it, instead of running part-way through generation and stopping with an unrelated error.
Fixed
- A does not equal filter no longer drops products whose attribute has never been set. A rule such as Meta Title is not "EXCLUDE-ME" kept only products that had some other value in that field and silently left out every product where the field was empty, even though the rule says nothing about requiring a value. Such products are now exported, alongside the ones with a different value.
- Feeds on a store with several store views no longer export each other's products. The intermediate list of products matching a Filter is cached while a feed generates, and that cache ignored which store view it had been built for: generating the same filter for a second store view wiped and replaced the first one's list, so a feed could pick up products that belong to another store view, and two feeds generating at the same time could corrupt each other's results. Each store view now keeps its own cached list, and clearing one leaves the others intact.
-
A template calculation that cannot be carried out on some products no longer kills the entire feed. With
{{ price | divided_by: pack_qty }}in a column, a single product whosepack_qtyis empty or not a number aborted generation outright and produced no file at all. Dividing by an empty or zero value now leaves the value as it was, and a modulo by such a value returns 0, so the export finishes. -
The
secure,unsecureand media-URL filters no longer export the literal wordArraywhen applied to a multi-value attribute — and no longer behave differently depending on whether the store runs in developer or production mode. Every value in the attribute now gets the URL rewrite and they are exported as a comma-separated list.
Aug 26
1.15.4
Aug 26
New
The filter preview opens straight away, whatever the size of your catalog
Preview Products on a Filter used to load every matching product into memory and walk the whole catalog before it drew a single row, so on a 20,000-product store the first page took 12–19 seconds, and on catalogs of 90,000 and up it built a query several megabytes long and could run out of memory outright. The preview now works through the catalog in chunks and stops the moment the page you asked for is full: the same three rules measured 19.4s, 12.8s and 15.8s now come back in 0.3s, 0.03s and 0.03s. Memory no longer grows with the size of the catalog, only with the size of the page you are looking at.
New
Paging through a preview stays fast to the last page
Turning to a deep page used to mean walking past every product before it, so on a rule matching 18,138 products page 1 took 0.4s and page 900 took 15.9s — and because the grid remembers the page you were on, one stray click deep into the pager left you waiting on every later visit too. Each page now remembers where the next one starts, so page 900 costs the same as page 2. A first jump far into the pager is still slow once, and every page up to it is instant afterwards.
New
The exact number of matching products, counted in the background
The count shown next to the grid is now an upper bound to begin with, so the rows appear immediately, and the precise figure is fetched behind the scenes and swapped in when it is ready. While it is being counted the number reads around 20000 (counting…) with a spinner beside it, so a figure that is about to change never looks like a settled one. The exact count is then reused for the rest of your visit — paging around the same rule shows it with no further waiting — and is recalculated only when you change a column filter, the keyword search or the page size, reload the page, or press Preview Products again, which is an explicit ask for a fresh answer. Both new labels are translated into all shipped locales.
Improved
-
The admin no longer freezes while a preview count is running. PHP holds an exclusive lock on your session for the duration of a request, so a count that takes minutes — a rule built from computed conditions such as Image 2–5,
Is SalableorFinal Pricestill does — used to queue every other admin request behind it, including turning the very page you were counting. Measured on the QA host, turning to page 2 during a count went from 201 seconds to 1.2 seconds. The count itself is no faster; it simply happens in the background instead of stopping you from working.
Fixed
- The filter preview no longer dies on a rule that uses an Image 2–5 or an MSI (Multi-Source Inventory) stock condition. Such a rule produced a server error and left the preview grid stuck on "loading" forever, with no message to explain it. Rules built from these conditions now preview normally.
- A filter using an Any aggregator together with a condition that cannot be expressed in SQL — quantity, salable status, final price, an image — no longer previews an empty or too-short list. The preview quietly narrowed the candidate set on the SQL condition alone and hid products the real export includes; it now checks every product the same way the export does.
-
The preview no longer promises products your feed will not actually contain. For a handful of conditions —
is_in_stock,is_in_stock_inventory,image,small_image,thumbnail— the shortcut the preview took asked a slightly different question than the export does, so a stale stock index was enough to make the two disagree (2046 previewed against 2045 exported). Those conditions are now always checked the way the export checks them, and the exported file itself is unchanged. -
A filter that uses a custom attribute whose code begins with
stock(for examplestock_level) alongside a stock condition no longer fails with an "Unknown column" database error. - Jumping to the last page of a preview no longer reported a nonsense total — "18 records found" for a rule matching 18,138 — and no longer bounced the pager back to page one.
- Returning to a preview page you had already looked at no longer put the rough upper bound back on screen next to a pager that still showed the exact number of pages.
- A field value containing the feed's own column delimiter no longer shifts every following column on that row. In a format that uses no quoting — a TSV feed, most commonly — a tab inside a product's HTML description was read as an extra column separator; such characters are now replaced with a space. Quoted formats are unaffected.
-
An XML feed whose template contains an empty element — written as
<g:brand/>or<g:brand></g:brand>— no longer fails to generate. Pressing Generate on such a feed stopped with the generic "a technical problem occurred" message and produced no file at all, on every feed that carried one. The empty element now reaches quality-control validation as an empty value, so a required-field rule reports it as missing, exactly as intended, and the export completes. - The feed edit page no longer writes PHP deprecation notices to the error log. On PHP 8 the Google Merchant Center notice shown on that page was rendered without an internal name, which other extensions that watch block rendering — Adobe Commerce price permissions among them — could not handle; every visit to the page added noise to the log. All feed admin blocks of this kind are now named, so the notices are gone.
Aug 25
1.15.3
Aug 25
Fixed
- Product feed exports no longer fail with a database timeout when products are being edited at the same time.
- Large product feeds now generate far faster and no longer stall part-way through.
- Feeds that filter products by a store-view-specific attribute value now generate correctly and quickly.
- A feed export that fails to generate now ends with an error instead of appearing to finish successfully.
Aug 12
1.15.2
Aug 12
New
JSONL
A new feed format for data pipelines — pick JSONL* as the feed type and every product is exported as one JSON object per line, instead of a CSV row or an XML node. You build it in the same column editor you already use for CSV: each column's header becomes the key, and its value comes from an attribute or a pattern exactly as before. Values are escaped as valid JSON, so a quote or a line break in a description can no longer break the line. A column set to All Attributes* emits every attribute the product has, keyed by the attribute's store label. This is the format most warehouses and ingestion tools (BigQuery, Snowflake, marketplace bulk APIs) expect, and unlike a single large JSON file it can be read line by line, so a partner never has to load the whole catalog into memory to process it.
New
Compress the generated file (gzip)
A Compress output (gzip) switch on the feed's General tab, available for CSV, TXT and JSONL feeds. The finished file is packed and published as, for example,
products.csv.gz, which for a typical catalog is several times smaller — faster to upload, cheaper to transfer, and accepted directly by most channels and data pipelines. Compression is streamed, so turning it on does not increase the memory a large export needs. Quality-control validation still checks the real published file: the archive is unpacked before the rules run, including on stores that keep media on remote storage such as AWS S3. An export that produced no products yields a valid empty archive rather than an unreadable zero-byte file. Note: enabling this changes the feed's filename and therefore its URL — update anything that fetches the previous address.
Improved
-
⚠️ The feeds table gains an
is_compressedcolumn, added automatically bysetup:upgrade.
Aug 11
1.15.1
Aug 11
New
Real numbers, booleans and nulls in the JSON output of an XML feed
Until now every value in the generated
.json arrived as a string, a field with one nested element became a single object where two made a list, and an empty value simply disappeared. A partner asking for a price as a number or a stock flag as true/false could not be served by any template. You now say what a value is where you write it, the same way an XML schema does: mark the element xsi:type="xs:decimal", xs:integer or xs:boolean and it is converted, mark it xsi:nil="true" and it comes out as null, mark it xsi:type="array" and it is always a list even when the product has only one of them. Nothing is guessed from the value itself, so an SKU of 0012333 keeps its leading zeros and a text attribute reading "true" stays text. A value that does not match the type you declared is left as a string rather than turned into 0 or false, so a typo in a template cannot silently corrupt a feed. Feeds that declare nothing produce exactly the same JSON as before.
New
JSON tab in the feed preview
With Generate JSON enabled, the preview now shows the JSON alongside the XML, so the output can be checked while the template is being written instead of after a full export. If the JSON cannot be produced, the preview shows why, on the same screen where the template is fixed.
Improved
-
A template whose output is a series of top-level elements rather than one enclosing element is now converted to JSON as well — previously the
.jsonfor such a feed could not be produced at all. -
Templates that use prefixed tags such as
<g:id>without declaring the prefix on the root — which is what shopping channels expect — no longer produce parser warnings during export.
Fixed
-
When the generated XML was broken (a truncated file, unbalanced tags, an empty result), the export finished quietly and left the previous, now stale
.jsonpublished next to the new.xml. The export now stops with a message naming the tag and the line in your template output that caused it. -
A value declared as a decimal ships in its shortest form — a price formatted as
9999.00becomes9999— while a genuine fraction such as34.50keeps it, and a number too large for the platform's integer range stays text instead of being replaced by a wrong one. - ⚠️ Upgrading from an older version could stop with a fatal error when a stored feed validation schema was not parseable on its own; such records are now skipped and the upgrade completes.
Aug 10
1.15.0
Aug 10
New
AI-assisted feed optimization
Your catalog was written for your product pages; shopping channels want something else. That gap is why Merchant Center disapproves items, why variants collapse into one listing, and why products miss the searches they should win. Point an AI profile at a field and the extension fills what is missing:
New
Two new console commands, for stores that automate their feed pipeline:
Improved
- AWS S3 / remote media storage support — Feeds now generate, validate, and display correctly on stores that keep media on a remote backend such as AWS S3. Previously the feed logo was reported as missing, feed generation could fail outright, the public feed URL pointed at a private bucket path that browsers couldn't open, and quality-control validation of the generated file failed. Now logos are detected on the remote, the feed is built locally and only the finished file is stored remotely, the feed URL is a proper browsable media URL, and validation reads the file through the storage backend so it works even on private buckets.
- The Advanced Product Feeds admin menu no longer lists every feed you have created. On a store with a few dozen feeds the menu grew long enough to push the section links off the screen; the Feeds grid reaches any one of them in a click, with the search and filters the menu cannot offer.
- Button labels across the extension's admin screens now read in Title Case, and every button that creates something is phrased the same way — Add New Feed, Add New Template, Add New Filter, Add New Profile, Add New Attribute, Add New Category Mapping, Add New Variable. Previously these six differed from one another, and labels such as Clear values or Test connection were cased differently again. Field and column labels are unchanged.
Fixed
-
Nine categories in the shipped Google product taxonomy had corrupted characters (for example
Piñatasinstead ofPiñatas,Sauté Pansinstead ofSauté Pans). They appeared mis-spelled in the Category Mapping autocomplete and could not be selected reliably; the taxonomy file now uses the correct encoding. - The Feed Templates grid now honours the admin role restriction that guards the page it lives on. The grid's own data and export routes were not covered by that check, so an admin role without access to the feed section could still read or export the list by calling them directly.
- The Delete button was missing from the Filters form, so a filter could only be deleted from the grid. Its Save button also offered no Save & Close, unlike every other form in the extension — the form now carries the same split Save, both while creating a filter and while editing one.
July 2026
Jul 28
1.14.9
Jul 28
Fixed
-
The Test Connection button no longer uploads anything to your FTP/SFTP destination. It used to place a
deliverer.txtfile there — actually a copy of one of the module's own PHP files — which exposed source code and, on stores whose remote folder is watched by a feed consumer (such as OpenAI Ads Manager), was picked up and ingested as a bogus feed. The test now only verifies that the server is reachable, the credentials work, and the destination path exists, leaving the folder untouched. Failed tests also report the reason more clearly, distinguishing a wrong SFTP login from an invalid SFTP path. - CSV and tab-delimited feeds no longer lose the last row's empty trailing columns. If the final product in the feed had no value for the last few columns, those columns were trimmed away, so the closing row had fewer columns than the header — and marketplaces that read values by column position misread or rejected that product. Every row now has the full set of columns.
-
Feed generation no longer fails for products with an empty list field. When a template used the
firstorlastfilter on something a product had no values for (for example a product with no gallery images), the export aborted with a fatal error; such fields now simply come out empty and the feed generates to the end.
Jul 23
1.14.8
Jul 23
Fixed
-
Testing an FTP/SFTP feed connection no longer leaves a leftover file behind. The Test Connection button used to upload a
deliverer.txtfile to the destination folder and never remove it; it now writes a temporary file only to confirm write access and deletes it once the test passes, so the target directory stays clean.
Jul 21
1.14.7
Jul 21
Fixed
- Feeds now generate on stores hosted on network-mounted filesystems (NFS, AWS EFS). On these hosts the exclusive file lock taken during export could fail with a cryptic "An error occurred during '' fileLock execution." error, which aborted every feed generation from both the admin and cron/CLI. The lock now degrades gracefully on such filesystems so feeds generate normally, while a genuine lock conflict on a regular filesystem is still detected as before.
Jul 21
1.14.6
Jul 21
Improved
- Redesigned feed edit page — The feed's main tab now opens with a status bar that shows everything at a glance: current status, how many products are in the feed, the feed URL with a one-click copy button, when it was last generated and how long that took, any quality-control issues (as clickable badges that open the validation report), and when it was last validated. The form fields are grouped into clean collapsible sections, active/JSON options are shown as toggles, and the statistics table is easier to read — so you can see a feed's health without hunting through the page.
-
Export problems that used to fail silently are now recorded to
var/log/mirasvit/feed.log— for example when tier prices, a category-mapping file, a Google Merchant service-account key, or a click-tracking record can't be read. The feed still generates as before, but you now have a log entry to explain any missing data.
Fixed
- Opening the New Feed / Custom Feed page no longer crashes with a blank form — creating a feed from scratch failed to render on this version, and now works normally.
- Feeds with quality-control issues no longer break the edit page. The validation badges triggered a JavaScript error ("validateFeed is not defined") that could stop the page from loading; the badges now open the validation report correctly.
- Duplicating a feed now starts clean. A copied feed inherited the original's generated file link and "Last Validated" date even though it had never been generated; a duplicate now shows no feed URL and no validation date until you generate it.
- Restricting an admin role's access to the feed configuration section (Stores → Settings → Configuration → Advanced Product Feeds) now works. The permission for that section was never registered, so the setting had no effect; it is now enforced correctly.
-
⚠️ This version now requires Mirasvit Core 1.7.15 or newer — run
composer updateandbin/magento setup:upgradeafter upgrading.
Jul 9
1.14.5
Jul 9
Fixed
- Multiselect attributes with more than one selected option now export their actual labels instead of the literal word "Array". Products whose multiselect attribute (e.g. a "Features" or "Colors" field) had two or more values selected exported the placeholder text "Array" and, under strict mode, could raise a warning; the labels are now joined with commas and exported correctly.
June 2026
Jun 30
1.14.4
Jun 30
Fixed
-
Feed templates that use an
{% elsif %}branch no longer break feed generation. Exporting a feed whose template reached an{% elsif %}condition failed with a fatal error and aborted the export; such templates now generate correctly. - Adding a new filter rule no longer throws an error. Creating or opening a filter rule before any conditions had been set could fail with a fatal error, blocking you from setting up product filters; empty conditions are now handled correctly.
Jun 24
1.14.3
Jun 24
Fixed
- Feeds that filter by category in fast mode now generate far faster on large catalogs. The "Category is one of / is not one of" filter no longer forces a full table scan, which could slow cron exports to a crawl (roughly one product every several seconds); it now uses an indexed lookup. The fix also corrects "Category is not one of" results — products that belonged to no category, or that belonged to both a listed and an excluded category, were previously dropped or could leak into the feed, and are now matched correctly.
-
⚠️ Re-importing an exported feed template no longer corrupts its saved settings — a template's stored configuration now survives an export/import round-trip intact. This fix is delivered through Mirasvit Core; this version now requires module-core 1.7.14 or newer, so run
composer updateandbin/magento setup:upgradeafter upgrading.
Jun 16
1.14.2
Jun 16
New
Google Shopping Promotions feed
A new built-in "Google Shopping Promotions" template lets you publish your active Cart Price Rules (coupons) to Google Merchant Center, so shoppers see offers such as percentage discounts, fixed-amount discounts, free shipping, and free gifts alongside your products. Create a feed from the template, set its Marketplace to Google Merchant Center, and submit it like any other GMC feed.
Improved
- When a Google Merchant Center upload fails because your Google Cloud project isn't registered with your Merchant Center account, the feed history now shows a clear, actionable message — telling you exactly where to register (Merchant Center → Settings → Developer registration), to retry in about 5 minutes, and linking to both Google's registration guide and our setup manual — instead of a raw API error.
Jun 4
1.14.1
Jun 4
Fixed
- Feed export no longer runs out of memory on large catalogs when generated from the command line or cron. Memory now stays flat regardless of catalog size.
Jun 3
1.14.0
Jun 3
New
Stop a running feed export
You can now interrupt an export that is already in progress instead of waiting for it to finish. A Stop Export button appears in the generation progress dialog, and there is a new CLI command for the same purpose:
bin/magento mirasvit:feed:stop --id=<feed_id> for one feed or bin/magento mirasvit:feed:stop --all for every running export. The export stops gracefully between steps, records a "stopped by user" entry in the feed's history, and leaves the previously generated feed file intact so the public feed URL keeps working. Works for exports started from the admin, the command line, or cron.
New
Marketplace field for feeds and templates
Feeds and templates now have a Marketplace field (currently None or Google Merchant Center). The Google Merchant API section only appears on feeds set to Google Merchant Center, so the form is cleaner for feeds that don't use it, and the module no longer risks uploading a non-Google feed to Google Merchant Center by accident. Existing feeds are detected automatically on upgrade — any feed whose name contains "google" or that already had Google Merchant upload enabled is set to Google Merchant Center; the bundled Google Shopping templates are pre-set as well. ⚠️ Adds a
marketplace column to the mst_feed_feed and mst_feed_template tables — run bin/magento setup:upgrade after upgrading.
Fixed
-
Feed REST API endpoints (
GET/POST/PUTon/V1/feed/feeds) no longer fail with HTTP 500. The Google Merchant fields added in 1.13.0 were missing the metadata Magento needs to serialize the response, which broke every feed API call that returned feed data.
May 2026
May 27
1.13.4
May 27
Improved
- Shortened the Google Merchant API field notices on the feed edit form to a single descriptive sentence each; operational detail moved to the manual.
Fixed
-
Feed export no longer aborts with
SQLSTATE[23000]duplicate-key onmst_feed_rule_productwhen stock / status / visibility changes between AJAX polls. The Filtration step now uses keyset pagination and the admin path holds a per-feed lock. -
Concurrent admin and CLI generation of the same feed no longer produces a corrupted XML file with interleaved
<?xml ?>declarations. The admin and CLI export paths now share a single per-feed lock so they are mutually exclusive. - Generate dialog spinner no longer hangs for the duration of an export chunk before the wizard renders — the admin PHP session lock is now released up-front and re-released each iteration, so progress polls run in parallel with the export.
-
History tab keyword search now narrows the grid; a missing FULLTEXT index made it return every row regardless of the query. ⚠️ Run
bin/magento setup:upgradeafter upgrading. - History grid with no keyword matches now shows "0 records found" instead of a blank count.
- Feed and Template grid date range filters no longer reset the year to 2005 after a date is picked.
- Filtering the Feed grid by ID range or Created At no longer fails with an "ambiguous column" SQL error.
- Unchecking every filter on a feed and saving now actually clears the filter set instead of preserving the previously-saved one.
- Centered the generation steps wizard inside the export modal.
- Removed the non-functional "Reset" button from the filter edit page.
May 27
1.13.3
May 27
Fixed
- The bundled "Base Product Filter" rule is now shipped as JSON. Fresh installs no longer log "Unable to unserialize data" when opening a feed that uses it.
-
Added a one-time data patch that converts any legacy PHP-serialized feed rule conditions, dynamic attribute conditions, feed and template formats, and category mappings to JSON on
setup:upgrade. Stores already on JSON are unaffected.
May 26
1.13.2
May 26
Fixed
-
Removed
unserialize()fallback inMirasvit\Feed\Service\Serialize. The service is now JSON-only and marked@deprecatedin favour of\Magento\Framework\Serialize\Serializer\Json.
May 22
1.13.1
May 22
New
Submit non-product feeds to Google Merchant Center
In addition to the existing Products feed, you can now submit Supplemental, Local Inventory, Regional Inventory, Promotion, Product Review, and Merchant Review feeds to GMC. Pick the type in the new "Content Type" dropdown on the feed's Google Merchant Center section — pre-filled automatically when you create a feed from a built-in Google template (e.g. Google Shopping → Products, Google Shopping Review → Product Reviews). ⚠️ Run
bin/magento setup:upgrade after upgrading. On existing installs, also run the admin Import Templates action to pick up the new pre-fill values for the bundled Google templates.
Improved
-
⚠️ The
google/shopping-merchant-datasourcesSDK is now an optional dependency instead of a hard requirement, so the module installs again on PHP 7.4 / Magento 2.3.7. To use Google Merchant Center upload, install the SDK separately withcomposer require google/shopping-merchant-datasources:^1.2(PHP 8.1+ required). When the SDK is missing, the Google Merchant Center section in admin shows an install banner with the exact command, and cron generation skips the upload step instead of failing.
Fixed
-
Fixed
NOT_FOUNDerrors immediately after creating a new GMC data source — the module now retries while Google's API replicas catch up.
May 12
1.13.0
May 12
New
Google Merchant Center direct integration
Submit feeds to Google Merchant Center via the Merchant API v1 without manually uploading files. Configure your Merchant ID and service account key (JSON file upload) once under Stores → Configuration → Mirasvit Feed → Google Merchant Center, then enable GMC on each feed's edit page. Per-feed settings include target countries, content language, feed label, fetch frequency (how often GMC re-fetches on its own schedule), and upload trigger (automatically after each generation, or manually via a Submit button on the feed edit page). ⚠️ Run
bin/magento setup:upgrade after upgrading — new columns added to the mst_feed_feed table (gmc_enabled, gmc_feed_label, gmc_target_countries, gmc_language, gmc_data_source_name, gmc_upload_trigger, gmc_fetch_frequency, gmc_uploaded_at).
May 5
1.12.3
May 5
New
Added built-in ChatGPT feed template (CSV) for OpenAI's Commerce platform, pre-configured with all required fields, and seller/policy fields.
April 2026
Apr 23
1.12.2
Apr 23
Fixed
- Fixed blank "Add New Feed" page caused by Prototype.js.
-
Fixed
stock_statusattribute returning localized values on non-English storefronts — Google Shopping requires "in stock" / "out of stock" in English, so feeds were failing platform validation on stores running in other languages. - Fixed a severe performance regression introduced in 1.12.0 where feeds with fast mode filters on product attributes could take significantly longer to generate than expected.
- Fixed an error when saving a feed whose template had been deleted — the missing template is now skipped and surfaced as an admin notice instead of crashing the save.
Apr 13
1.12.1
Apr 13
Fixed
-
Fixed fatal TypeError after running
bin/magento mirasvit:feed:deliveryandbin/magento mirasvit:feed:migrate- both commands declared anintreturn type but fell through without returning on the success path.
March 2026
Mar 30
1.12.0
Mar 30
New
REST API for feed management
All major feed objects (feeds, templates, filter rules, dynamic attributes, category mappings, and variables) are now accessible via Magento REST API. You can create, update, delete, generate, deliver, and validate feeds programmatically. Feed generation runs asynchronously via a queue — trigger it and poll the queue endpoint for status. ⚠️ New database table
mst_feed_generation_queue is created on upgrade.
New
split modifier in template loopsUse
| split: "," inside {% for %} loops to iterate over comma-separated (or any-delimiter-separated) attribute values directly in feed templates, without needing a custom dynamic attribute.
New
Admin interface translated into 40+ languages
Improved
- Compatible with Magento 2.4.9 — CLI commands updated to meet the new PHP return type requirements introduced in Magento 2.4.9.
Fixed
- Fixed feed filter conditions ignoring the store scope for product attributes when fast mode is enabled — products could be incorrectly included or excluded from the feed.
- Fixed category attributes (e.g. category name, URL) returning values from the default store view instead of the store view configured for the feed.
- FTP delivery failures now properly throw an error — previously a failed FTP upload could be silently ignored; now it surfaces as an error so you can act on it.
February 2026
Feb 6
1.11.11
Feb 6
New
Added compatibility with MageWorx Advanced Product Options Suite for accurate min_price/max_price calculation
January 2026
Jan 27
1.11.10
Jan 27
Fixed
- Fixed click reporting error when accessing non-existent feeds
Jan 23
1.11.9
Jan 23
Fixed
- Fixed the display of the generation modal on Hyvä-based storefronts
Jan 14
1.11.8
Jan 14
Fixed
- Fixed the cleanup cron job incorrectly removing non-feed files from pub/media/feed
Jan 2
1.11.7
Jan 2
New
Added
sort and rsort modifiers for sorting array values in feed templatesDecember 2025
Dec 4
1.11.6
Dec 4
Fixed
- Fixed deprecated functionality error on feed pages in Magento Commerce (EE)
Dec 3
1.11.5
Dec 3
Fixed
- Fixed missing conditions for weight and price attributes in the dynamic attribute form
November 2025
Nov 27
1.11.4
Nov 27
Fixed
- Fixed the "Save and Continue Edit" button remaining disabled after saving a feed