RSS Feed
News
Nov
16
Miva Merchant 9.07.03 Released
Posted by Wayne Smith on 16 November 2017 09:12 AM

Miva Merchant 9.07.03 Release Notes

 

 

Bugs Fixed

25576: Module: customfields: Facet fails to load correctly if the facet is a custom field and that custom field is selected to be searchable.

25580: Core Runtime: Facet Range Slider does not work on mobile


Read more »



Nov
10
Miva Merchant 9.07.02 has been released
Posted by Wayne Smith on 10 November 2017 08:08 AM

Miva Merchant 9.07.02 Release Notes

 

Bugs Fixed

25543: Core Runtime: Runtime search needs to work exactly the same as pre-9.07.00

25558: Module: templateorderemails: Reference counts are not properly tracked for Template Based Emails scheduled tasks created by the 9.07.01 patch or during module installation

25559: Module: templateorderemails: Template Based Emails: Scheduled tasks should not send emails when the Abandoned basket email is configured to send manually

25561: Module: discount_saleprice: Assigning a product to multiple categories can cause duplicate price groups to display on edit product

25562: Module: discount_volume: Assigning a product to multiple categories can cause duplicate price groups to display on edit product


Read more »



Nov
7
Miva Merchant 9.07.01 has been released
Posted by Wayne Smith on 07 November 2017 02:09 PM

Miva Merchant 9.07.01 Release Notes

 

MMTextEditor Changes

  • MMTextEditor settings have been moved from the Settings tab of the Users screen to User Preferences:
    • mmtexteditor.richtext replaces the "Default to Rich Text Mode When Available" option
    • mmtexteditor.linenumbers replaces the "Line Numbers Visible By Default in Source Mode" option
    • mmtexteditor.spellcheck replaces the "Browser Level Spell Check Enabled (If Supported)" option
    • All of these preferences are Domain-level boolean values and can be added to a user's preferences on the Preferences tab of the Edit User screen
  • A new user preference, "mmtexteditor.enabled", allows the 9.07 rich text editor to be disabled completely on a per-user basis

 

 Other Changes

  • Facet values are no longer progressively loaded based on the selected values of higher priority facets. Instead, each facet is now queried with all other applied facets in effect.
  • The product list component no longer honors facet parameters or loads possible facet values unless the "facets" item is assigned to the page.

Bugs Fixed

25302: MMTextEditor: MMTextEditor: Background color, foreground color, and font size cannot be replaced in certain edge cases

25303: Attribute Templates: Attribute Templates: Products tab can take a long time to load

25304: MMTextEditor: Feature Request: MMTextEditor: Add ability to completely disable MMTextEditor and fall back to a generic HTML TextArea

25307: MMBatchList: MMBatchList: Sort By Ascending/Descending menus do not scroll when content overflows height of menu

25311: Scheduled Tasks: Resumed tasks that return an error enter infinite loop

25314: Administrative Interface: Setting Maxasynctasks =-1 causes runtime errors in admin and runtime

25416: Module: cmp-cssui-searchfield: Search value needs to be encoded

25426: Module: reviewbaskets: Typo in Delete Baskets button on Review Baskets batch list

25428: Search: Searching should split on spaces within the search value and search for each word individually

25429: Module: marketplaces: Remove the UTF8 byte order mark from the following files

25430: Database Layer: Sort operations should update appropriate lastmodified/cache_ver values

25432: Facets: Checkbox custom fields when used as facets should display the field value as 'Yes' instead of '1'

25433: Administrative Interface: New Payment Module column makes order list loading unbearably slow

25442: Wish Lists: Attributes are not displayed in the correct display order when viewed from wish lists

25443: Scheduled Tasks: ScheduledTasks_Spawn_AsynchronousTask should NOT wait for the async lockfile if the async task fails to spawn

25444: Module: templateorderemails: Abandoned cart emails get sent for empty baskets

25446: Module: mailchimp: MailChimp should be sent order datetimes

25448: Scheduled Tasks: ScheduledTasks_Spawn_AsynchronousTask should verify a store is open before executing any scheduled tasks

25451: Module: templateorderemails: Abandoned basket email scheduled task should be created by default.

25459: Core Runtime: Search field has two class attributes

25460: Module: mailchimp: MailChimp should be sent product image URLs

25461: Utility Library: Image_ResizeIntoBoundingBox honors non-integer width/height and results in an ever-growing list of sNN_GeneratedImages entries

25462: Administrative Interface: Canceled items do not get removed from order subtotal

25495: MMTextEditor: JavaScript error in FireFox when you undo to a completely empty mmtextarea

25505: MMTextEditor: Background color does not get applied if the last item in the selection is a blank newline (chrome and Firefox)


Read more »



Oct
13
Work Faster with Keyboard Shortcuts for the Miva Admin
Posted by Wayne Smith on 13 October 2017 09:20 AM

NAVIGATE YOUR MIVA STORE ADMIN FASTER THAN EVER WITH KEYBOARD SHORTCUTS!

With our helpful key command reference sheet for both Mac and PC users, you can perform basic functionality from global keyboard shortcuts like showing history and bookmarks to batch list search with just a couple keystrokes. You can save time by ditching the need for several mouse clicks. Utilizing these helpful key commands can help you and your team multitask more effectively and work more efficiently.

 

Download Miva admin hot keys reference sheet for Mac and PC.

 

 

Related Post

Get to know the Miva 9 Admin: Hot Keys Infographic

 


Read more »



May
5
Miva Blog - How To Convert Your Entire Miva Store to HTTPS
Posted by Wayne Smith on 05 May 2016 10:18 AM

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


Read more »



May
6
End of Life Software and Non Compliance Fee Change Updates
Posted by Wayne Smith on 06 May 2015 02:54 PM

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.


Read more »




Help Desk Software by Kayako fusion