MMUI to CSSUI

[ids]

How do you restart the MMUI to CSSUI migration wizard after a failed attempt at a conversion?

Secondary question which is more of a comment: Why doesn't the wizard take inventory of the needed dependencies before nixing the user interface.

Scott

[lesliekirk]

Good questions - all of my failures have been related to some sort of duplicate in the database. I've discovered that there are issues running the conversion when the site has Sebenza modules installed. In my cases, I have had to have Miva Support intervene and pretty much start over. They seem to have better luck with the conversion tool than I have had, but then again I can break pretty much anything.

[Bruce - PhosphorMedia]

They seem to have better luck with the conversion tool than I have had, but then again I can break pretty much anything.

True. We've always wanted to do a "even a caveman can do it" Ad replacing it with "Even Leslie can't break it" ad for our modules. :)

[hmendenhall]

Hello
I was wondering what errors you got when you ran the tool the 1st time so maybe I can give you some pointers on how to remedy those.
After the tool is ran and if you are presented with errors you have to restore the website and then you will be able to clear up those errors and run the tool again.

[ids]

I think the db tables might be in the process of being restored.

The error I received was that the CSSUI messages module was missing.

My next attempt after up loading that component module was to try again. I would guess it would fail -- it did. Then I applied the "default" MMUI framework. Kinda let me know that there was still data available. But another attempt gave me the error message implying I needed to restart.

Getting some insight for solving an issue prior to running the conversion will be helpful. Please tell us everything you already know about.

Thanks.

Scott

[hmendenhall]

If you got the CSSUI messages module is missing error. You would just need to add that module to your store. Attached is the cssui message mvc file. Let me know if you run into anymore error messages. If you do take a screenshot of the message and post it to this thread or create a ticket by submitting the information to [email protected]

[ids]

Thanks Happie. This confirms I guess that what I have already done while waiting for the restore of the dev site was the correct procedure. I'll let you know if it doesn't. Does that missing module message come up with the CSSUI Messages module consistently like there is a pattern? If this module is a pattern then may mean a different kind of problem.

Here's the general problem IMO. I don't do the conversion all the time. And I usually don't run into a problem. This particular issue will cost 1 week or more to get the back up restored to the dev site. Then I will need potentially go through this again if there is another hick-up. Obviously it will go smoother if I can get control of the back up but there will still be a time cost that my client doesn't want to have to pay me for. The ramification is illustrated in a time contrast. I can go from a short time period, maybe a few, 30 minutes for a clean store to run a successful conversion to a few weeks for a problematic conversion.

I (maybe I speak for many) would really love to know other types of potential issues I can check for since the wizard does not before I run the wizard. Please tell us everything you already know about these potential problems.

I haven't thought this through but here's a suggestion that might work. When there is a missing Miva module during the conversion, the module should be able to stream or download that missing Miva module.

Thanks,

Scott

[lesliekirk]

Scott - one thing I discovered is an issue with the Header and Footers in the Page Templates. They get lost in the conversion. You need to go in, un-assign the the CSSUI Headers & Footers item, then reassign them. Then you have to go back to the "live" site to get the content. Sometimes you have to go through and do the unassign / reassign to ALL of the Items for a Page. Losing the Header & Footer content is also a time drain.

So yes, everything that goes wrong in the dev site, will go wrong in the live site.

[ids]

Leslie,

Not sure what you mean by saying the local Page headers and footers get lost. Does that mean the data in the tables gets deleted? Might be more correct to say that data is being over-written when the conversion created the CSSUI version of the tables.

BTW: I think something similar happens when transporting frameworks even on a CSSUI site when moving a framework from a dev site to a live site. I've at least run into the global header and footer taking a leap into the electronic abyss.

Instead of the abyss, I am going to head into the weeds for a minute. These items are form the same component module. IMO, they are not really needed any longer. You can set up an item from the Content component module to do the same thing. I find I do that more and more. I don't remember using these PAGE entities recently. This is off the top of my head and may be incorrect; It may also be possible to rely more on the Readytheme module anyway for these type of page elements.

So now the question I have, do you know if Content items created in the MMUI store get 'lost" during the conversion?

And circling back to the original topic, do the Category headers/footers and Product headers/footers get lost? Hopefully, this data is not touched.

Scott

[lesliekirk]

Scott - I may not be technically describing this correctly but I discovered the error when trying to make tweaks to the Page Templates. Here is what was sent to me from support when I was trying to do a page update:

Here are some notes from the software developer

"Due to an error in the mmui to cssui conversion module the page templates for the Product attribute template, and product display layout items did not get regenerated correctly.

Unassigning and reassigning the items should resolve this issue."

So here's the thing (and it may only be with alternate page template layout - in this case for categories) - the content in the header and footer was in an MMUI field - MMUI Product/Category Header & Footer. The new layout is a CSSUI field - CSSUI Product/Category Header & Footer So when I un assign and reassign the Item, there is no content in it. Is the content still in the database? I don't know, I don't like to touch databases.


Another transporting framework issue - the ReadyTheme Navigation Sets get messed up. I'm finding the content of one set in another set where is doesn't belong.

Also, I find myself being reminded to make sure I have the latest version of the conversion tool. That's never an issue as I go an download a new one for each conversion I run just to be sure I do have it. It would be nice to get some sort of notice if an update is made.

[ids]

Definitely some interesting manifestations in the conversion tool.

"Unassigning and reassigning the items should resolve this issue." I am not sure if I can see this in the LSK, but this appears that it might be an indexing problem.

The note here describes Product page aspects. Is it just them or is it beyond such as the CTGY/SRCH pages, etc.

Scott

[lesliekirk]

I think I need to edit my post - I had it correct when I first mentioned - it's the hdft CSSUI Header & Footer item that is used in the Page Templates. I haven't come across an issue with the CSSUI Product/Category Header & Footer.