Ken

I'm more concerned with the fact that they're telling you all that it's not secure but a loop hole. It's not PCI compliance but rather avoidance. As a business owner/manager and credit card merchant your primary goal should be keeping customer data secure. Stripe has multiple methods for integration. Why would anyone just assume it's using stripe.js? I really don't see the big deal with documenting it to make everyone happy, it seems simple enough, but I also don't get the witch hunt here. If you didn't know before, you know now.

Am I misunderstanding something? If you open the color picker and edit the hex value it changes the color as you're typing it. http://screencast.com/t/bz8e505Zk74 Or are you trying to avoid the color picker all together?

Oh no worries at all, Paulo, I can relate. Tyson helped me accomplish what I wanted. I'm guessing that Blesta has no flag or setting for "email as a username" and so it doesn't know whether the user has chosen one or the other. The "email as a username" function is just on the registration form itself. Basically just entering a variable based on the user's email address. Same with the admin client edit.

Finally? You've been frothing at the mouth for this upgrade for a while now.

Paulo remember our discussion about SolusVM and the username issue? Enforcing usernames helps accomplish that. It is also key in using the shared login plugin since a username is permanent where an email address is expected to be changed at any given point. Then there is the issue of username predictability (in some situations). So there is going to many cases where email address won't be ideal. The username function is very important. I think there should be two modes that are configurable from admin that modifies the registration page. I made a feature request here: http://www.blesta.com/forums/index.php?/topic/2660-toggle-email-as-username-on-registration/

I've come across problems with this feature more than a couple of times so I'm suggesting that there be a toggle for disabling the Email as Username feature on registration forms without having to edit the form itself (since it'll get overwritten on updates anyway). Also if the email address method is used for usernames it's of my opinion that when the user updates their email address the username should be updated as well. Otherwise it's no different than using the Username method and entering an email address. http://www.blesta.com/forums/index.php?/topic/2659-client-email-address/

So the email as a username function is a onetime deal upon registration? That's kind of confusing to the client users I think. If people choose email address for usernames it's only logical that their current email address and any email address they change it to will be their login. That's how every sign-in service works. I can delete that function from the registration form but it'd be nice if we can toggle it in the admin panel. But even with that it should still use the updated email address if that mode is used in my opinion.

Why are you unable to use SSL?

Will do. Out of curiosity is there a place where I can see the current versions and check them that way?

Characters. That was one of one of the first things I checked and none of them are upgradable. If that function has been removed (or has it?) would it still be there anyway? Is it safe to assume that they have all been upgraded or should they be checked?

2/3 66%? Does anyone else get that? It seems to upgraded okay so far. ---------------------------------------- Blesta CLI Upgrader ---------------------------------------- Upgrade from 3.1.2 to 3.2.0? (Y/N): y 7/7 [========================================] 100% 2/3 [==========================> ] 66 % Finished. Btw the Client Area looks beautiful. Great work!

In the thread that he linked though he said he didn't have those emails in his log.

Is this solution still working for your order forms MemX2? http://www.blesta.com/forums/index.php?/topic/1579-shorter-urls/?hl=order+route#entry13500 +1 on shorter URLs overall. But not at the expense of proper methodology (including but not limited to best practices in terms of security).

Do you have it working with the universal module yet?

Blesta module got cancelled I see. That's disappointing.