Core-17 Streaming Update Released

[wcw]

Re: Core-17 Streaming Update Released

i'm looking at the s01_CFM_CustValues table.
I do see a lot of duplicate field_id and cust_id
where cust_id is zero.

Were those created by customer's checking out without created an account or not completing checkout?

Should i delete those records?

Are you using my custom customer fields interface module? If yes, you should have received an update (I mailed out) that will delete the records with cust_id = 0 in them when you update the module. If not, you can delete them manually.

[kayakbabe]

Re: Core-17 Streaming Update Released

WCW, nope i wasn't using it, i will manually delete them.

I deleted the cust_id = 0 fields and tried to rerun the update.

Still getting error:

Miva Merchant encountered a fatal error during upgrade. The upgrade process has been aborted.

Error Code: MER-UTL-CST-00049
Description: mysql_execute: Table 's01_CFM_CatFields' already exists

[wcw]

Re: Core-17 Streaming Update Released

You have to drop that table and alter the custom fields tables. Contact miva as they are tracking these.

[Jim McCormick]

Re: Core-17 Streaming Update Released

To avoid future panic, how do you set up a test environment? Can it be done on a personal computer -desktop?

If you don't have a host like Hostasaurus that can setup a testing environment for you, you can download Miva Merchant Mia and run your store on your local PC. The only catch is that Miva Merchant Mia is Windows only.

http://www.mivamerchant.com/products/mia/

[TipPro]

Re: Core-17 Streaming Update Released

Has anyone compiled a list of a tables that should be checked for duplicate records and a list of modules that should be upgraded before a user upgrades to Core-17?

[kayakbabe]

Re: Core-17 Streaming Update Released

i think they've done something like create 2 fields for each single custom field. like if the data within that field exceeds 254 characters, then use a different field instead. That can really bugger up things for anyone who uses third party modules to affect those custom fields. or in my case who uses php to affect the content of those fields.

i'm hoping that when miva tech support finally helps me out (i have a ticket open with them right now) that they will tell me this is only temporary for the core 17 update. such as they had to move the data somewhere before changing the field definition and that the existing data would have been moved back. I won't know until they've helped me fix the problem.

From the postings around this forum and from phone calls, it appears that those of us who use custom fields are being bitten by this bug. While many store owners don't seem to use them at all, so the bug won't affect them. It will at some future point if they decide to start using them. So, i hope this gets fixed.

[Rick Wilson]

Re: Core-17 Streaming Update Released

From the postings around this forum and from phone calls, it appears that those of us who use custom fields are being bitten by this bug. While many store owners don't seem to use them at all, so the bug won't affect them. It will at some future point if they decide to start using them. So, i hope this gets fixed.

While all of the issues around Core 17 are about third party mods and custom fields most customers who use custom fields won't have any issues with Core 17. We tested Core 17 on a store with 100,000+ sku's that utilizes more than 100 custom fields and Core 17 didn't cause any problems.

The issue is one of API usage and properly accessing that data.

[Biffy]

Re: Core-17 Streaming Update Released

Excellent job, ya'll!

I have a minor request...

Could you please rename the category spreadsheet meta-description and meta-keyword fields to say, well, meta-description and meta-keywords? It's not clear what these are using the current field names.

Thanks, and congratulations on a terrific update!

[lesliekirk]

Re: Core-17 Streaming Update Released

The ship to/bill to switching option is nice,

Would this new option cause an "Invalid" issue during checkout if someone doesn't fill out the Ship To because it's not different? I just got a report (and confirmed the behavior) from a site that started experiencing this problem immediately after running the latest update.

[Rick Wilson]

Re: Core-17 Streaming Update Released

Would this new option cause an "Invalid" issue during checkout if someone doesn't fill out the Ship To because it's not different? I just got a report (and confirmed the behavior) from a site that started experiencing this problem immediately after running the latest update.

I don't think so unless they flipped those settings. But can you open a ticket on it?

[bigdog12]

Re: Core-17 Streaming Update Released

Applied the update earlier and have run into an issue.
When I click on certain products (may be affecting several products out of hundreds, haven't checked yet), the product displays but I'm getting the following text at the very top of the page, above the global header: "Runtime error in lib/db.mvc @ [00000080:00000094]: lib/dbeng/runtime.mv: Line 247: MvOPENVIEW: Invalid instruction". I'm also getting the following error above where the product attributes have the pull down and/or checkbox options: "Runtime error in lib/db.mvc @ [0000013f:00000034]: lib/dbprim/products.mv: Line 101: MvOPENVIEW: Database 'Merchant' already has a view named 'Products' "

Damn, seems like everytime I do an update there's always an issues with my store. Not surprised with the string of bad luck I've been having :(

Thanks for the assistance. If nothing else, is there a way to roll back the update? We do quite a bit of sales on this store and I can hear the boss complaining already!

Thanks again for any assistance you can provide.

[Rick Wilson]

Re: Core-17 Streaming Update Released

Call support we can get this fixed very quickly. 858-490-2570 option 3

[Laura Schindler]

Re: Core-17 Streaming Update Released

Hi Big Dog,

Please call or email support so we can get a ticket started for you. 858-490-2570 option 3 or support@mivamerchant.com.

Thanks,

[bigdog12]

Re: Core-17 Streaming Update Released

Thank you Laura. I have just submitted the ticket and escalation form.
Ticket# is GDZ-535326.

Thanks again.

[Rick Wilson]

Re: Core-17 Streaming Update Released

Since our Tech Support is closed during the weekend, we've decided to move Core 17 over to the Beta stream while we're closed. It will be back up on Production early Monday morning and if you want it this weekend just switch your Update Settings to Beta (it's still the production patch).