Re: X-Cart v4.1.11 released
 

Installing version 4.1.11 displays and error because of missing permission of PGP, I am not using PGP. This is the first time of several installations of prior versions that pgp is kind of mandatory. How can I jump this requirement to continue the installation? or where is the directory to change the permission and go ahead? Thanks,

Re: X-Cart v4.1.11 released
 

I am using 4.1.10 and just had a customer try to modify his profile, but got an error saying his username was invalid and could only contain letters and numbers. He has used his email address since 2006 when we used a previous version of x-cart.

So I found this thread and was glad that it didnt take me TOO long to hunt down the solution ...

but then I realized this thread pertains to 4.1.11 ... and I'm still using 4.1.10

Would the code I found here: http://forum.x-cart.com/showthread.php?t=42147&page=4 (steps 1 and 2) work on 4.1.10?

Re: X-Cart v4.1.11 released
 

The version doesn't matter. The latest security patches are what made the changes.

Re: X-Cart v4.1.11 released
 

Thank you.

So I have customers with 2 years of order histories that need to update their billing informaiton in their profiles .. only they cant because they get that error about usernames only containing numbers and lowercase letters.

If someone originally used their email address, is there anyway to modify a profile or username without losing all the information pertaining to the profile?

Re: X-Cart v4.1.11 released
 

Something to be aware of, it has been reported that if existing customers try to modify their profile they will fall in to the "letters/numbers only trap". Right off hand I can't remember if the customer has the option to change his username or not, but if they don't it can be a HUGE issue.

Re: X-Cart v4.1.11 released
 

customers do not have the option of modifying their username.

now what?

Re: X-Cart v4.1.11 released
 

Check the thread at http://forum.x-cart.com/showthread.php?t=41583&page=3 beginning at post #27. There is a discussion and possible fix for this issue.