Printable View
It's not that there's no password to match, since EMP checks (after the customer password check) to see if the password belongs to an EMP-enabled admin. It's more likely that some COWOA update to the login page (?) is blocking the login using COWOA customers' email addresses.Quote:
Originally Posted by jeking
Should COWOA, with no other interfering plugins, allow an admin to login with just the customer email address?Quote:
Originally Posted by lat9
Quote:
Originally Posted by OLCS
you can try this: https://github.com/DivaVocals/zen_COWOA
Technically this is a beta version until it's submitted.. I am still gathering feedback on this version (which is why I haven't yet submitted it..) But I am using it on several live sites..
It's like lat9 pointed out.. COWOA prevents you from logging into ANY customer account flagged COWOA (meaning this is a guest account).. If you are not logged into the front-end of the store, just like the customer you can view the order status from the customer POV with the order number and email..Quote:
Originally Posted by jeking
Perhaps if you say what it is you are trying to do, we can help you come up with a solution..
Yes, of course. We like to be able to log into customer accounts to take orders over the phone. The problem arose with a customer with a guest account and we could not log into the account to place the order. The service rep ended up creating a new account for the customer.Quote:
Originally Posted by DivaVocals
I'm in the process of cleaning up old site modules,etc. and I've come to COWOA.
I was wondering if someone can explain to me the reason why this module is important.
Sort of an odd request, and I don't want to waste anyone's time, it just seems like nearly a default module at this point, so I think I'm missing the reason why.
Most likely that is due to me not realizing what it actually does OR my old version operates incorrectly.
On my sites, COWOA operates just like a store account, except the customer doesn't create an initial password.
If they want to access their info they can use the password forgotten tool.
This means there is only one less form field for the customer to fill in (password), yet a whole lot of files changes to make the magic happen.
The only reason this helps conversions is if a customer is totally at a loss to login to their existing account they can just create a new one using the COWOA process.
Again, I must be missing something important here. How is COWOA even possible? The name and process implies that a customer will be able to create an order without giving any permanent information - as though they are shopping at a brick and mortar store.
I'll throw my $0.02 in. The main functional difference is the removal of the password field. The shopper still needs to enter ALL the other fields, billing address, shipping address, email, etc. It is because shoppers don't want an 'account'. It's a perception rather than reality because all of the information in a guest account is the same as a full account. Yes, the password field exists for full accounts, but it's irrelevant from the store owners perspective. The only real benefit I see is that shoppers do not need to remember a password to place a new order. They can order with only their email address.Quote:
Originally Posted by lindasdd
It is a lot of core edits (not offense to the author(s), it's necessary for the functionality) to achieve such a small benefit, IMHO. They need passwords for lots of sites, this is no different, and don't many people use password managers so they don't really need to remember the password anyway.
The use of a password manager is not a reason to (or not to) use this module.. It's debatable whether "most" people use these tools anyway.. (for example, someone logging in from a corporate computer is most likely NOT using a password manager)Quote:
Originally Posted by jeking
There are still a large number of online shoppers who believe that when shopping on sites that are not one of the big box retailers that by avoiding the creation of an account it makes the shopping experience "safer". My own sister still thinks that shopping on a site that uses PayPal versus a merchant account and gateway (i.e. Authorize.net) is a "safer/secure" shopping experience.. (and NOPE I haven't bothered wasting my time explaining to her why what she thinks is VERY WRONG..:laugh:)
Either way for these and other shoppers, COWOA gives them the peace of mind needed to put them on the path to conversion..
The entire point of COWOA is to allow customer a choice about whether or not to maintain an account on the site. If the customer feels "safer" not creating an account, then there is no blocking the path to conversion.. Additionally if a shopper feels that by not creating an account that the path to conversion is faster, then COWOA offers that too.. I personally would like to see COWOA modified to put the entire choice about creating an account or not as a decision point that should be made AFTER the sales transaction is complete.. After all WHY is the choice about creating an account REQUIRED BEFORE completing the sales transaction.. (but I digress)Quote:
Originally Posted by lindasdd
COWOA will be a built in functionality in the upcoming Zen Cart v1.6.. It is NOT part of the v1.5.x codebase.. Today if you want guest checkout capabilities, you will need the COWOA module..
Depends on how you code the site! the password field may look to be missing, but is auto created to protect the user non-standard account!Quote:
Originally Posted by jeking
For my site I step out of the box by providing the password field. If left empty, COWOA Account, filed in, Standard Account... by changing the password code and adding the input fields.Code:$password=zen_create_random_value(15, 'mixed');
Code:// COWOA password for account
$password = zen_db_prepare_input($_POST['password']);
$cowoa_account = 0;
if ($password == '') {
$password = zen_create_random_value((ENTRY_PASSWORD_MIN_LENGTH + 5), 'mixed');
$cowoa_account = 1;
}
if (strlen($password) < ENTRY_PASSWORD_MIN_LENGTH) {
$error = true;
$messageStack->add('no_account', ENTRY_PASSWORD_ERROR);
}
Agreed, but I've walked away from sites that forced me to create account even with what I know of the code.. Passwords wasn't the reason, no options was... IMHO.. I don't see problems with coding so user have options, I do see issues when sites don't provide options that I see as easy to code. I have over 50 site in my safe all with 12-16 char. hardened passwords.Quote:
It is a lot of core edits (not offense to the author(s), it's necessary for the functionality) to achieve such a small benefit, IMHO. They need passwords for lots of sites, this is no different, and don't many people use password managers so they don't really need to remember the password anyway.
From some experience on a few sites adding COWOA increases sales! Reason enough.Quote:
Originally Posted by lindasdd