COWOA (for ZC v1.5.x)

DivaVocals:

Finding that one of the on-screen messages may not be fully understood by all customers. It's the error message displayed when a customer attempts to use COWOA with an e-mail address that is linked to a standard customer account.

So I've revised it so it is much more detailed than the current message. Thought I'd share in case anyone else has the same experience.

Updated includes\languages\YOUR_TEMPLATE\english.php:
Change this:

define('ENTRY_EMAIL_ADDRESS_ERROR_EXISTS', 'Our system already has a record of that email address - please try logging in with that email address. If you do not use that address any longer you can correct it in the My Account area.');

> 
> To this:
> ```
define('ENTRY_EMAIL_ADDRESS_ERROR_EXISTS', 'You cannot use our "<strong>checkout without an account</strong>" feature with the e-mail address provided because our system already has a regular store account on file using that email address - please try logging in to our store with that email address. If you do not use that email address any longer you can correct it in the "<strong>My Account</strong>" area once logged in.');

Hi Diva,
thanks that make even better sense.

countrycharm:

Hi Diva,
thanks that make even better sense.You're welcome.. My client and I collaborated to come up with the revised message.. Fortunately THE customer who had the issue contacted my client when she couldn't complete her purchase.. I think the revised message will ensure that future customers don't abandon the cart because of an unclear error message..

Somewhere I read something about sending email in a COWOA shop.

Everytime a customer orders through COWOA he adds his emailaddress to the list. So when he ordered 6 times and I want to send him an email from Admin he is receiving 6 emails. I've read something about this but can't find it anymore. Someone else seen this thread?

Datax:

Somewhere I read something about sending email in a COWOA shop.

Everytime a customer orders through COWOA he adds his emailaddress to the list. So when he ordered 6 times and I want to send him an email from Admin he is receiving 6 emails. I've read something about this but can't find it anymore. Someone else seen this thread?

A customer who uses COWOA does so for a reason. They don't want their information stored on your site. That's one of the reasons for a customer checking out without an account, so they don't receive unsolicited e-mails? This could give those customers on your site an incentive to create an account, tell them you do this for registered customers only. NEVER send any additional information to a customer unless they sign up for your newsletter. Also, deleting them from the customers table is not the same as deleting them from the orders table. You can delete them as a customer but their order will remain and there would be no issues with duplicate emails, etc.

Thanx. You're right. Never send any additional info to a COWOA client.
The problem still occurs when a COWOA client later decides to make a full account with the same emailaddress.
Directly deleting the COWOA client is the solution.

I still would like a situation where only 1 email is send.

Datax:

Thanx. You're right. Never send any additional info to a COWOA client.
The problem still occurs when a COWOA client later decides to make a full account with the same emailaddress.
Directly deleting the COWOA client is the solution.

I still would like a situation where only 1 email is send.

You can always customize the code yourself.. or you can look into hiring someone to create this custom code for you..

DivaVocals:

You can always customize the code yourself.. or you can look into hiring someone to create this custom code for you..

Of course, but I thought I've seen it before. And why spend a lot of energy at something that already exists.

Datax:

Of course, but I thought I've seen it before. And why spend a lot of energy at something that already exists.

You can try this, change line 87 to 95 In the file includes/functions/audience.php, Changed function get_audience_sql_query to:

//if no match found against queries listed in database, then $selected_entry must be an email address
  if ($query_name=='' && $query_category=='email') {
        $cust_email_address = zen_db_prepare_input($selected_entry);
        $query_name   = $cust_email_address;
        $query_string = "select customers_firstname, customers_lastname, customers_email_address
                              from " . TABLE_CUSTOMERS . "
                              where customers_email_address = '" .     zen_db_input($cust_email_address) . "'  
                              and COWOA_account = '0'";
    }

By doing this Cowoa will not send any emails to Cowoa customers.

countrycharm:

You can try this, change line 87 to 95 In the file includes/functions/audience.php, Changed function get_audience_sql_query to:

//if no match found against queries listed in database, then $selected_entry must be an email address
if ($query_name=='' && $query_category=='email') {
$cust_email_address = zen_db_prepare_input($selected_entry);
$query_name = $cust_email_address;
$query_string = "select customers_firstname, customers_lastname, customers_email_address
from " . TABLE_CUSTOMERS . "
where customers_email_address = '" . zen_db_input($cust_email_address) . "'
and COWOA_account = '0'";
}

> 
> By doing this Cowoa will not send any emails to Cowoa customers.
But this also includes order e-mails too right???

DivaVocals:

But this also includes order e-mails too right???

Which order emails do you mean?

It seems to work

If you add this in de query around line 55 also, the COWOA clients are removed from the dropdown field too.

I forgot to mention. It has to be "and COWOA_account = '0' "

Still didn't find a problem with the order emails??

Datax:

Which order emails do you mean?order confirmation, updates..

DivaVocals:

order confirmation, updates..

As far as I understand this file only concerns modules with email dropdown field.
Tried order emails and everything seems to work fine.

Thanx Country & Diva

DivaVocals:

But this also includes order e-mails too right???
Diva the order emails still work like they suppose to.

Datax
If you add this in de query around line 55 also, the COWOA clients are removed from the dropdown field too.
"and COWOA_account = '0' "

Thank you, you are right about the COWOA extra email clients being removed from the dropdown send email field.

joejoejoe:

Well that error message I got about the unexpected end didn't go away when I put the updated time_out.php file in. I just checked and after each sale I am still getting it (PHP Parse error: syntax error, unexpected $end in )- but now it says line 19 instead of line 20 and line 19 is the last line of the file, which I uploaded straight from the unzipped download of v2.3 Line 19 says:

define('TEXT_PASSWORD_FORGOTTEN', 'Forgot Your Password?')

And I opened it with Crimson editor just to check and there are no extra spaces or lines after that )

DrByte:

"unexpected $end" is almost always caused by unmatched/unclosed parentheses or braces, such as in an IF statement or WHILE or FOR or SWITCH loop, or an incomplete class/function declaration (such as would happen if you were editing a class or function file and remove a closing brace, or forget to add a closing brace to an IF statement you're adding, etc). Basically it's a programming error in your customized code.

Installing this last night for a client.. Ran into this issue last night.. (hadn't run into this issue hence my previous incorrect response) DrByte was on the money with regards to the cause. There is a missing semi colon on line 19 of the time_out.php.
change line 19 from:

define('TEXT_PASSWORD_FORGOTTEN', 'Forgot Your Password?')

to:

define('TEXT_PASSWORD_FORGOTTEN', 'Forgot Your Password?');

and poof the problem goes away..

DivaVocals:

Finding that one of the on-screen messages may not be fully understood by all customers. It's the error message displayed when a customer attempts to use COWOA with an e-mail address that is linked to a standard customer account.

So I've revised it so it is much more detailed than the current message. Thought I'd share in case anyone else has the same experience.

Updated includes\languages\YOUR_TEMPLATE\english.php:
Change this:

define('ENTRY_EMAIL_ADDRESS_ERROR_EXISTS', 'Our system already has a record of that email address - please try logging in with that email address. If you do not use that address any longer you can correct it in the My Account area.');

> 
> To this:
> ```
define('ENTRY_EMAIL_ADDRESS_ERROR_EXISTS', 'You cannot use our "<strong>checkout without an account</strong>" feature with the e-mail address provided because our system already has a regular store account on file using that email address - please try logging in to our store with that email address. If you do not use that email address any longer you can correct it in the "<strong>My Account</strong>" area once logged in.');

countrycharm:

Hi Diva,
thanks that make even better sense.

DivaVocals:

You're welcome.. My client and I collaborated to come up with the revised message.. Fortunately THE customer who had the issue contacted my client when she couldn't complete her purchase.. I think the revised message will ensure that future customers don't abandon the cart because of an unclear error message..

So I've been doing more work refining the on-screen text and error messages for this module.. In testing this module, my client and I both felt that some of them are a little awkwardly worded. I also realized that the Standard and COWOA error message I posted my corrections for previously should be separated and not shared. My client and I have been doing some informal research as to how similar guest checkout features are used with other online retailers (with a particular eye on some of the larger online retailers). My client and I are also gathering feedback from some of his customers who agreed to help us with a VERY informal usability study.

The purpose of this effort was to come up with clearer and more consistent on-screen messages for COWOA. I made a number of changes to several COWOA files to implement the changesIn this effort, I also found one instance of hard coded text in one of the COWOA files which I also corrected to use a language file define.

Wanted to share the changes I've made as a result. It's too much to post all the changes inside a post so I've uploaded screenprints of the changes I made. I will attache a zip file of the modified files my next post.. Would like to suggest that these changes (or similar ones) should be part of the next COWOA release. I would be happy to bundle these changes up, but wanted to throw it out to the community for opinions.. (and I don't want to step on my friend CountryCharm's toes!:smile:)

Files modified:
includes/languages/YOUR_TEMPLATE/english.php
includes/languages/english/YOUR_TEMPLATE/time_out.php
includes/languages/english/YOUR_TEMPLATE/login.php
includes/modules/YOUR_TEMPLATE/no_account.php
includes/templates/YOUR_TEMPLATE/templates/tpl_login_default.php

I also added an additional arrow image thought others might find it useful so I've included this as well
New_Installation\Optional_Arrows\arrow_checkout16.png

DivaVocals:

So I've been doing more work refining the on-screen text and error messages for this module.. In testing this module, my client and I both felt that some of them are a little awkwardly worded. I also realized that the Standard and COWOA error message I posted my corrections for previously should be separated and not shared. My client and I have been doing some informal research as to how similar guest checkout features are used with other online retailers (with a particular eye on some of the larger online retailers). My client and I are also gathering feedback from some of his customers who agreed to help us with a VERY informal usability study.

The purpose of this effort was to come up with clearer and more consistent on-screen messages for COWOA. I made a number of changes to several COWOA files to implement the changesIn this effort, I also found one instance of hard coded text in one of the COWOA files which I also corrected to use a language file define.

Wanted to share the changes I've made as a result. It's too much to post all the changes inside a post so I've uploaded screenprints of the changes I made. I will attache a zip file of the modified files my next post.. Would like to suggest that these changes (or similar ones) should be part of the next COWOA release. I would be happy to bundle these changes up, but wanted to throw it out to the community for opinions.. (and I don't want to step on my friend CountryCharm's toes!:smile:)

Files modified:
includes/languages/YOUR_TEMPLATE/english.php
includes/languages/english/YOUR_TEMPLATE/time_out.php
includes/languages/english/YOUR_TEMPLATE/login.php
includes/modules/YOUR_TEMPLATE/no_account.php
includes/templates/YOUR_TEMPLATE/templates/tpl_login_default.php

I also added an additional arrow image thought others might find it useful so I've included this as well
New_Installation\Optional_Arrows\arrow_checkout16.png Modified files in a zip

Trashed my admin and template also no option to switch it on in admin. Should be an easier install.

Just install Fast and Easy Checkout. The installation is simpler and it includes COWOA already.

typecast:

Trashed my admin and template also no option to switch it on in admin. Should be an easier install.so you posted in the support thread just to gripe?? Okay.. well since you provided NO DETAILS there's no way to know how you did that. This install is no more complicated than any other module.. most issues usually end up being due to install errors.. but since you only were here in the SUPPORT. THREAD to post a complaint not ask for help it doesn't matter..

typecast:

Just install Fast and Easy Checkout. The installation is simpler and it includes COWOA already.lol.. simpler eh.. okay.. yep it sure does include nearly the SAME COWOA files/code.. just no support and wait until you find out other modules don't play nicely with it.. but you enjoy!!