Miva 10 must be in place before Christmas?

[birdwaves]

Am I correct that our Production site must be updated by Dec. 21st?

Before Christmas?

Does anyone else question the timing on this?

[ILoveHostasaurus]

If you're referring to what PCI requires, any and all payment applications must be within 90 days of a non-security version release, not just production. Regarding the timing, version 10 was released upon its completion after three years of development. It could not be released before that point, nor would we intentionally delay its release given many customers 1) wanted its features for this fall, 2) needed time to deploy it on a development site and train their staff on its use prior to the Q4 shopping surge.

There is additional information in the following thread: https://www.miva.com/forums/forum/on...ompliance-fees

[birdwaves]

If you're referring to what PCI requires, any and all payment applications must be within 90 days of a non-security version release, not just production. Regarding the timing, version 10 was released upon its completion after three years of development. It could not be released before that point, nor would we intentionally delay its release given many customers 1) wanted its features for this fall, 2) needed time to deploy it on a development site and train their staff on its use prior to the Q4 shopping surge.

There is additional information in the following thread: https://www.miva.com/forums/forum/on...ompliance-fees

My point is that there ISN'T enough time. You can't drop it in Sept. and expect folks to be ready for the shopping season.

[lesliekirk]

2) needed time to deploy it on a development site and train their staff on its use prior to the Q4 shopping surge.

FWIW - the Q4 shopping surge seems to have started back in Q2. Now if the "shipping" season can just catch up. I have store owners that may opt to pay the non-compliance fee and wait until next year to even begin the staff training.

[Rick Wilson]

I understand that depending on your perspective, it would seem like an easy call just to sit on the software for a couple weeks, but I can assure you from where I sit as CEO and can see the multitude of applications our clients use our software for and the variance in their peak season, use case, training needs, bug fix needs, performance needs, it's neither simple to conclude that we should've held the software nor safe to do that.

As a rule, we release as soon as our software is deemed production ready, the major exception to that is if it's done on say a Friday night, we'll hold until Monday.

What is early enough to allow for training with one customer may not have been sufficient for another. What is a feature one customer won't use is one another considers critical to increasing sales/margins. There are also many areas that have seen performance increases, which benefit everyone.

Adding any artificial delay could have created major issues for a large segment of customers who intended to upgrade immediately for performance and/or feature reasons, and needed as much time as possible to train or alter business processes and integrations. To reiterate what I've said previously, any non-compliance fees would not occur until well into January, so this is not going to affect anyone in December from a billing perspective (and the financial penalty is virtually nil FWIW).

Yes to maintain 100% PCI compliance (assuming you're not doing something else that would violate your PCI Compliance) you'll need to upgrade all of your sites, production, test and development by December 21st.

That's ultimately a decision each merchant will have to make for themselves and compared to our competitors who can "force" an update on you, we feel this is the better path.

[Mark Hood]

I'm on the holy heck this has made our lives easier train! It allowed us to be more efficient at just about everything. Yes we have a couple very minor bumps and bruises but...
Since switching I was able to apply a complete new look and feel to our site with no real pain using the new branches feature.
The review basket ability https://docs.miva.com/miva10/referen...review-baskets & https://docs.miva.com/reference-guide/shop-as-customer has changed the customer service world us.
New anything can be tough but this one was worth every penny for us.

[Krsullivan]

So Rick,

Will the Cascading Cat menu be added back to the Miva 10 prior to the 12/21 PCI deadline. Brennon showed me that was being worked on and hoped to have back in Miva 10 by the end of the year. It was a great feature in miva 9, and my techs take 5 times as long to change things, as they cannot find a specific cat quickly and takes too much time for them to verify its the correct one. We have so many subs over 225 and are named the same or very similar under the parent. Some of our cats have 5 sub levels. We are not planning to upgrade our three websites until that feature is in place. I understand the deadline, and the cost for non compliance. I'm sure Miva 10 will turn out to be the greatest thing since sliced bread. It look pretty, but cumbersome to navigate to what we need often. My opinion of course.

Thank you,

Kevin
AutomotiveWorkwear.com

[Brennan]

As of now, the new category cascading menu is part of a 10.00.05 release currently planned for early in Q1.

[schoolsin]

Is the cascading category list still on target for Q1? I have our data entry people testing Miva 10 and refuse to go to allow us to go through the upgrade process because of the category tree missing and it's making it nearly impossible for them to find/categorize products.

[Rick Wilson]

Yeah, it could slip into April though.