Production Release 8 Bugs

[Ron Frigon]

Re: Production Release 8 Bugs

Product > Shipping Rules > Limit Shipping Methods

I use Limit Shipping Methods on pretty much all of the products in a particular store.

I imported a small update to a custom field on about 60 items. Imported the PRODUCT_CODE, PRODUCT_NAME, "Custom Field" via Import Data > Add/Update Products from CSV.

After the product import, "Limit Shipping Methods" for each of the items imported was unchecked.

Edited for additional info:
The Shipping Dimensions fields were also emptied.

[Rick Wilson]

Re: Production Release 8 Bugs

I would recommend upgrading to 5.17 and the latest GD lib.

The issue almost certainly has something to do with your GB lib.

[BigDummy]

Re: Production Release 8 Bugs

You were right about the cache not fixing it. The word back from my host is that my server is using GD 2.0.28 on Miva Empresa 5.12. I looked, but wasn't able to find the documentation for the minimums required for PR8 Update 7.

[Rick Wilson]

Re: Production Release 8 Bugs

The only reason those would break is if there's an issue with the GD library in your engine. You should contact your host's support to have them check the GB Library in the Engine.

You might also try clearing your cache, but I doubt that'll solve it.

I can say for sure that on our corporate store that Update 7 didn't impact the graphs, etc...

[BigDummy]

Re: Production Release 8 Bugs

I couldn't find this elsewhere, so perhaps it is local. Since the upgrade to update 7, the graphs only show a broken image symbol in the Reports on the main page, and attempting to load a report crashes IE (not sure about other browsers).

[alphabet]

Re: Production Release 8 Bugs

Hi kayakbabe

I have added a bug for the forgot password link not validating that there is a value in the email address/ user field.

Until the bugfix here's a js form validation script to check email.

1. In the head section add:

<script type="text/javascript">
function checkemail() {
var oError = document.getElementById('fpwdemail');
var email = document.dkfpwd.Customer_LoginEmail.value;
var re = /^[^\W][a-zA-Z0-9_-]+(\.[a-zA-Z0-9_-]+)*\@[a-zA-Z0-9-]+(\.[a-zA-Z0-9-]+)*\.[a-zA-Z]{2,6}$/;
if (re.test(email)) {
oError.style.display = "none";
return true;
} else {
oError.style.display = "block";
return false;
}

}
</script>

2. Name the form and add event:

<form action="&mvt:global:secure_sessionurl;" method="post" name="dkfpwd" autocomplete="off" onsubmit="return checkemail(this);">

3. Add an error message just above the email input field:

<div id="fpwdemail" style="display:none;padding-left:66px;color:red;">Hint: Invalid Email Format</div>

4. Change input type field for modern browsers:

<input type="email" name="Customer_LoginEmail" id="Customer_LoginEmail" autocomplete="off">

[titus]

Re: Production Release 8 Bugs

Product Attributes get entity encoded when they're put in the basket, but they aren't decoded when they're taken out.

For example:

"To be, or not to be?", that is the question..

Would get saved as:

"To be, or not to be?", that is the question..

And this is fine, I understand that sometimes entities need to be encoded when you're working with a database. However, they aren't decoded when they're pulled out.

[Eric Foresman]

Re: Production Release 8 Bugs

Hi kayakbabe

I have added a bug for the forgot password link not validating that there is a value in the email address/ user field.

-Eric

[Rick Wilson]

Re: Production Release 8 Bugs

I spoke to Jon and he agrees the Null values thing is a bug, not sure if that'll get fixed in Update 8 (coming in 2 weeks) but it likely will.

As for the Multiple Select on tablets and phones, I just tried it on my iPhone and iPad and it's really slick. It's way superior to the prior checkbox method IMHO. Have you actually tried it via tablet or phone yet? At least in iOS they handle multi select boxes in a very nice way that makes it highly usable.

[kayakbabe]

Re: Production Release 8 Bugs

I vote to have the checkboxes back too!
I sometimes have to edit my site with my phone or tablet. Have you EVER tried to do a multiple select box on something like that instead of being at a full blown computer? just try it from an ipad or iPhone.. ugh!

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).

[Rick Wilson]

Re: Production Release 8 Bugs

I agree on the null values, I'll talk to Jon.

[kayakbabe]

Re: Production Release 8 Bugs

But that message makes absolutely no sense, if the field is empty.
if the field is empty then no reverse engineering is being attempted at all
it was just 'empty' 'null' 'blank'
it is greatly confusing and is going to piss of customers and make them think my store is broken.
I've been using webstores for years to shop, and it made ME think it was broken.
What is is going to do to my customers?

a message like, please fill in the blank so we can attempt to find your account.
in the case of an empty field...
is not going to reveal anything and can't be used to exploit anything.

It's not like they are trying different addresses.

[Rick Wilson]

Re: Production Release 8 Bugs

That's a specific security issue with PCI and the Banking industry. They want a generic message so you can't reverse engineer if someone has given you an email address in the past.

[kayakbabe]

Re: Production Release 8 Bugs

bug with pr8 update 7, forgot password error message doesn't make sense.

I cleared my cookies and restarted my browser to make sure this wasn't a caching issue.

If I click on sign in and do nothing, do not enter anything into any form field.
Click on forgot password as a shopping trying to get their password might do.

the store gives me a message that makes no sense. here it is.

"Instructions to reset your password have been sent to the email address on file with your account. Please contact us if you require further assistance."

I haven't given it a user or an email address to identify any account, the store SHOULD be asking me for a userid or something with which to do something. I haven't given it anything yet. So I wonder who it is emailing.

[kayakbabe]

customer login via email with multiple email accounts broken

bug with pr8 update 7. customer login via email with multiple email accounts broken.

Previously I used Weilands customer email login. For the update I removed it because update 7 includes email login and I wanted the new minibasket and shipping calculator.
I ran the update.
However now my customers who had several accounts can not log in to all of them. They can only log into the first account in the database by using their email address.

With Bill's module, both the email and password were used to find the account, so a customer with several accounts under the same password could still login to the appropriate account.

The new miva login with email feature doesn't account for the fact that there can be multiple customer accounts with the same email address. So there is now no access for those customers to their second or third accounts in the store. those accounts are essentially 'broken'.
doing password recovery also only gives the password for the first account, not the second or third, etc.