Wombat Beta - Feedback

[Rick Wilson]

Re: Wombat Beta - Feedback

Diana,

You will not need to change gateways to run new transactions from Wombat.

At this time though if you want to run Voids and/or Refunds you'll need to use IMS or CHASE.

[Hostasaurus]

Order Fulfillment Modules emails

When setting an item's status under Order Processing to Backordered, the store sends an email immediately. If I try to resend the email by clicking on the Order Fulfillment Modules tab of the order, checking the Process box for Back Order Confirmation HTML Email, nothing is sent.

Is this expected, and if so, what's the purpose of the Order Fulfillment Modules tab? The Customer Order Confirmation HTML Email seems to be the only one that is send on demand from that tab.

[eMediaSales]

Re: Wombat Beta - Feedback

I have a client running wombat. Clicking on the Logout link doesn't log the client out entirely. Appears to be cookie related between the http and https based links not staying connected.

You're logged out on http, not logged out on https.

Recommendations?
James

[wcw]

Re: Wombat Beta - Feedback

Make sure the link is global:secure_sessionurl instead of global:sessionurl

[eMediaSales]

Re: Wombat Beta - Feedback

Make sure the link is global:secure_sessionurl instead of global:sessionurl

Confirmed. Miva dev team - possible bug?

[wcw]

Re: Wombat Beta - Feedback

Isn't that part of the new session management. I had routine where a person could remove items from their tool kit favorites/wish list on the ACED page. Instead of removing the item from the list, it sent them to the login screen because the session id was the wrong one for the page ACED.

[yovation]

Re: Wombat Beta - Feedback

Hello,

I am using this link but customers can't logout.

<a href="&mvt:global:secure_sessionurl;Action=LOGO&Screen=SFNT&Store_Code=&mvta:global:Store_Code;">Logout</a><br>

Any suggestions?
Thank you.
David

[benjamintr]

Re: Wombat Beta - Feedback

Hi... Sorry if this has been asked before but I'm not clear on it.

I'd like to to take an existing store and upgrade to the brand new version/CSS UI model when it's released. If I could get a head start on this with a beta version then all the better.

As I understand it, following the the standard patch/upgrade model won't accomplish this and I need to start "from scratch".

I have a development environment available to me.

Rick (or someone else), could you spell out the best steps to upgrade to the new version/CSS model but keep as much store data as possible?

I'm guessing it's something like this....

1) Create new version of store on Dev server.
2) Import all modules, products, categories, customers.
3) Apply my current look feel.

Then.... how do I get this over to my production environment. I'm assuming this needs to be deleted and started over too?

A step by step list would be extremely helpful for me and I'm sure for others too.

thanks!

[Rick Wilson]

Re: Wombat Beta - Feedback

I'd like to to take an existing store and upgrade to the brand new version/CSS UI model when it's released. If I could get a head start on this with a beta version then all the better.

I'm a little confused, so before I answer let me ask a couple questions.

1. Do you want to somehow keep your currently look and feel AND have CSSUI?

or

2. Do you want all the data in your current store but in CSSUI, without your existing look and feel?

[benjamintr]

Re: Wombat Beta - Feedback

Yes, I want to keep my current look and feel and have CSSUI. As I understand it, this is a change in the initial framework for how the pages are presented which can then be modified to suit a user's needs.

-B

[Rick Wilson]

Re: Wombat Beta - Feedback

Ben,

Those are conflicting goals and not possible. If you want your existing look and feel, why do you want to change to the CSSUI? As your look and feel is already based on the existing part table based UI, it would be impossible to automatically do that.

[benjamintr]

Re: Wombat Beta - Feedback

That's exactly it.... I don't want my site to be table based. (Nor should anyone else for that matter, but that's a different thread.) I want it to be CSS based. It can look the same but be CSS based instead of table based.

Perhaps I'm not understanding exactly was CSSUI is. I thought it was a rewriting of the HTML to get rid of the tables and add features at the same time. Is it something different?

I'd like to start on top of the new framework and then modify the CSS to look like my current site.

-B

[Rick Wilson]

Re: Wombat Beta - Feedback

Got it, so yes you want what I described as to port over all of your data into CSS UI.

If you choose to restyle CSSUI to follow your current look and feel, that's up to you, but it would be impossible to "migrate" your look and feel automatically from MMUI to CSSUI.

The steps would be:

1. Make a dev copy of your store.
2. Upgrade that store to Wombat
3. Export all or your Products, Categories and Customers from your Dev site, essentially everything possible except for your framework.
4. Delete your store. (Obviously this is why it has to be on a dev site that's a backup of your real site)
5. Add A Store via the admin, make sure you choose CSSUI as the UI module under settings (it should be the default)
6. Reimport everything you exported
7. Restyle the CSS and Page Templates to your desire
8. You're done :)

[benjamintr]

Re: Wombat Beta - Feedback

Yes, that's it! I understand that nothing here can automatically take a table based design and convert it to CSS. I'll be doing that on my own. I guess that proves what they say about assuming things... ;)

And if I do that today with the beta version on a dev server then the beta should upgrade to the production version without any issues?

-B

[Rick Wilson]

Re: Wombat Beta - Feedback

FYI - Release Candidate 2 has been released. Release notes are here: http://extranet.mivamerchant.com/for...446#post353446