Search by

rocketweb / module-shopping-feed-migration-rocketweb

rocketweb-fed

Optional, explicit migration of Rocket Web feed configuration to Mage-OS Shopping Feed.

Package info

github.com/rocketweb/module-shopping-feed-migration-rocketweb

Type:magento2-module

pkg:composer/rocketweb/module-shopping-feed-migration-rocketweb

Statistics

Installs: 26

Dependents: 0

Suggesters: 1

Stars: 0

Open Issues: 0

v1.0.1 2026-11-09 20:26 UTC

This package is auto-updated.

Last update: 2026-11-09 20:29:16 UTC


README

An optional Magento module that copies Rocket Web Shopping Feeds configuration into MageOS_ShoppingFeed. Install it only on stores that are migrating. The main Shopping Feed module does not depend on this package.

Version 1.0.1 includes the reviewed security/correctness fixes after v1.0.0 and translations for the original and inverse 2.3.2 duplicate settings. See the release changes and 2.3.2 acceptance and upgrade order for tested source revisions, behavior differences, and remaining store checks.

The November checks exercise original-source migration with Magento 2.4.7/PHP 8.3 and Mage-OS 3.6/PHP 8.5 dependencies and disposable databases. Earlier full-store results keep their dated scope. Representative store and recipient acceptance remain required. Follow installation and upgrade to select the versioned package.

What it does

  • Imports one feed at a time with its store, type, settings, inherited defaults, and supported mappings.
  • Creates a disabled destination with microdata off and schedules/uploads held in an encrypted receipt.
  • Leaves source records intact; requires a reviewed preview and reference to an already completed backup.
  • Validates configuration, credentials, and current state before transactional writes.
  • Supports activation, unchanged-target rollback, missing-target recovery, and fresh import after rollback with encrypted history retained.
  • Records sanitized Admin/CLI operation outcomes through Magento's logger.

The package is rocketweb/module-shopping-feed-migration-rocketweb; the Magento module is RocketWeb_ShoppingFeedMigration. Both feed modules must share the installation and matching encryption key. Keep legacy modules enabled during setup:upgrade; disable individual feeds only when arranging cutover.

Documentation

The reviewable wiki source follows the main Mage-OS Shopping Feed documentation layout. Start at Home, or choose a procedure:

Task Guide
Check versions and boundaries Status and compatibility
Install or upgrade the importer Installation and upgrade
Migrate the first staging feed Quick start
Understand settings, tokens, and validation Preview and import
Compare original and migrated files Compare feed output
Enable delivery and switch recipient URLs Activation and cutover
Recover or retry an import Rollback and recovery
Diagnose failures Logs and troubleshooting
Look up commands and paths Commands and paths

Wiki publication is separate from source commits. See wiki maintenance for the page convention and publication process.

Evidence and development

The published v1.2.0 acceptance record starts with original Rocket Web feeds on a fresh Magento Open Source store before installing either new package. It includes sample files, a byte-identical four-row Generic example, and explicit Google, stock, MSI, URL, and weight comparisons. Copied configuration does not guarantee identical output.

The completed October 4 disposable-store matrix repeats Admin, permission/CSRF, native output, scope, FTP/SFTP, lifecycle, concurrency, and restore acceptance with the reviewed code. Five regression profiles pass 99 tests each, with no skips. Output verifiers pass 108 current-version and 421 minimum-version checks, with documented differences.

The October 4 review response records the security/correctness fixes, rejected recommendations, current test results, recovery checks, and concurrency evidence. The September acceptance retains the earlier authenticated Admin, transfer, lifecycle, scope, and backup-restoration evidence; its dated results remain historical; use the October 4 matrix for the current checkpoint.

Use verification for commands, legacy compatibility for opt-in original-package patches, and core integration for the separate main-module discovery notice. Current work and remaining release gates are recorded in the handoff.