We've completed initial testing on our OUI/MMUI Store Framework Exporter.
There's 4 unique modules in here all for 4.x compiled:
1. MMUI Framework Exporter**
2. OUI Framework Exporter*
Both of these work in the same way, install them, go to Stores - StoreName - Utilities - Export and you'll see a new Export Framework option. Then go to a PR6 or MMUI PR7 and install the Framework.
3. Catalog Exporter
4. Order Exporter
Both of them create XML exports and you use the XML importer in 5.5 to upload the file and it imports.
It's important to note that specifically if you're using OUI, this Framework exporter does NOT attempt to parse the OUI tokens. This tool is not designed to make a one click 4.x OUI export/import into 5.5 that gets you all the way to a live store, but instead the goal is to get you 70 - 90% of the way there and save you time (and therefore money) in completing the final steps.
You'll need to look at your Dev site once you've installed the Framework and go look for all the un-rendered OUI tokens and replace them with something meaningful in the 5.5 universe.
These are the known issues we're seeing regarding the OpenUI export module:
1) Engine versions before 5.03 will always fail, since they do not implement the "tar_create" function, which is required to generate the framework package file (no workaround other than an engine upgrade).
2) Engine versions before 5.07 will intermittently send corrupted email attachments due to an engine bug, however, the valid package file can still be retrieved from the data directory on the server.
3) Module versions 4.2404 and 4.2405 have a bug related to how "../" relative images are parsed out of some page templates, which causes any of these images to fail to be copied and their references are reduced to . These versions also suffer from a susceptibility to crash when parsing certain types of broken HTML for image and CSS tags.
Release Notes for export-openui-layout5.mvc:
Initial version 4.2404
- Fixed a bug where image destination path generation was causing some images
to be listed in the control file as /mm5/, or whatever the user defined target
image directory was set to.
- Fixed a bug related to how "../" relative images are parsed out of some page
templates, which causes any of these images to fail to be copied and their
references are reduced to . These versions also suffer from a
susceptibility to crash when parsing certain types of broken HTML for image and
- Fixed a bug that allowed non-existent CSS files that were referenced in the
"CSS Styles" input field to be included in the control file's image list, thus
causing the framework install to fail.
- Corrected false positive in some cases when checking for a file with zero
- Corrected an issue where images could sometimes be displayed in the list of CSS files
** Update to export-mmui-layout5.mvc
-Fixed bugs BUG#5761 and BUG#5759 where the external file parsing functions
exhibited the same issues as the OpenUI layout export module, in which they
were replacing templates that did not reference any external files with empty
To add the modules:
1. unzip the zip file
2. Login to your Miva Merchant v4 admin interface
3. Expand Modules
4. Click on Add Module
5. Browse to the file on your local computer and click the upload button