Re: Production Release 8 Bugs
I'd like to officially ask that this be reverted back.
In my humble opinion its bad UI, and begs for easy mistakes when making changes to any of these sections... especially if you have a number of selections and just forget to properly click one (or worse yet, click one while inadvertently deselecting others).
Announcement
Collapse
No announcement yet.
Production Release 8 Bugs
Collapse
X
-
Re: Production Release 8 Bugs
It's also documented in the Reference Guide: www.mivamerchant.com/referenceguide
Leave a comment:
-
Re: Production Release 8 Bugs
Hi William
It is in the release notes for update 7 under "Administrator Changes" it is the first bullet point.
“To reduce UI clutter, all locations that previously displayed a grid of checkboxes to permit selection of custom fields now use a multiple select list.”
Leave a comment:
-
Re: Production Release 8 Bugs
Seems counterintuitive to me... way to easy to mistakenly click and remove them... hard to see the "highlight"....
I looked thru notes and didn't - is this documented somewhere so I should have know before deselecting stuff?
Leave a comment:
-
Re: Production Release 8 Bugs
Hi William
In update 7 we changed from the checkboxes to a multiple select box. By clicking on any of the custom field names within the select box you activate them; you can select several by holding down the Ctrl key. When you click away from the box any selected items will remain highlighted showing you which custom fields you have turned on.
Hope this helps
-Eric
Leave a comment:
-
Re: Production Release 8 Bugs
Something changedon Category Tree Template.
non-updated site shows checkboxes for"Custom Fields"
updated sites all have a scrolling selection - and it seems nothing can be done with it.
Did I miss something?
Untitled.pdf
Leave a comment:
-
Re: Production Release 8 Bugs
Originally posted by entrepre7 View PostWhen doing a search for a product I use the link in the left column and use the checkmarks to bring the information I need up before searching. Then I use the edit here button rather than going into the product.
Can anyone else duplicate? Or is a module of mine to blame?
Leave a comment:
-
Re: Production Release 8 Bugs
Major bug in this miva supplied module. It does not show in any of my stores so it must be a custom module. It is also likely it cannot be uninstalled, so it needs to be updated. If it has already been updated, what module version is the latest.
Code: custcrypt
Name: Encrypted Customer Passwords
Provider: Miva Merchant
Supported API Version: 5.00
Version: 1.0001
The problem is that system extension modules in the queue to run after the encryption module simply do not run. They are skipped or suppressed. The customer account gets created/saved, but modules which are doing system actions before the customer account is created are prevented from running.
Leave a comment:
-
Re: Production Release 8 Bugs
When doing a search for a product I use the link in the left column and use the checkmarks to bring the information I need up before searching. Then I use the edit here button rather than going into the product.
If current stock and basket inventory are checked when you change current stock and update it changes to zero. No matter what was there or what you put in it.
If current stock, basket inventory and total inventory are checked it also changes it to zero. Wipes out the previous inventory and does not record a change.
Current stock and total inventory checked it keeps the old inventory but does not update it.
The only way to change current stock is if it is the only inventory checked when you click update.
The Total inventory works fine no matter what is opened.
If the argument is that you should not use the current stock to change inventory then it should be blacked out when you click edit here rather than a window. As I normally open current stock and basket because they display right next to each other.
Can anyone else duplicate? Or is a module of mine to blame?
Leave a comment:
-
Re: Production Release 8 Bugs
I'm not sure when this one crept in. A store is using the Miscellaneous Fee module to create a "Handling" fee. Everything is fine with the fee showing in the basket and then into checkout. It was even showing on the OSEL page. But after clicking Continue and landing on the OPAY page, the fee would disappear. After hours of head beating, I changed the fee from Handling to Handling Charge. The fee stuck and was not erased on the OPAY.
The problem is if you call the fee "Handling" the built in shipping rules/handling charges module removes the charge. I see this as a bug as it should only remove the charge if it's module ID is assigned to that specific charge. Other modules which apply a handling charge should not have their charges removed. Instead of deleting by type, it should be deleting by module_id. If one module removes another module's charge based on type (which could be similar across several modules, e.g. COUPON), there will be a wild west environment with lots of hours spent trying to troubleshoot the problems.
Leave a comment:
-
Re: Production Release 8 Bugs
First backorder since switching to CSSUI. I put in a date of 10-01-2012 but now the order shows "Backordered: 4-11-1964". Not sure if this is a bug or just something to do with my store.
Miva Merchant 5.5
Production Release 8 Update 6
Miva Merchant Engine v5.12
Database API: mysql
Leave a comment:
-
Re: Production Release 8 Bugs
Originally posted by chrisb View PostThe tokenlist module isn't showing the attributes structure when I've included the product_attributes item on a page. Yes, I've made sure that the product I've loaded in the token list has attributes.
I looked into this and it is in fact a bug in the tokenlist module. I have filed a bug on this and it will be resolved in the next update. Thanks for finding and pointing this out!
Ryan
Leave a comment:
-
Re: Production Release 8 Bugs
The tokenlist module isn't showing the attributes structure when I've included the product_attributes item on a page. Yes, I've made sure that the product I've loaded in the token list has attributes.
Leave a comment:
-
Re: Production Release 8 Bugs
The character set in the store's settings is set to UTF-8, and all of the pages in my store are being served as UTF-8, both front-end and admin pages as far as I can tell (Chrome's developer tools are saying that the server is sending a Content-type of "text/html; charset=utf8" in all pages I've loaded, and Chrome is rendering the page with UTF-8 encoding).
In the database, all of my "é"s are being stored as "é," yet when loaded on a front-end page or in the edit product page, it appears correctly. It's like the Windows-1252 equivalents of UTF-8 strings are being stored in UTF-8 encoding. Yes, phpMyAdmin is also operating in UTF-8 as well.Last edited by chrisb; 07-18-12, 07:11 AM.
Leave a comment:
-
Re: Production Release 8 Bugs
What do you have your HTML declarations set to? I have all my sites as UTF8 and thus no issues.
If your HTML page headers are 1255 then forms will submit that data. There are conversation threads this forum about encoding types that explain why.
Leave a comment:
Leave a comment: