https://www.miva.com/whats-new-version-9-08

New Features

· New Square payment module

· New Combination Facets module allows facets to be constructed from multiple component parts. For example, it could be used for an auto parts application (Year/Make/Model), etc.

· The Custom Fields module now supports multiple-value fields. These fields can store more than one value per product.

· The Braintree payment module now supports advanced fraud filtering through their Kount service.

· The Template Based Emails module now supports pending subscription emails, which are sent N days before a subscription is scheduled to be processed.

· The CHASE Orbital Payment Gateway payment module now supports username/password authentication.

· Apple Pay now provides better error messages/handling when used with iOS 11 devices.

· Facet Rules now allow a facet to be displayed, hidden (but active, if a value is passed) or disabled entirely.

Other Changes

The buySAFE module has been removed.

Bugs Fixed

22469: Payment: Unable to complete checkout using PayPal express when limiting payment methods to PayPal express.

25066: MMTextEditor: Make 'URI' & 'Display' fields bold when inserting hyperlink

25076: MMTextEditor: 'auto' & 'Auto' do no behave the same when editing image dimensions

25200: Specifications: Subscription Reminder Emails

25312: MMTextEditor: Feature Request: MMTextEditor: Add ability to enable/disable spell check on a per-editor basis

25441: Module: marketplaces: Marketplaces: Google Shopping: Variants which have images and are using the selected variant Google Shopping image do not get uploaded

25452: MMTextEditor: Feature Request: MMTextEditor: Add local/global setting management

25454: MMTextEditor: Feature Request: MMTextEditor: Add ability to change displayed font size/color/family for source mode

25480: Module: mvga: Subscription orders display zero quantity in Google Analytics

25484: MMBatchList: MMBatchList: MMBatchList_Column_TextArea: Inline editing multiple records and changing the first record's textarea updates the last records textarea instead

25486: Module: applepay: ApplePay: International postal codes are not handled correctly

25492: Module: marketplaces: Marketplaces: Etsy: Listing descriptions should not be limited to any character limit

25493: Facets: Facets need to account for products hidden when out of stock.

25500: Database Layer: Setting a product to inactive should update Product.lastupdated/cache_ver values

25523: Module: applepay: Apple Pay transactions fail to complete on iOS 11

25525: Module: marketplaces: Marketplaces: Google Shopping: Duplicate product images should be shown on the product settings screen

25526: Module: marketplaces: Marketplaces: Google Shopping: Product images and how they are built and handled need to be reworked

25527: Module: marketplaces: Marketplaces: Google Shopping: Deleting a product does not delete all associated sNN_MP_GoogleShoppingXXX data

25566: Module: marketplaces: Marketplaces: Google Shopping: Add image_id back to the sNN_MP_GoogleShoppingItemImages table so it can track image records

25583: Module: marketplaces: Marketplaces: Etsy: If creation of listing variants fails, the entire listing should be deleted

25584: Module: marketplaces: Marketplaces: Etsy: Item image type records are not deleted when a product is deleted

25594: Module: mailchimp: MailChimp: Multiple incorrect currency codes

25595: Administrative Interface: product_update_lastupdated_relatedproduct slows down batchlist product deletion considerably.

25601: Module: upsxml: Update API endpoint URLs 25602: Module: mailchimp: Full sync task should delete the webhook when everything has been synced OR on error

25605: Module: cmp-cssui-addressfields: CADE, g.Address_Default_Shipping and g.Address_Default_Billing do not get set correctly

25606: Subscriptions: Subscriptions: Next order date gets saved to midnight server time, but displayed in admin as merchant local time

25652: Module: discount_volume: Volume pricing table becomes duplicated on products when more than one price group is assigned to a category.

25653: Module: discount_saleprice: Sale Price input field is duplicated on the edit product screen

25656: Module: cmp-cssui-prodlist: In advanced mode, the "Calculate Predicted Discounts and Sale Price" checkbox must be checked to get sale prices

25891: MMTextEditor: MMTextEditor: Z-Index issue causes line numbers of other editors to be displayed above table settings overlay

25894: Database Layer: Scheduled tasks, Perform Module Cleanup Tasks, takes too long when there are a lot of baskets.

25902: Discounting Subsystem: Product variants are not excluded from discounts when the master product is excluded.

25903: Module: discount_addon: Product added to the basket via the Add on product discount are missing the sku value.

25909: Administrative Interface: Edit order, order items, discount line item shading is not consistent across the table.

25915: Module: stdschtasks: Precalculating discount prices generates too much i/o and does not complete with a large number of discount signatures

25938: Administrative Interface: Admin: Orders: Need to add check to see if the inline edit button exists before calling Show/Hide

25939: Administrative Interface: Admin: Customer Orders: Need to add check to see if the inline edit button exists before calling Show/Hide

25946: Price Groups: PriceGroupCategory_Update_Assigned returns as blank when logged in as a non-admin user

26035: Facets: Attribute template facets that overlap with product attribute facets can cause 0 records to be returned when selected.

26037: MMTextEditor: MMTextEditor: Source Mode editor does not position cursor correctly when typing

26070: Facets: Facet codes that contain & in them do not get properly encoded for page numbers

26124: Template Import/Export: TUI_HTML_Parse_Tag_Start does not read the last character in the buffer

26125: Template Import/Export: Page Import will fail if two items that have an external file template are located too close to each other

26147: Gift Certificates: Fatal error during checkout when purchasing a Gift Certificate in MYSQL strict mode.

26150: Administrative Interface: User Preferences: Stores are not visible for administrators who are not store managers

26174: Module: canvat: Wizard_CanVat_Content_GST: g.Wizard_CanVat_GST needs output encoding

26175: Module: devat: Wizard_DEVAT_Content_Add_Rate: g.Wizard_DEVAT_Add_Rate needs output encoding

26176: Module: devat: Wizard_DEVAT_Content_Product_Rate: g.Wizard_DEVAT_Product_Select needs output encoding

26177: Module: vat: Wizard_VAT_Content_Product: g.Confirm_Rate_Message needs output encoding

26178: Module: vat: Module_Wizard_Summary_Field: g.Wizard_VAT_Prompt needs output encoding

26179: Module: readytheme: ReadyTheme: Product Listing in Advanced Mode does not properly export image settings to frameworks

26181: Facets: Duplicate facets appear at runtime when 2 or more product list items are assigned to the same page.

26262: Module: chasepaytech: CHASE Paymentech Orbital Gateway: Mode provisioning tag sets the outputted values backwards

26266: Module: customfields: Custom Fields: Missing security preamble in JSON functions

26330: Facets: Attributes facets with mixed case don't work at all in MivaSQL

26332: Module: customfields: Facets with mixed case are handled differently in MivaSQL than in MySQL

26355: Facets: Category Facet Rules List displays incorrect value for Handling

New Builtin Functions

miva_joinstring( input var, join_with, flags )

• If the "input" parameter is a string, then a string is returned alongside any modifications made via the "flags" parameter.
• If the "input" parameter is an array, then a string is returned with each array element's value separated by the "join_with" parameter along with any modifications made via the "flags” parameter"
• If the "input" parameter is a structure, an empty string is returned.

Parameters:

• input - The input variable
• join_with - The string that will seperate array elements
• flags - A comma separated list of any of the following:
• escape - Escapes the join_with characters if the join_with characters exists in the element's value.
• insensitive - When combined with the escape flag, it will search for the join_with characters in an insensitive fashion.

Return Value:

• The joined string

Other

miva_splitstring

• Added flag "escaped" which will cause the function to not split on the separator character if the seperator character is escaped.

Bugs Fixed

25940: crypto_base64_decode should not require padded "=" in order to successfully decode

26092: The compiler outputs an invalid engine version for every command line parameter

26134: Output::Write_Compressed_Full can read past the end of the buffer

26186: FunctionManager::Read should validate all values read from the binary

26188: Dictionary::Read should validate all values read from the binary

26189: VariableHash::Read should validate all values read from the binary

26190: LocalizedIndex::Read should validate all values read from the binary

26191: LocalizedDictionary::Read should validate all values read from the binary

26192: SegmentManager::Read should validate all values read from the binary

26193: TaggedFile::Header_Read should validate all values read from the binary

26194: TaggedFile::Directory_Read should validate all values read from the binary

26204: config3x_setconfigvalue leaks memory 26216: TaggedFile::Section_End doesn't grow directory entries properly

26221: LocalizedLanguages::Read should validate all values read from the binary

26310: MivaVM::localize / MivaVM::localizev need to ensure the dictionary is loaded

Over the last year, our team has been working diligently to engineer a brand new framework for our ReadyTheme website templates. Last quarter, we introduced you to Elements, the revolutionary new raw foundation for which all of our new ReadyThemes will be based upon.

Now available for download, Shadows is the newest addition to our extensive ReadyTheme library and is undeniably, our most polished ReadyTheme yet. Each component of the Shadows ReadyTheme has been artfully crafted for desktop and mobile shoppers to provide the best user experience possible from the sleek storefront design, to the robust product pages, and all the way through to the checkout process.

The Shadows ReadyTheme elegantly showcases the sophisticated capabilities of our native faceted search functionality along with a collection of other new features designed to help ecommerce storeowners build the best online shopping experience possible. Learn more about the new, native ReadyTheme functionality below.

New Out of the Box Functionality in the Shadows ReadyTheme 

• Users can view relevant products as they enter a search query, thanks to the search preview feature that seamlessly works in the global header and the new sticky header.

Click here to read more 

HTTPS has always been a core part of any ecommerce website. If you’re accepting personal information online, including credit cards, you must have an SSL Certificate to encrypt the data. Typically, a website was only served over securely (HTTPS) on Account and Checkout Pages. General shopping and browsing was done over unencrypted HTTP. Over the past couple of years, that is starting to change. Google now prefers the entire site to be served over HTTPS to protect the visitor. They are even giving sites that are all https a small ranking boost. 

While serving every page over HTTPS adds some additional server overhead and can cause the page to load slightly slower, the additional time should be unnoticeable to the visitor.

This tutorial will walk you through step by step how to convert your Miva store to be entirely served over HTTPS. While the actual implementation and changes are relatively simple, making sure everything is done correctly is extremely important. If done improperly there are negative customer experiences which can occur, such as getting insecure warnings on pages and negative SEO consequences which can damage your rankings – both of which you want to avoid.

Click here to read more

As Miva has evolved, we’ve built a unique, hybrid Software-as-a-Service (SaaS) platform that allows our customers to retain the control and independence of distributed software, while having the easy upgrades we’ve all come to expect from SaaS platforms. It’s time we refine and formalize our policies on when software is officially EOL (End of Life), and update our Non-Compliance Fee (NCF) policies accordingly.

Most Software-as-a-Service platforms don’t give you a choice when it comes to upgrades – you simply login one day and your platform has been upgraded for you, whether you like it or not, and whether it negatively impacts your business or not.

Miva has chosen a different path. While providing the type of seamless upgrades and updates people have come to expect from Software-as-a-Service, we don’t force you to upgrade before you’re ready. The downside to this path is that, often times, people will choose to run out-of-date software; and in this day and age, it’s simply not a wise, safe or prudent choice to run out-of-date software. 

We specifically created and use the Non-Compliance Fee program as an economic incentive program to encourage people to update their stores regularly.

For example, in my opinion, it is simply not safe to run any version of Miva Merchant prior to 5.5 Production Release 8 Update 7 (which was released on October 16, 2012, over two and a half years ago), yet we still have many customers who choose to run Miva Merchant 5.5 PR8 Update 6 or older (including people still running 2.x stores, which was released way back in 1999).

Going forward, Miva Merchant software will be considered EOL (End of Life) when either of these 2 circumstances are met:

1. Software has been officially Non-Compliant due to normal software releases, from the perspective of PCI software updates, for more than 12 Months. In other words, 15 months after the release of a new update, software will officially become EOL.

or 

2. Software that is Non-Compliant due to a security release, from the perspective of PCI software updates, for more than 3 months. In other words, if we mark an update as a security-focused update, per the terms of PCI compliance, older software will be considered EOL 4 months after the security update is released.

What impact does Miva marking a product as End of Life have on you, the merchant?

First and foremost, it means we will not, under any circumstances, release a patch, update or upgrade for that version. The most common use cases would be either an API change by a provider (say for example USPS changes its rating API, we will not be releasing an updated USPS module to work on any EOL version of Miva Merchant).

Second, when there are system-level security changes (such as POODLE in 2014), we will not be releasing a patch or engine upgrade to keep EOL software fully operational on modern Operating Systems.

Non-Compliance Fee program changes:

Currently, we have a varied Non-Compliance Fee program that means you pay a different fee depending on if you’re hosted by a third party or directly with us; and, if you’re hosted with us, your fee varies based on the plan you have.

Going forward, we’re standardizing our Non-Compliance Fee program to a flat rate program. Your NCF will be $50 per month, if you’re running Non-Compliant but non-EOL’d software; or, it will be $100 per month, if you’re running Non-Compliant and EOL’d software.

Click here for the original blog post.

For anyone looking to build ReadyThemes (or you just want to learn more about how the new ReadyThemes works) We just released 5 new developer videos which walk through the Base Developer Framework as well as a overview of the main ReadyTheme features and functionality

http://www.miva.com/videos/category/readythemes


We'll be continuing to add new ReadyTheme videos however, if you have any areas you would like to see more video content (or written documentation) on let me know and I can add it to our queue.

Some other helpful links:

ReadyTheme Documentation - https://docs.miva.com/videos/articles/...-documentation

Base ReadyTheme Framework - https://docs.miva.com/videos/articles/...ase-readytheme

Dear Miva Merchant 4.x Customers,

As many of you already know, July 1, 2010 was the mandatory deadline for all payment applications to become PA-DSS Validated. This requirement impacts all payment gateway providers, swipe terminals, and shopping cart vendors like Miva Merchant.

PA-DSS Validation is different from PCI-DSS Compliance. Both are implemented and governed by the PCI Security Council, but in order to maintain your PCI-DSS Compliance as a merchant, you must be running PA-DSS Validated (and properly configured) software.

Miva Merchant recently completed its PA-DSS Audit and has received its Attestation of Validation (AOV) for Miva Merchant 5.5 Production Release 7. However, Miva Merchant 4.x is not and will not be PA-DSS Validated.

There are a number of reasons why we’ve been unable to validate Miva Merchant 4.x. The bottom line is that due to the complexity of the software code, it would be impossible to maintain compatibility with existing 4.x stores while still achieving validation.

So here is what we are providing for you, our valued Miva Merchant 4.x customers, to enable you to be fully PA-DSS Validated: an absolutely FREE (yes free) upgrade license to Miva Merchant 5.5. This upgrade license previously cost $399. But it is now available free of charge to every Miva Merchant 4.x user with an eligible license. Please contact your Host or Miva Merchant at (858) 490-2570 for information on your upgrade license.

We’ve also developed three new tools (also free) to make it easier to upgrade to 5.5.

1. OpenUI/MMUI Framework Exporter
2. Order History Exporter
3. Catalog Exporter (Products, Categories, etc...)

You can get information and to download the tools here

In addition, for any Miva Merchant 4.x storeowners whose merchant account providers are not providing a grace period for running PA-DSS Validated software, we’ve cut a deal with PayPal to provide you a reduced rate on PayFlow Link. Utilization of PayFlow Link provides a workaround that, though less than ideal, will fully integrate with Miva Merchant 4.x as it exists today and handle all of your PA-DSS and PCI-DSS requirements. Finally, you need to be aware that Miva Merchant 4.x will formally reach End Of Life on December 31st, 2011.

Until then, we will continue to maintain existing critical shipping and payment updates to ensure your 4.x store operates as it does today. But as stated above, PA-DSS Compliance will only be available through the PayFlow Link workaround. And on January 1st, 2012 all support and updates will cease for those who have not upgraded to Miva Merchant 5.5.

We want you and your store to continue to succeed. That’s why the Miva Merchant team is providing you with this free upgrade to 5.5. We encourage you to begin the upgrade process immediately in order to maintain the best experience for you and your customers – as well as robust compliance and validation with all PCI security issues.

Community Forum post regarding Miva Merchant 4.x PA-DSS Update and End Of Life Announcement

Click Here

Credit Card Security Code ( CVV2 ) explained

What is the CVV2?

The CVV2, Credit Card Security Code is the number found on the back of most cards. It's usually a three digit code, and it's purpose is to ensure that the person using the card for a purchase actually has that card IN THEIR HAND.

Why ask for the CVV2?

There are LOTS of ways that criminals can get their hands on lists of stolen credit card numbers. Getting hold of matching CVV2 numbers is much more difficult. Because of that, if your store verifies the CVV2 at checkout then it is much more likely that the purchase is genuine.

How can I accept CVV2?

Miva Merchant has modified many of its CURRENT payment gateways to include the CVV2 feature in the LATEST releases. Some CVV2 supported gateways are:
# AuthorizeNet

# Innovative Gateway
# First Data Global Gateway
# Payflow Link
# Payflow Pro
# CHASE Paymentech Orbital Gateway

# CyberSource

What if you process your orders through a terminal and it NEEDS CVV2

This is another frequently asked questions. The simple answer is... Tough Luck!.

There is a REASON why your terminal wants this CVV2. It's probably because your merchant account provider is giving you a good rate for NON-INTERNET sales. They give you this rate because if you are processing a card through a terminal, and have the card in hand then this is low risk. If on the other hand you are trying to process internet sales, then your merchant account providor wants to charge you Mid or Low qualifying rates.

What do you do? Well one thing you cannot do is find some way to store your customers CVV2 at checkout. This is absolutely forbidden by Visa, Mastercard etc. Think about it... what value is the CVV2 standard if people start storing this number with the credit card!!!

Bottom line, if you use simple credit card validation then your only options are:

# 1. Call customers and ask for the CVV2 when processing the transaction
# 2. Upgrade your payment gateway to one of the options above.