Announcement

Collapse
No announcement yet.

OUI/MMUI Store Framework Exporter Beta

Collapse
This is a sticky topic.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Rick Wilson
    started a topic OUI/MMUI Store Framework Exporter Beta

    OUI/MMUI Store Framework Exporter Beta

    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.

    *export-openui-layout5.mvc v4.2408

    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 <img src="">. 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

    4.2405
    - 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.

    4.2406
    - 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 <img src="">. These versions also suffer from a
    susceptibility to crash when parsing certain types of broken HTML for image and
    CSS tags.

    4.2407
    - 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.

    4.2408
    - Corrected false positive in some cases when checking for a file with zero
    length

    - Removed code that was pulling JavaScript src files, because of tracking code eval errors

    - Corrected an issue where images could sometimes be displayed in the list of CSS files

    ** Update to export-mmui-layout5.mvc

    v1.0002
    -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
    strings
    Attached Files
    Last edited by wsmith; 09-08-10, 08:43 AM.

  • lesliekirk
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Yup, deleting the store is definitely not an option here either, as I was just trying to grab the last bit of missing data before going live. The site is way beyond starting over.

    Leave a comment:


  • gsam
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    I placed a ticket on this and after 3 days I got a response...."You need to delete the store, and then before you re-add it click the settings tab and choose Miva Merchant look and feel. " I replied by saying that's not really an option. If nothing else can be done please overwrite my store with a backup.

    I'm still waiting on a response.

    Leave a comment:


  • lesliekirk
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    That's interesting - I just checked and sure enough there are 2 now. I'll pass that on to support since they are now looking at it.

    Leslie

    Leave a comment:


  • gsam
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    When you view a product or category do you now have 2 tabs labeled Header/Footer?

    I also used the XML provisioning to import the prod_ctgy_hdft.htm and I now have 2 Header/Footer tabs on every category and product.

    Leave a comment:


  • lesliekirk
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Okay I submitted a ticket. Everything seemed to go okay with the XML import of the .html file but when I went to look at the products them self, the data was not there. I have no idea where the data went to

    Leave a comment:


  • Jim McCormick
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Originally posted by lesliekirk View Post
    Hmmm, looking at the store in question and all I see is the "Export Catalog to Miva Merchant 5.x XML File" - I don't see a framework exporter. Maybe I need to (re)install the module?

    Leslie
    No, you just need to install the framework exporter.

    https://support.mivamerchant.com/sup...ework-exporter

    Leave a comment:


  • lesliekirk
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Hmmm, looking at the store in question and all I see is the "Export Catalog to Miva Merchant 5.x XML File" - I don't see a framework exporter. Maybe I need to (re)install the module?

    Leslie

    Leave a comment:


  • wsmith
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Leslie,

    If I remember correctly the header and footer information is stored within the framework export and not the catalog export. Run the framework export tool on the 4.x store to export the look and feel of the OUI store. Download that pkg (framework.pkg) to your desktop. Rename the 'framework_name'.pkg to 'framework_name'.tar.bz2 and use winzip or winrar to extract the files. You should now have a directory with the 'framework_name' called components. Go into that directory and try importing the hdft.html or prod_catgy_hdft file into the version 5 store ('x'.html files can then be imported via the Import Data from XML File).

    I haven't done this in a long time so I apologize if I've missed a step. Keep us posted and if you continue to have trouble, please open up a ticket with support. If you do open up a ticket with support please make sure to reference this post.

    Thanks,

    Wayne

    Leave a comment:


  • lesliekirk
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Bringing this one back to life. Looks like the MM4 store has the upgrade5_catalog module installed and was probably used to populate their MM5.5 store. Unfortunately, it looks like the OUI Header & Footer data did not transfer over. What would be the best course of action on this?

    Thanks!
    Leslie

    Leave a comment:


  • Eric
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Hi Miva,

    Is their a newer version of this openUI exporter tool it has been about a year since the last posted version of 4.2408?

    Thank You,

    Leave a comment:


  • wsmith
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Steve,

    Open up a ticket with support ([email protected]) and attach the files. In the subject please put ATTN: Engineering and include a link to this post and a brief description of the issue. Please also note what version of the export-openui-layout5.mvc the store is currently using.

    Wayne, if you need any server info like engine version, etc. let me know.
    David,

    Engine version right now might be good to know as the tools don't play well with some older versions.

    Thanks,

    Wayne

    Leave a comment:


  • ILoveHostasaurus
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Wayne, if you need any server info like engine version, etc. let me know.

    Leave a comment:


  • Advanz Design
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Hi Wayne,

    Thanks for the in depth response. Hostasaurus initially provided the export/import of the OUI framework so not all of the images are missing from the storefront, but pertain to missing some of the category tree images and most of the category title images. The physical images exist as they were all copied over entact, but oddly some of the image paths did not come through.

    After trying to export/import the data several times on a local test platform, I noticed that these missing images originated in the exported framework file (i.e. category_title.html and category_tree.htm files) so perhaps I stumbled upon a bug in the OUI layout exporter? If necessary, I can provide these files for your troubleshooting reference.

    For now, we'll have to continue on by manually inputting this missing data through the admin as the client can't afford to suspend this upgrade too much longer. If anyone knows of a faster work around to administrate this data please let me know.

    Best regards,

    Leave a comment:


  • wsmith
    replied
    Re: OUI/MMUI Store Framework Exporter Beta

    Steve,

    Applying the upgrade5.mvc (provide.xml) after using the newer tools is not required. You do want to make sure to export/import in the following order.

    1) upgrade5_catalog.mvc
    2) Apply framework* (export-mmui-layout5.mvc or export-openui-layout5.mvc).
    3) upgrade5_orders.mvc

    *Framework can only be applied to a store running Miva Merchant Look & Feel for the Store User Interface. Data can be extracted to be applied to a store running to either Store User Interface.

    The framework contains the category_tree and category_title information. If you did not apply an exported framework; this could be why the data is missing. You should be able to take a copy of the framework, rename the extension from .pkg to .tar.bz2 and extract the data with winrar or winzip. Look within the components directory once the data has been extracted. You can pick and choose which information you would like to re-import and import via the Import Data from XML File section.

    buttons.htm
    category_title.htm
    category_tree.htm
    colors.htm
    customerlink.htm
    fonts.htm
    hdft.htm
    XXXX_messages.htm
    navbar.htm
    prod_ctgy_hdft.htm
    product_display.htm
    product_list.htm

    Attached is a rough draft of instructions for the newer tools (export-mmui-layout5.mvc or export-openui-layout5.mvc, upgrade5_catalog.mvc, upgrade5_orders.mvc) and any feedback would be great.

    OUI/MMUI Store Framework Exporter Beta
    https://support.mivamerchant.com/sup...mid=57&nav=0,1

    Report any issues to Miva Merchant Support and provide specific steps to replicate.

    Thank you,

    Wayne
    Attached Files

    Leave a comment:

Working...
X

This website uses cookies to identify visitors, track visitors to our website, store login session information and to remember your user preferences. By continuing to use this site you agree to our use of cookies. Learn More.

This website uses cookies. By continuing to use this site you agree to our use of cookies. Learn More.

Accept