COWOA (for ZC v1.5.x)

Quote:

---

Originally Posted by 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:

Code:

---

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:

Code:

---

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.

Quote:

---

Originally Posted by 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?

Quote:

---

Originally Posted by 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.

Quote:

---

Originally Posted by 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..

Quote:

---

Originally Posted by 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.

Quote:

---

Originally Posted by 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:

PHP Code:

---

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

Quote:

---

Originally Posted by countrycharm

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

PHP Code:

---

//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???

Quote:

---

Originally Posted by 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??

Quote:

---

Originally Posted by Datax

Which order emails do you mean?

---

order confirmation, updates..

Quote:

---

Originally Posted by 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

Quote:

---

Originally Posted by DivaVocals

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

---

Diva the order emails still work like they suppose to.

Quote:

---

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.

Quote:

---

Originally Posted by 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 )

---

Quote:

---

Originally Posted by 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:

Code:

---

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

---

to:

Code:

---

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

---

and poof the problem goes away..

Quote:

---

Originally Posted by 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:

Code:

---

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:

Code:

---

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

---

---

Quote:

---

Originally Posted by countrycharm

Hi Diva,
thanks that make even better sense.

---

Quote:

---

Originally Posted by 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

Quote:

---

Originally Posted by 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.

Quote:

---

Originally Posted by 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..

Quote:

---

Originally Posted by 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!!

Quote:

---

Originally Posted by 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

---

No problem Diva, since you have change and modified the code your welcome to upload the update. Just change the version number to 2.4 when doing so. I will continue to help support this thread when I have time.

Quote:

---

Originally Posted by countrycharm

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

PHP Code:

---

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

---

Quote:

---

Originally Posted by Datax

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.

---

Should this be added to COWOA's core?? if so, I have a few questions:
Can someone share with me what the change at line 55 should look like (wanna test it)
Help me to fully understand what this change will do exactly.. When you say prevent COWOA from sending e-mails, which e-mails??

Lastly I think that there is one more change that COWOA should include. Sideboxes should be turned off during the checkout process to minimize customer distractions during checkout. (I believe FEAC includes this as part of it's default setup) looking at some of the larger e-commerce retailers, they too turn off "distractions" during checkout... That said I will be adding the following change to the COWOA version I will be submitting:
in the includes/templates/YOUR_TEMPLATE/common/tpl_main_page.php file:

Code:

---

  // the following IF statement can be duplicated/modified as needed to set additional flags
if (in_array($current_page_base,explode(",",'account,account_password,account_edit,address_book,account_history_info,account_newsletters,account_notifications,account_history,login,logoff,checkout_shipping,checkout_shipping_address,checkout_payment,checkout_payment_address,checkout_confirmation,checkout_process,checkout_success,shopping_cart,address_book_process')) ) {
    $flag_disable_right = true;
    $flag_disable_left = true;

---

Quote:

---

Originally Posted by DivaVocals

Lastly I think that there is one more change that COWOA should include. Sideboxes should be turned off during the checkout process to minimize customer distractions during checkout. (I believe FEAC includes this as part of it's default setup) looking at some of the larger e-commerce retailers, they too turn off "distractions" during checkout... That said I will be adding the following change to the COWOA version I will be submitting:
in the includes/templates/YOUR_TEMPLATE/common/tpl_main_page.php file:

---

Please make this an option, not a default setting.

Quote:

---

Originally Posted by dw08gm

Please make this an option, not a default setting.

---

Wasn't planning on making it a default feature.. Will be including it because its good practice and one that many of the larger retailers use for the reasons that many of the Zen Cart powerhouses/gurus suggest it.. If the reason that shopowners use COWOA is to decrease cart abandonment, and to increase sales conversions, this is simple low hanging fruit that should be included with COWOA..

Quote:

---

Originally Posted by DivaVocals

Wasn't planning on making it a default feature.. Will be including it because its good practice and one that many of the larger retailers use for the reasons that many of the Zen Cart powerhouses/gurus suggest it.. If the reason that shopowners use COWOA is to decrease cart abandonment, and to increase sales conversions, this is simple low hanging fruit that should be included with COWOA..

---

:thumbsup: been using that edit since I started using zencart looks sooooo much neater.

Quote:

---

Originally Posted by discoverytdi

:thumbsup: been using that edit since I started using zencart looks sooooo much neater.

---

yep I agree.. my edit is a tad more aggressive than most. I went through a painstaking process of reviewing the entire checkout process and all the pages that a customer can get to from each step. I added each one of those pages to the list of pages to turn sideboxes off. Now the checkout process is lean and mean..

Quote:

---

Originally Posted by DivaVocals

yep I agree.. my edit is a tad more aggressive than most. I went through a painstaking process of reviewing the entire checkout process and all the pages that a customer can get to from each step. I added each one of those pages to the list of pages to turn sideboxes off. Now the checkout process is lean and mean..

---

Ditto, me too. Much neater.

Quote:

---

Originally Posted by countrycharm

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

PHP Code:

---

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

---

Back in July 2010 some were getting a duplicate email address/duplicate email send bug.. JTheed in one of his post shared the fix if you were getting them. Unless you are getting them also I wouldn't worry about this.

Quote:

---

Originally Posted by Datax

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 understand what he was talking about sorry for not explaining it.

Whenever a customer check out using the guest checkout his email address is saved.
When the same customer returns and use the guest checkout again there email address is saved again.

If he decides to make and permanent account it is saved again the difference is you can not use the guest checkout again unless they use a different email address.
Each time the he/she returns and use the guest checkout there email address is saved in the database.

What is the point here if you need to send that customer a email from under admin/tools send email there email address is there by my example under the drop-down menu 3 times. The more that customer uses the guest checkout the more there email address will show up when sending emails.

If you add this code to line 57 in the includes/functions/audience.php
"and COWOA_account = '0' " .

the cowoa customer email address will not show but 1 time. I hope that makes since to you.

Quote:

---

Originally Posted by DivaVocals

Should this be added to COWOA's core?? if so, I have a few questions:
Can someone share with me what the change at line 55 should look like (wanna test it)
Help me to fully understand what this change will do exactly.. When you say prevent COWOA from sending e-mails, which e-mails??

Lastly I think that there is one more change that COWOA should include. Sideboxes should be turned off during the checkout process to minimize customer distractions during checkout. (I believe FEAC includes this as part of it's default setup) looking at some of the larger e-commerce retailers, they too turn off "distractions" during checkout... That said I will be adding the following change to the COWOA version I will be submitting:
in the includes/templates/YOUR_TEMPLATE/common/tpl_main_page.php file:

Code:

---

  // the following IF statement can be duplicated/modified as needed to set additional flags
if (in_array($current_page_base,explode(",",'account,account_password,account_edit,address_book,account_history_info,account_newsletters,account_notifications,account_history,login,logoff,checkout_shipping,checkout_shipping_address,checkout_payment,checkout_payment_address,checkout_confirmation,checkout_process,checkout_success,shopping_cart,address_book_process')) ) {
    $flag_disable_right = true;
    $flag_disable_left = true;

---

---

This is how I have set up my regular checkout. Yes I think it would be a good idea. Yes it have being proven the less distraction a customer has the more likely he will finish the checkout process.

Here the whole code staring on line 53 and ending with line 64 includes/functions/audience.php

Quote:

---

//if this is called by an emailing module which offers individual customers as an option, add all customers email addresses as well.
if ($query_category=='email') {
$customers_values = $db->Execute("select customers_email_address, customers_firstname, customers_lastname " .
"from " . TABLE_CUSTOMERS . " WHERE customers_email_format != 'NONE' " .
"and COWOA_account = '0' " .
"order by customers_lastname, customers_firstname, customers_email_address");
while(!$customers_values->EOF) {
$audience_list[] = array('id' => $customers_values->fields['customers_email_address'],
'text' => $customers_values->fields['customers_lastname'] . ', ' . $customers_values->fields['customers_firstname'] . ' (' . $customers_values->fields['customers_email_address'] . ')');
$customers_values->MoveNext();
}
}

---

Quote:

---

Originally Posted by countrycharm

Back in July 2010 some were getting a duplicate email address/duplicate email send bug.. JTheed in one of his post shared the fix if you were getting them. Unless you are getting them also I wouldn't worry about this.

---

But it seems to me that this isn't as much of a bug as it is a function that needs to be modified if you have COWOA installed.. Based on the original post which necessitated this fix, this would still be an issue if a customer uses COWOA and later signs up for an account.

Quote:

---

If a customer checks out without an account, then later signs up for a full account, you have two accounts with the same email address.
If I then send a gift certificate from admin, the customer gets 2 gift certificates with 2 different redemption codes!
You may be asking yourself why am I sending gift certificates? Well, I have a competition running where the prize is £30 of gift certificates.

---

Seems that this code should be part of the core to prevent this from happening..

Quote:

---

Originally Posted by countrycharm

I understand what he was talking about sorry for not explaining it.

Whenever a customer check out using the guest checkout his email address is saved.
When the same customer returns and use the guest checkout again there email address is saved again.

If he decides to make and permanent account it is saved again the difference is you can not use the guest checkout again unless they use a different email address.
Each time the he/she returns and use the guest checkout there email address is saved in the database.

What is the point here if you need to send that customer a email from under admin/tools send email there email address is there by my example under the drop-down menu 3 times. The more that customer uses the guest checkout the more there email address will show up when sending emails.

If you add this code to line 57 in the includes/functions/audience.php
"and COWOA_account = '0' " .

the cowoa customer email address will not show but 1 time. I hope that makes since to you.

---

Makes perfect sense, and thanks for the explanation.. and it seems that this too needs to be a part of the core COWOA code for the reasons you explained. However would it not make sense that the dropdown only show one instance of the e-mail address versus hiding all the COWOA customers (as the suggested code would do).

Quote:

---

Originally Posted by countrycharm

This is how I have set up my regular checkout. Yes I think it would be a good idea. Yes it have being proven the less distraction a customer has the more likely he will finish the checkout process.

---

Gonna remove the checkout_success page though.. No reason to hide the sideboxes once the sales transaction is complete..

Quote:

---

Originally Posted by DivaVocals

But it seems to me that this isn't as much of a bug as it is a function that needs to be modified if you have COWOA installed.. Based on the original post which necessitated this fix, this would still be an issue if a customer uses COWOA and later signs up for an account.



Seems that this code should be part of the core to prevent this from happening..

Makes perfect sense, and thanks for the explanation.. and it seems that this too needs to be a part of the core COWOA code for the reasons you explained. However would it not make sense that the dropdown only show one instance of the e-mail address versus hiding all the COWOA customers (as the suggested code would do).


Gonna remove the checkout_success page though.. No reason to hide the sideboxes once the sales transaction is complete..

---

By adding the code to line 57 if the cowoa customer makes a permanent account with that same email address it would only show one instance of there email address in the dropdown regardless cowoa, permanent.

Quote:

---

Gonna remove the checkout_success page though.. No reason to hide the sideboxes once the sales transaction is complete..

---

Agreed

While your discussing the improvement of the customer experience of cowoa I'll put my 2cents worth in.
Is it possible to move the Terms and Conditions acknowledgement box to the bottom of the page say under the Special Instructions Order Comments box, even I miss the T&C box when testing :lamo: and maybe a home button at the bottom of the Order Complete page just a thought

Quote:

---

Originally Posted by discoverytdi

While your discussing the improvement of the customer experience of cowoa I'll put my 2cents worth in.
Is it possible to move the Terms and Conditions acknowledgement box to the bottom of the page say under the Special Instructions Order Comments box, even I miss the T&C box when testing :lamo: and maybe a home button at the bottom of the Order Complete page just a thought

---

The changes I am planning to submit are not about layout preferences as much as they are about providing clearer on-screen and error messages, and providing admin configurable options to make COWOA deliver what it promises (decrease cart abandonment, and to increase sales conversions)

What you are talking about is more of a layout preference, and IMHO, these kind of changes should be left to the shopowner to make (most are super easy to do). Just because I prefer the COWOA fieldset to appear ABOVE the new account and login fieldsets because my clients would prefer that clients use COWOA, does not mean everyone is going to want this same layout. So I don't plan to submit the 2.4 update with my preferred layout as part of the fileset. It's an EASY enough change for me to make on my own without imposing my preference on the community.

As for a home button on the checkout success page, again this is something a shopowner can easily add themselves if they want it. It's a preference and shouldn't be part of the core code IMHO.. As an aside, if the site has sideboxes, a top menu and a footer menu is this really needed??

Still refining the on-screen messages. Thanks to Delia Wilson I found two more.

1. On the payment page the customer is prompted to continue to step 4 to "to confirm your order". Step 4 is actually the REVIEW order step. So I will edit: includes/languages/english/YOUR_TEMPLATE/checkout_payment.php so that the text reads "- to review your order."
2. Gonna make a small change to the includes/languages/english/custom_template/login.php file so that the PayPal Express text reads (the part in red is the addition):
   Have a PayPal account? Want to pay quickly with a credit card? Use the PayPal button below to use the Express Checkout option. No PayPal account is required to use your credit card.

Quote:

---

Originally Posted by DivaVocals

Still refining the on-screen messages. Thanks to Delia Wilson I found two more.

1. On the payment page the customer is prompted to continue to step 4 to "to confirm your order". Step 4 is actually the REVIEW order step. So I will edit: includes/languages/english/YOUR_TEMPLATE/checkout_payment.php so that the text reads "- to review your order."
2. Gonna make a small change to the includes/languages/english/custom_template/login.php file so that the PayPal Express text reads (the part in red is the addition):
   Have a PayPal account? Want to pay quickly with a credit card? Use the PayPal button below to use the Express Checkout option. No PayPal account is required to use your credit card.

---

I think the paypal express edit is a brilliant idea I've edited the paypal button on the cart contents page to read No Account Required in bold, you won't believe the number of times customers ring me because they think they need an account with paypal.

Quote:

---

Originally Posted by discoverytdi

I think the paypal express edit is a brilliant idea I've edited the paypal button on the cart contents page to read No Account Required in bold, you won't believe the number of times customers ring me because they think they need an account with paypal.

---

Yep.. It's totally an excellent idea!!

There's a few other minor changes Delia did that also make sense from a usability POV.. The next steps text really should be next to the "Continue" button and not on the far left of the page. So I'll make those changes as well..

Also in going through the two different checkout processes, I noticed a number of other inconsistencies that I will be correcting:

1. The order step numbers are inconsistent in the standard check out flow versus the COWOA flow. In the standard checkout it shows that there are only 3 steps, but in the COWOA flow there are 5 steps. (That's because the confirmation step is counted in the COWOA flow, but not in the standard flow) So I've corrected the text in the standard flow to reflect that there are FOUR steps not THREE.
2. I also noted that in the final confirmation step in BOTH flows and the billing step of the COWOA flow, the heading "Step # or #" is missing. So I've corrected the package to include the same step heading text as the other pages in the checkout process.

I'm continuing to test and review the workflow for inconsistencies and other usability issues.. Hope to have this all finalized and submitted today..

More modifications to share..

If you are using the CSS Horizontal Dropdown Menu With jquery module with COWOA, there are some changes needed so that it works correctly with COWOA. in the file includes/templates/YOUR_TEMPLATE/common/tpl_drop_menu.php on find lines 104-113

Code:

---

              <ul class="level2">
                <?php if ($_SESSION['customer_id']) { ?>
                <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT, '', 'SSL'); ?>"><?php echo HEADER_TITLE_MY_ACCOUNT; ?></a></li>
                <li><a href="<?php echo zen_href_link(FILENAME_LOGOFF, '', 'SSL'); ?>"><?php echo HEADER_TITLE_LOGOFF; ?></a></li>
                <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT_NEWSLETTERS, '', 'SSL'); ?>"><?php echo HEADER_TITLE_NEWSLETTERS; ?></a></li>
                <?php } else { ?>
                <li><a href="<?php echo zen_href_link(FILENAME_LOGIN, '', 'SSL'); ?>"><?php echo HEADER_TITLE_LOGIN; ?></a></li>
                <li><a href="<?php echo zen_href_link(FILENAME_CREATE_ACCOUNT, '', 'SSL'); ?>"><?php echo HEADER_TITLE_CREATE_ACCOUNT; ?></a></li>
                <?php } ?>
              </ul>

---

Replace with:

Code:

---

              <ul class="level2">
                <?php if (($_SESSION['customer_id']) && (!$_SESSION['COWOA']=='True')) { ?>
                <li><a href="<?php echo zen_href_link(FILENAME_LOGOFF, '', 'SSL'); ?>"><?php echo HEADER_TITLE_LOGOFF; ?></a></li>
                <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT, '', 'SSL'); ?>"><?php echo HEADER_TITLE_MY_ACCOUNT; ?></a></li>
                <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT_NEWSLETTERS, '', 'SSL'); ?>"><?php echo HEADER_TITLE_NEWSLETTERS; ?></a></li>
<?php
      } else {
        if (STORE_STATUS == '0') {
?>

                <li><a href="<?php echo zen_href_link(FILENAME_LOGIN, '', 'SSL'); ?>"><?php echo HEADER_TITLE_LOGIN; ?></a></li>
                <li><a href="<?php echo zen_href_link(FILENAME_CREATE_ACCOUNT, '', 'SSL'); ?>"><?php echo HEADER_TITLE_CREATE_ACCOUNT; ?></a></li>
                <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT_NEWSLETTERS, '', 'SSL'); ?>"><?php echo HEADER_TITLE_NEWSLETTERS; ?></a></li>
                <?php } } ?>
              </ul>

---

The order of items on the menu has been modified a little so that there is a more consistent layout of the menu items. Most importantly the menu will now work correctly with COWOA.

Or if you are using the Pure CSS Mega Menu module Or any template by Picaflor Azul which uses this menu, these are the changes needed for it to work with COWOA:

in the file includes/templates/YOUR_TEMPLATE/common/tpl_mega_menu.php on find lines 190-197

Code:

---

            <?php if ($_SESSION['customer_id']) { ?>
                    <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT, '', 'SSL'); ?>"><?php echo HEADER_TITLE_MY_ACCOUNT; ?></a></li>
                    <li><a href="<?php echo zen_href_link(FILENAME_LOGOFF, '', 'SSL'); ?>"><?php echo HEADER_TITLE_LOGOFF; ?></a></li>
                    <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT_NEWSLETTERS, '', 'SSL'); ?>"><?php echo TITLE_NEWSLETTERS; ?></a></li>
                    <?php } else { ?>
                    <li><a href="<?php echo zen_href_link(FILENAME_LOGIN, '', 'SSL'); ?>"><?php echo HEADER_TITLE_LOGIN; ?></a></li>
                    <li><a href="<?php echo zen_href_link(FILENAME_CREATE_ACCOUNT, '', 'SSL'); ?>"><?php echo HEADER_TITLE_CREATE_ACCOUNT; ?></a></li>
                    <?php } ?>

---

Change to:

Code:

---

            <?php if (($_SESSION['customer_id']) && (!$_SESSION['COWOA']=='True')) { ?>
                    <li><a href="<?php echo zen_href_link(FILENAME_LOGOFF, '', 'SSL'); ?>"><?php echo HEADER_TITLE_LOGOFF; ?></a></li>
                    <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT, '', 'SSL'); ?>"><?php echo HEADER_TITLE_MY_ACCOUNT; ?></a></li>
                    <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT_NEWSLETTERS, '', 'SSL'); ?>"><?php echo TITLE_NEWSLETTERS; ?></a></li>
                    <?php
                  } else {
                    if (STORE_STATUS == '0') {
            ?>
                    <li><a href="<?php echo zen_href_link(FILENAME_LOGIN, '', 'SSL'); ?>"><?php echo HEADER_TITLE_LOGIN; ?></a></li>
                    <li><a href="<?php echo zen_href_link(FILENAME_CREATE_ACCOUNT, '', 'SSL'); ?>"><?php echo HEADER_TITLE_CREATE_ACCOUNT; ?></a></li>
                    <li><a href="<?php echo zen_href_link(FILENAME_ACCOUNT_NEWSLETTERS, '', 'SSL'); ?>"><?php echo TITLE_NEWSLETTERS; ?></a></li>
                    <?php } } ?>

---

Nice work Diva, your coming along very well. You know that Cowao will be a built in feature in zen cart 1.6.0 While updating cowoa is a good thing I really wouldn't go to extreme if you know what I mean. I know how you are, getter done................:D

Quote:

---

Originally Posted by countrycharm

Nice work Diva, your coming along very well. You know that Cowao will be a built in feature in zen cart 1.6.0 While updating cowoa is a good thing I really wouldn't go to extreme if you know what I mean. I know how you are, getter done................:D

---

Just because it's going to be built into Zen Cart v1.6 doesn't mean I would use it as is if they are using an older (outdated) version of COWOA.. I do know they do plan to have it built in to v1.6, but if the version included in Zen Cart v1.6 does not include the changes I am making, I would still make these exact changes anyway. My client and his customer's feedback was invaluable in nailing down the tweaks I am making to this module. From a consistency, usability and functional POV they are very much needed. I would hope that the admins would look to see what the LATEST version of COWOA is before releasing v1.6 and consider incorporating the latest changes into the v1.6 core code.

If these changes are not included in the Zen Cart v1.6 core that's fine.. It won't deter me from continuing to work on these improvements/modifications and sharing them with the community. Just like Super Orders is an enhanced version of the default order management, and Improved Sitemap is an enhanced version of the default Zen Cart sitemap, there's no reason there can't be an "Improved/Super COWOA" module.

Quote:

---

Originally Posted by DivaVocals

Just because it's going to be built into Zen Cart v1.6 doesn't mean I would use it as is if they are using an older (outdated) version of COWOA.. I do know they do plan to have it built in to v1.6, but if the version included in Zen Cart v1.6 does not include the changes I am making, I would still make these exact changes anyway. My client and his customer's feedback was invaluable in nailing down the tweaks I am making to this module. From a consistency, usability and functional POV they are very much needed. I would hope that the admins would look to see what the LATEST version of COWOA is before releasing v1.6 and consider incorporating the latest changes into the v1.6 core code.

If these changes are not included in the Zen Cart v1.6 core that's fine.. It won't deter me from continuing to work on these improvements/modifications and sharing them with the community. Just like Super Orders is an enhanced version of the default order management, and Improved Sitemap is an enhanced version of the default Zen Cart sitemap, there's no reason there can't be an "Improved/Super COWOA" module.

---

It is already included in the 1.6 version available on github.

Quote:

---

Originally Posted by Design75

It is already included in the 1.6 version available on github.

---

I understand that.. I too am following the progress of v1.6 on github..

Quote:

---

CHANGE-303 Add COWOA Contribution

---

They have integrated COWOA v2.2 as of 5 months ago.

Quote:

---

@version $Id: Integrated COWOA v2.2 - 2007 - 2012

---

However, what's NOT included in v1.6 as of today are the latest version COWOA updates (v2.3 and soon v2.4) and what I stated is that I hope they will include the LATEST version before the release and hopefully they will include the changes I will be submitting today as part of the COWOA integration into the Zen Cart v1.6 codebase. THAT'S what I was making reference to in my post.. So I will say this again..

Quote:

---

If the version included in Zen Cart v1.6 does not include the changes I am making, I would still make these exact changes anyway. My client and his customer's feedback was invaluable in nailing down the tweaks I am making to this module. From a consistency, usability and functional POV they are very much needed. I would hope that the admins would look to see what the LATEST version of COWOA is before releasing v1.6 and consider incorporating the latest changes into the v1.6 core code.

---

If Zen Cart v1.6 releases with the COWOA v2.2 code as part of the codebase, I would STILL make these changes and I would STILL share them with the community.. Hope that makes what i am saying a lot clearer now..

Quote:

---

Originally Posted by DivaVocals

I understand that.. I too am following the progress of v1.6 on github..


They have integrated COWOA v2.2 as of 5 months ago.


However, what's NOT included in v1.6 as of today are the latest version COWOA updates (v2.3 and soon v2.4) and what I stated is that I hope they will include the LATEST version before the release and hopefully they will include the changes I will be submitting today as part of the COWOA integration into the Zen Cart v1.6 codebase. THAT'S what I was making reference to in my post.. So I will say this again..



If Zen Cart v1.6 releases with the COWOA v2.2 code as part of the codebase, I would STILL make these changes and I would STILL share them with the community.. Hope that makes what i am saying a lot clearer now..

---

**nods in agreement**:yes:

Quote:

---

Originally Posted by DivaVocals

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:

Code:

---

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

---

to:

Code:

---

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

---

and poof the problem goes away..

---

Quote:

---

Originally Posted by 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

---

Quote:

---

Originally Posted by DivaVocals

Lastly I think that there is one more change that COWOA should include. Sideboxes should be turned off during the checkout process to minimize customer distractions during checkout. (I believe FEAC includes this as part of it's default setup) looking at some of the larger e-commerce retailers, they too turn off "distractions" during checkout... That said I will be adding the following change to the COWOA version I will be submitting:
in the includes/templates/YOUR_TEMPLATE/common/tpl_main_page.php file:
(edited from the original post)

Code:

---

  // the following IF statement can be duplicated/modified as needed to set additional flags
if (in_array($current_page_base,explode(",",'account,account_password,account_edit,address_book,account_history_info,account_newsletters,account_notifications,account_history,login,logoff,checkout_shipping,checkout_shipping_address,checkout_payment,checkout_payment_address,checkout_confirmation,checkout_process,shopping_cart,address_book_process')) ) {
    $flag_disable_right = true;
    $flag_disable_left = true;

---

---

Quote:

---

Originally Posted by DivaVocals

Still refining the on-screen messages. Thanks to Delia Wilson I found two more.

1. On the payment page the customer is prompted to continue to step 4 to "to confirm your order". Step 4 is actually the REVIEW order step. So I will edit: includes/languages/english/YOUR_TEMPLATE/checkout_payment.php so that the text reads "- to review your order."
2. Gonna make a small change to the includes/languages/english/custom_template/login.php file so that the PayPal Express text reads (the part in red is the addition):
   Have a PayPal account? Want to pay quickly with a credit card? Use the PayPal button below to use the Express Checkout option. No PayPal account is required to use your credit card.

---

Quote:

---

Originally Posted by DivaVocals

There's a few other minor changes Delia did that also make sense from a usability POV.. The next steps text really should be next to the "Continue" button and not on the far left of the page. So I'll make those changes as well..

Also in going through the two different checkout processes, I noticed a number of other inconsistencies that I will be correcting:

1. The order step numbers are inconsistent in the standard check out flow versus the COWOA flow. In the standard checkout it shows that there are only 3 steps, but in the COWOA flow there are 5 steps. (That's because the confirmation step is counted in the COWOA flow, but not in the standard flow) So I've corrected the text in the standard flow to reflect that there are FOUR steps not THREE.
2. I also noted that in the final confirmation step in BOTH flows and the billing step of the COWOA flow, the heading "Step # or #" is missing. So I've corrected the package to include the same step heading text as the other pages in the checkout process.

I'm continuing to test and review the workflow for inconsistencies and other usability issues.. Hope to have this all finalized and submitted today..

---

Okay I think I got it all updated, tested, and documented.. I summarized all the threads I posted which covers most of the updates I made above. I'm wiped out right now and I will bundle this all up and submit it in the morning..

Hi

Thanks for the module, I have a problem though.

I have merged all files (hopefully correctly) and installed the SQL patch, under Cowoa Configuration I get the Title, Value and Action headings but no content there at all, I can't see any options to turn it on or off etc.

I saw someone had this problem in the old support thread for 1.3.9 and I tried their fix but the database entries were already set up properly according to that fix so I can't find the solution.

Any help would be fantastic.

Oh and btw I'm on V1.5.0

Quote:

---

Originally Posted by PomND

Hi

Thanks for the module, I have a problem though.

I have merged all files (hopefully correctly) and installed the SQL patch, under Cowoa Configuration I get the Title, Value and Action headings but no content there at all, I can't see any options to turn it on or off etc.

I saw someone had this problem in the old support thread for 1.3.9 and I tried their fix but the database entries were already set up properly according to that fix so I can't find the solution.

Any help would be fantastic.

Oh and btw I'm on V1.5.0

---

Run the Uninstall_COWOA.sql then reinstall the COWOA_Full_Install.sql and see what happens.

Quote:

---

Originally Posted by countrycharm

Run the Uninstall_COWOA.sql then reinstall the COWOA_Full_Install.sql and see what happens.

---

Thanks that made the options come up again (thought I'd tried that!)

Now, however, when I select COWOA from the checkout section it goes to the billing page and shows the progress thing at the top but everything is blank below it, no where to put in address etc or go onto the next stage.

I checked the error log files and it comes back with this:

"[12-Feb-2013 09:34:29 Europe/London] PHP Warning: strlen() expects parameter 1 to be string, array given in /home/zoosp198/public_html/shop/includes/functions/functions_general.php on line 153


[12-Feb-2013 09:34:29 Europe/London] PHP Warning: strlen() expects parameter 1 to be string, array given in /home/zoosp198/public_html/shop/includes/functions/functions_general.php on line 153


[12-Feb-2013 09:34:29 Europe/London] PHP Warning: strlen() expects parameter 1 to be string, array given in /home/zoosp198/public_html/shop/includes/functions/functions_general.php on line 153


[12-Feb-2013 09:34:30 Europe/London] PHP Warning: strlen() expects parameter 1 to be string, array given in /home/zoosp198/public_html/shop/includes/functions/functions_general.php on line 153


[12-Feb-2013 09:34:30 Europe/London] PHP Warning: strlen() expects parameter 1 to be string, array given in /home/zoosp198/public_html/shop/includes/functions/functions_general.php on line 153
"

Is that related?

Thanks for your help.

I fixed that PHP warning, it was nothing related I don't think as the problem is still there.

I have another error log that I think is more related (hopefully)

[12-Feb-2013 09:36:01 Europe/London] PHP Parse error: syntax error, unexpected $end in /home/zoosp198/public_html/shop/includes/templates/zoosportwhite/templates/tpl_modules_no_account.php on line 318

And when I go to look at that file this is the code that comes up towards the end:

Code:

---

<fieldset id="noAccountReferral">
<legend><?php echo TABLE_HEADING_REFERRAL_DETAILS; ?></legend>
<label class="inputLabel" for="customers_referral"><?php echo ENTRY_CUSTOMERS_REFERRAL; ?></label>
<?php echo zen_draw_input_field('customers_referral', '', zen_set_field_length(TABLE_CUSTOMERS, 'customers_referral', '15') . ' id="customers_referral"'); ?>
<br class="clearBoth" />
</fieldset>
<?php } ?>

---

The very last line of that is line 318 and is the last line of the doc.

Any ideas? Thanks again.

Quote:

---

Originally Posted by PomND

I fixed that PHP warning, it was nothing related I don't think as the problem is still there.

I have another error log that I think is more related (hopefully)

[12-Feb-2013 09:36:01 Europe/London] PHP Parse error: syntax error, unexpected $end in /home/zoosp198/public_html/shop/includes/templates/zoosportwhite/templates/tpl_modules_no_account.php on line 318

And when I go to look at that file this is the code that comes up towards the end:

Code:

---

<fieldset id="noAccountReferral">
<legend><?php echo TABLE_HEADING_REFERRAL_DETAILS; ?></legend>
<label class="inputLabel" for="customers_referral"><?php echo ENTRY_CUSTOMERS_REFERRAL; ?></label>
<?php echo zen_draw_input_field('customers_referral', '', zen_set_field_length(TABLE_CUSTOMERS, 'customers_referral', '15') . ' id="customers_referral"'); ?>
<br class="clearBoth" />
</fieldset>
<?php } ?>

---

The very last line of that is line 318 and is the last line of the doc.

Any ideas? Thanks again.

---

Did you make any other changes to this file??? The error would indicate that there is other code that has been added that has not been properly enclosed in brackets..

Quote:

---

Originally Posted by DivaVocals

Okay I think I got it all updated, tested, and documented.. I summarized all the threads I posted which covers most of the updates I made above. I'm wiped out right now and I will bundle this all up and submit it in the morning..

---

Submitting now.. :smile:

Quote:

---

Originally Posted by DivaVocals

Okay I think I got it all updated, tested, and documented.. I summarized all the threads I posted which covers most of the updates I made above. I'm wiped out right now and I will bundle this all up and submit it in the morning..

---

Version: v2.4 is now available in the downloads section see http://www.zen-cart.com/showthread.p...48#post1184148 for summary of the changes..

I’ve installed this module and I think everything is installed correctly. However the sign up page is not gone it’s just changed to this:
http://vestaforyou.net/estoppel/inde...ain_page=login
What am I missing?
Thanks in advance for any help…
using: v1.5.0
NEW INstall
TinyMCE plug in installed
This install was done using cpanel on bluehost.

I’ve installed this module and I think everything is installed correctly. However the sign up page is not gone it’s just changed to this:
http://vestaforyou.net/estoppel/inde...ain_page=login
What am I missing?
Thanks in advance for any help…
using: v1.5.0
NEW INstall
TinyMCE plug in installed
This install was done using cpanel on bluehost.

Add something to your basket and you will see the COWOA option.
You did not upload all the language files, because i can see the defines rather than the text

Thank you – I added the missed language files.

So just so I got this straight, COWOA will only be an option? Is there any way to make it the only option?
IE: go directly to this page for check out?
http://vestaforyou.net/estoppel/inde...age=no_account

Quote:

---

Originally Posted by markalpine

Thank you – I added the missed language files.

So just so I got this straight, COWOA will only be an option? Is there any way to make it the only option?
IE: go directly to this page for check out?
http://vestaforyou.net/estoppel/inde...age=no_account

---

You may want to have a look at this free mod, it has COWOA integrated into it but with the additional option of COWOA as the only checkout option too.
https://www.numinix.com/downloads/ze...-easy-checkout

take note though that it doesn't play at all well with this COWOA mod, you will find it easier to restore the backup you made prior to installing COWOA and starting with a clean sheet.

Quote:

---

Originally Posted by picandnix

You may want to have a look at this free mod, it has COWOA integrated into it but with the additional option of COWOA as the only checkout option too.
https://www.numinix.com/downloads/ze...-easy-checkout

take note though that it doesn't play at all well with this COWOA mod, you will find it easier to restore the backup you made prior to installing COWOA and starting with a clean sheet.

---

Two things for the OP to note
FEC doesn't play well with other mods (other payment and shipping modules and URL rewriter have been known to be problematic)..
The next Zen Cart release will bundle in THIS module. Which may impact any FEC installs (especially since FECs COWOA code is based in this module's core code)

Finally.. the author of FEC provides little to no support on this forum and does not update the module repository on this forum when there are updates to FEC.. these were all deal breakers for my client who I migrated from FEC to COWOA.. to help with usability I moved the COWOA section to the top of the page above the standard account options.

Quote:

---

Originally Posted by DivaVocals

Two things for the OP to note
FEC doesn't play well with other mods (other payment and shipping modules and URL rewriter have been known to be problematic)..
The next Zen Cart release will bundle in THIS module. Which may impact any FEC installs (especially since FECs COWOA code is based in this module's core code)

Finally.. the author of FEC provides little to no support on this forum and does not update the module repository on this forum when there are updates to FEC.. these were all deal breakers for my client who I migrated from FEC to COWOA.. to help with usability I moved the COWOA section to the top of the page above the standard account options.

---

The exact reasons I 'converted' from FEC to COWOA myself too but I was just answering his specific need :hug:

Quote:

---

Originally Posted by picandnix

The exact reasons I 'converted' from FEC to COWOA myself too but I was just answering his specific need :hug:

---

I understand.. I merely wanted to point out FECs caveats before the OP installed it to solve one issue only to find they had two other new issues because they didn't know all the pros and cons..

Thank you both for all your help!

Update:
Not sure if this is the best way to do this but here’s what I did.
I went to this file:
includes\templates\template_default\templates\ tpl_shopping_cart_default.php

and I changed the code in line 132:

<div class="buttonRow forward"><?php echo '<a href="' . zen_href_link(FILENAME_CHECKOUT_SHIPPING, '', 'SSL') . '">' . zen_image_button(BUTTON_IMAGE_CHECKOUT, BUTTON_CHECKOUT_ALT) . '</a>'; ?></div>

change to this:

<div class="buttonRow forward"><?php echo '<a href="' . zen_href_link(FILENAME_NO_ACCOUNT, '', 'SSL') . '">' . zen_image_button(BUTTON_IMAGE_CHECKOUT, BUTTON_CHECKOUT_ALT) . '</a>'; ?></div>

Notice the change from “FILENAME_CHECKOUT_SHIPPING” to “FILENAME_NO_ACCOUNT” – this takes the user right to the no account sign up page used in COWOA.

Quote:

---

Originally Posted by markalpine

Update:
Not sure if this is the best way to do this but here’s what I did.
I went to this file:
includes\templates\template_default\templates\ tpl_shopping_cart_default.php

and I changed the code in line 132:

<div class="buttonRow forward"><?php echo '<a href="' . zen_href_link(FILENAME_CHECKOUT_SHIPPING, '', 'SSL') . '">' . zen_image_button(BUTTON_IMAGE_CHECKOUT, BUTTON_CHECKOUT_ALT) . '</a>'; ?></div>

change to this:

<div class="buttonRow forward"><?php echo '<a href="' . zen_href_link(FILENAME_NO_ACCOUNT, '', 'SSL') . '">' . zen_image_button(BUTTON_IMAGE_CHECKOUT, BUTTON_CHECKOUT_ALT) . '</a>'; ?></div>

Notice the change from “FILENAME_CHECKOUT_SHIPPING” to “FILENAME_NO_ACCOUNT” – this takes the user right to the no account sign up page used in COWOA.

---

What use is it for a customer that has not put anything in his/her shopping basket to sign up without an account??

Any error logs generated by doing so?

Not sure where this idea came from:

‘a customer that has not put anything in his/her shopping basket to sign up without an account”

The way I’ve set this up you can’t sign up (or order) unless you’ve placed something in your cart. But I’ve taken it all the way to the point of submitting credit card with no errors at all. I’ll have the whole thing set up next week and respond if there are any errors.

Quote:

---

Originally Posted by markalpine

Update:
Not sure if this is the best way to do this but here’s what I did.
I went to this file:
includes\templates\template_default\templates\ tpl_shopping_cart_default.php

and I changed the code in line 132:

<div class="buttonRow forward"><?php echo '<a href="' . zen_href_link(FILENAME_CHECKOUT_SHIPPING, '', 'SSL') . '">' . zen_image_button(BUTTON_IMAGE_CHECKOUT, BUTTON_CHECKOUT_ALT) . '</a>'; ?></div>

change to this:

<div class="buttonRow forward"><?php echo '<a href="' . zen_href_link(FILENAME_NO_ACCOUNT, '', 'SSL') . '">' . zen_image_button(BUTTON_IMAGE_CHECKOUT, BUTTON_CHECKOUT_ALT) . '</a>'; ?></div>

Notice the change from “FILENAME_CHECKOUT_SHIPPING” to “FILENAME_NO_ACCOUNT” – this takes the user right to the no account sign up page used in COWOA.

---

Yes this will work, but if it were me I would want to make this an admin configurable option.. An admin configurable option means you don't have to go digging through the code should you decide you want both standard and COWOA options. You also have to remove the link to the login page from the no_account page and you have to figure out a way to prevent folks from "backdooring" their way into the login page. There is a way to turn off the defined pages so that if someone directly entered the link to that page they get a "Page Not Found" error.. If it was me I would look for a means to do something similar to the login page.

From personal experience I have fo8und that clients who INSIST that there should be no other options other than COWOA generally don't have a really good business reason to insist on this.. They merely "heard" that this was better.. (Usually someone told them it's good for SEO or something similar) I tell folks to look at the large retailers.. (WWAD - What would Amazon do?)

In other words there is no downside to people CHOOSING to register for a shop account.. The clients I converted from FEC to COWOA found that their "concerns" were addressed by simply moving the COWOA options above the standard options on the login page so it's seen first by customers.

This is my first post/question here. Hopefully, I will give enough info.
Running a linux server, php 5.2.17, Zen Cart v1.5.1 fresh install.
I have installed the CKEditor and Dynamic Price Updater.
Using a template from (sorry, site offline) (by SamWilson3D).
I am installing COWOA 2.4 (fresh).
Looking through the directory structure of the install files and comparing to the what I have, I found there are places where the install files have 'YOUR-TEMPLATE' directories where I don't. Should I add the new directory in that place (with the appropriate name) or put the file in the default template directory? Or did I miss something?

Quote:

---

Originally Posted by Stilter

This is my first post/question here. Hopefully, I will give enough info.
Running a linux server, php 5.2.17, Zen Cart v1.5.1 fresh install.
I have installed the CKEditor and Dynamic Price Updater.
Using a template from (sorry, site offline) (by SamWilson3D).
I am installing COWOA 2.4 (fresh).
Looking through the directory structure of the install files and comparing to the what I have, I found there are places where the install files have 'YOUR-TEMPLATE' directories where I don't. Should I add the new directory in that place (with the appropriate name) or put the file in the default template directory? Or did I miss something?

---

Hi Stilter,
Welcome to the community :)

YOUR-TEMPLATE as a common name where you should use your own template name. So is your template name is stilter, replace all instances of YOUR-TEMPLATE with stilter.
Like YOUR_ADMIN is replaced by the secert name you gave your admin folder

Your_TEMPLATE, or CUSTOM are used as a universal name to tell you when to use an override.

Thanks for the reply and info.
So I changed the appropriate directory names to the template name I use and uploaded/overwrote the files from the install package as described. I verified that all the files have been uploaded to the correct directories with the correct names etc. When I went to the admin page (different name), the admin-home page had this error; 'WARNING: An Error occurred, please refresh the page and try again.' I assumed this was because I haven't preformed the sql patch yet. So I went to Tools->Install SQL Patches. I copied the plain-text information from the COWOA_Full_Install.sql file and pasted to the window and hit 'Send'. Now I get an error 500 screen; 'The server encountered an internal error or misconfiguration and was unable to complete your request.'
I would greatly appreciate some assistance on what I might have done wrong and how I can fix it.
BTW, now my storefront layout is messed up...

Do I need to copy and paste the sql patches one section at a time?

The server I am using has PHP 5.2.17. Is there anything in the configuration I sure check for as the cause of an internal server error (500) when doing the sql patch?

Quote:

---

Originally Posted by Stilter

The server I am using has PHP 5.2.17. Is there anything in the configuration I sure check for as the cause of an internal server error (500) when doing the sql patch?

---

We can't GUESS what's going on with your install.. So you will need to provide more information. Blank or incompletely rendered pages means that an error has ocurred and that an error log has been generated.. You need to check your error logs.. I'm that there are a few.. the source of your issue will probably be in the error log message..

BEFORE YOU DO THIS:
The most common cause of issues is due to errors when installing a module.. PLEASE review the readme file that somes with COWOA. Re-review the installation instructions and double check that you have uploaded ALL the right files to the right locations. Make sure that you have installed the SQL correctly (you asked if you can install the SQL in sections.. the general answer to this is NO you cannot run the SQL in bits and pieces).

Quote:

---

Originally Posted by Stilter

Do I need to copy and paste the sql patches one section at a time?

---

If you are SURE you've got everything in place (and I am POSISTIVE that there is an installation error at play here) THEN check your error logs.. Post the error log messages here..

Hopefully this is the right place to post this question. I have a site with cherry_zen template installed. The only reason I think this may be relevant to my issue is because I have other sites where COWOA module work just fine. I'm running ZC 1.5.1. I've installed the COWOA files, as well as the SQL install, but when I go to checkout, it doesn't give the guest checkout option that is normally available with this module. I haven't yet uploaded this site to the web yet, as I'm working on it locally. Does anyone have an idea of what can be the problem? I've enabled the COWOA under configuration > COWOA but it just isn't showing. Any help would be greatly appreciated.

Quote:

---

Originally Posted by eazy

Hopefully this is the right place to post this question. I have a site with cherry_zen template installed. The only reason I think this may be relevant to my issue is because I have other sites where COWOA module work just fine. I'm running ZC 1.5.1. I've installed the COWOA files, as well as the SQL install, but when I go to checkout, it doesn't give the guest checkout option that is normally available with this module. I haven't yet uploaded this site to the web yet, as I'm working on it locally. Does anyone have an idea of what can be the problem? I've enabled the COWOA under configuration > COWOA but it just isn't showing. Any help would be greatly appreciated.

---

Did you double check that all the files are loaded.. because if the guest checkout option is missing it sounds like the files were not fully uploaded.

Quote:

---

Originally Posted by DivaVocals

Did you double check that all the files are loaded.. because if the guest checkout option is missing it sounds like the files were not fully uploaded.

---

I've checked and checked the files again and again. Any idea of what specific file presents the guest checkout box on the : index.php?main_page=login ??

Quote:

---

Originally Posted by eazy

I've checked and checked the files again and again. Any idea of what specific file presents the guest checkout box on the : index.php?main_page=login ??

---

Did you turn on the module from the admin following the guidelines in the Read Me file?

Yes, it's turned on inside the admin. But on the checkout this is what I get:

Attachment 12319

I have not setup the server yet, so I'm running on locahost.

Quote:

---

Originally Posted by eazy

Yes, it's turned on inside the admin. But on the checkout this is what I get:

Attachment 12319

I have not setup the server yet, so I'm running on locahost.

---

You do not have all the files uploaded.. If you had uploaded ALL the files this page would display the COWOA options.. doublecheck that ALL the files from COWOA have been upload and MAKE SURE that the folders named YOUR_TEMPLATE were renamed to match your template's folder name before you uploaded them..

Seriously if installed correctly this will work.. Your issues SCREAMS that this is an installation issue..

DivaVocals: thanks for all the help. I'm having another issue. I've never had problems in the past with this module. I've gone through winmerge and copied/modified the necessary files. See the screenshot below. It's showing the constant name for billing, and not for the other steps. I'm assuming it has something to do with tpl_no_account_default.php but I haven't made any modifications to it. Any idea what could be wrong?

Attachment 12321

Quote:

---

Originally Posted by eazy

DivaVocals: thanks for all the help. I'm having another issue. I've never had problems in the past with this module. I've gone through winmerge and copied/modified the necessary files. See the screenshot below. It's showing the constant name for billing, and not for the other steps. I'm assuming it has something to do with tpl_no_account_default.php but I haven't made any modifications to it. Any idea what could be wrong?

Attachment 12321

---

No this is not an issue with the tpl_no_account_default.php.. The module when installed correctly works fine.. this isn't a bug, and there isn't any code that needs to be fixed..

You're going think I sound like a broken record, but this again says that ALL THE FILES this module needs have not been uploaded to the places they should be.. In this case you are missing ALL the language files..

Now I don't know what's going on, but perhaps it's the FTP software you are using which is the issue.. Somehow it's not replacing the files on your server maybe, but if all the properly modified files were where they should be then this module will just work..

Hi there;
This may have been answered somewhere, but I've gone buggy eyed trying to find it. I do apologize.
I've installed the COWOA version for v1.5. Had a problems, so uninstalled all the files and re-installed.
Site is not broken now (Yippie) but when I go to my Admin - Configure the COWOA is not in the dropdown.
Did I miss something?

Thanks in advance,
KJ

Quote:

---

Originally Posted by ladyk

Hi there;
This may have been answered somewhere, but I've gone buggy eyed trying to find it. I do apologize.
I've installed the COWOA version for v1.5. Had a problems, so uninstalled all the files and re-installed.
Site is not broken now (Yippie) but when I go to my Admin - Configure the COWOA is not in the dropdown.
Did I miss something?

Thanks in advance,
KJ

---

Suggest rolling back your site to the state it was BEFORE you installed COWOA and then start over with the install..

Quote:

---

Originally Posted by DivaVocals

Suggest rolling back your site to the state it was BEFORE you installed COWOA and then start over with the install..

---

Thanks for getting back DivaVocals. I noticed something else while I was comparing files to change. In includes/filenames
there is no define line for COWOA. There is only the mention of COWOA at the top. Is there a line missing?

Thanks,
KJ

Quote:

---

Originally Posted by ladyk

Thanks for getting back DivaVocals. I noticed something else while I was comparing files to change. In includes/filenames
there is no define line for COWOA. There is only the mention of COWOA at the top. Is there a line missing?

Thanks,
KJ

---

No.. there isn't anything missing from this file at all.. One line was added and it is the correct code.. Otherwise all of our UAT testing for COWOA would have failed and many people would be reporting issues with this module..

Quote:

---

Originally Posted by DivaVocals

No.. there isn't anything missing from this file at all.. One line was added and it is the correct code.. Otherwise all of our UAT testing for COWOA would have failed and many people would be reporting issues with this module..

---

Ok. I just wanted to double check.
I'm trying to run the uninstall but am running into a snag. If I run in MyPhP I get this error :

SQL query:

SELECT @t4 := configuration_group_id
FROM configuration_group
WHERE configuration_group_title = 'COWOA';


MySQL said:

#1146 - Table 'brideazz_zenc849.configuration_group' doesn't exist

If I run in Admin / SQL Patches, I get this :

WARNING: An Error occurred, please refresh the page and try again.

Help?

Quote:

---

Originally Posted by ladyk

Ok. I just wanted to double check.
I'm trying to run the uninstall but am running into a snag. If I run in MyPhP I get this error :

SQL query:

SELECT @t4 := configuration_group_id
FROM configuration_group
WHERE configuration_group_title = 'COWOA';


MySQL said:

#1146 - Table 'brideazz_zenc849.configuration_group' doesn't exist

If I run in Admin / SQL Patches, I get this :

WARNING: An Error occurred, please refresh the page and try again.

Help?

---

Beacuse as the message indicates, this table doesn't exist.. (you are probably using table pre-fixes)

You need to run this from the shop admin (as suggested in the readme). If you want to run this in phpAdmin, then you need to modify the SQL to add your table pre-fix to the table name.. and before you ask, the addition of a table prefix is NOT required if you run this from the store admin..

Hi,

Seems to be some discussion about this, but let me just ask anyway. I just tried a new install of COWOA 2.4. I installed all the files in the distribution but when I went to paste the SQL patch into the admin area the admin main page loaded with no content other than something like "an error was encountered, try refreshing the page." I browsed around the admin and everything seemed fine otherwise but I decided against going further with the install. I would suspect that the problem lies with the index.php file in the admin folder but personally would not know what to look for. Any thoughts or known issues??

Quote:

---

Originally Posted by wacamatic

Hi,

Seems to be some discussion about this, but let me just ask anyway. I just tried a new install of COWOA 2.4. I installed all the files in the distribution but when I went to paste the SQL patch into the admin area the admin main page loaded with no content other than something like "an error was encountered, try refreshing the page." I browsed around the admin and everything seemed fine otherwise but I decided against going further with the install. I would suspect that the problem lies with the index.php file in the admin folder but personally would not know what to look for. Any thoughts or known issues??

---

There's no reason to assume that the issue is with the admin index.php based on the infromation you provided.. So I wouldn't assume that the issue is with any file until you look at the error log.. What does the error log you would have gotten after running the SQL file say..

Didn't actually get to do the new install.sql. Noticed the problem in the admin before I did that. That is why I assume it was an issue with the admin index.php. I'll keep you posted if I make any progress. Thanks for the help though.

Warren

Quote:

---

Originally Posted by wacamatic

Didn't actually get to do the new install.sql. Noticed the problem in the admin before I did that. That is why I assume it was an issue with the admin index.php. I'll keep you posted if I make any progress. Thanks for the help though.

Warren

---

Well based on the on-screen message you would have generated an error log which will contain a hint as to the nature of the issue..

Firstly, I must to thank you the Zencart support team for helping us to solve so much problems!

I'm very new to Zen cart, and tried to install COWOA 2.4 (my zencart version 1.5.1 with PHP Version: 5.2.17, using Abagon template).

Problems as belows:
- Webpage became 100% width. (That means the left and the right column shifted to the screen edge.)
- The white background color of product info. page disappeared.
- Product description changed to "center alignment" from "left alighment".
- Header banner disappeared.
- Currency pull-down menu disappeared.

My installation process:
For new COWOA installation, I just followed the instruction to rename the admin and template folder name, then used ftp software to upload all the files to my host. During installation, some files were overwritten, then I installed COWOA_Full_Install.sql and configured COWOA by following the instruction. No any error warning occur!


At the same time, I've tried to change to classic template, it's normal.

I've gone thru all the posts here but really couldn't find the same problems as mine.

I uninstalled the COWOA, but the layout cannot be recoverd, no any improvement at all! Then I installed Abagon template again to get back the original layout.

I would like to install COWOA again but I'm afraid the same result will be came out!
I don't know if I missed some steps during installation and how I can fix it.

Could anyone help me? thank you very much!

Quote:

---

Originally Posted by jaychan2013

Firstly, I must to thank you the Zencart support team for helping us to solve so much problems!

I'm very new to Zen cart, and tried to install COWOA 2.4 (my zencart version 1.5.1 with PHP Version: 5.2.17, using Abagon template).

Problems as belows:
- Webpage became 100% width. (That means the left and the right column shifted to the screen edge.)
- The white background color of product info. page disappeared.
- Product description changed to "center alignment" from "left alighment".
- Header banner disappeared.
- Currency pull-down menu disappeared.

My installation process:
For new COWOA installation, I just followed the instruction to rename the admin and template folder name, then used ftp software to upload all the files to my host. During installation, some files were overwritten, then I installed COWOA_Full_Install.sql and configured COWOA by following the instruction. No any error warning occur!


At the same time, I've tried to change to classic template, it's normal.

I've gone thru all the posts here but really couldn't find the same problems as mine.

I uninstalled the COWOA, but the layout cannot be recoverd, no any improvement at all! Then I installed Abagon template again to get back the original layout.

I would like to install COWOA again but I'm afraid the same result will be came out!
I don't know if I missed some steps during installation and how I can fix it.

Could anyone help me? thank you very much!

---

Anytime you install a module and it uses the same files make sure you merge all files with the files it is over writing. Use a program like winmerge or the one I use is Beyond Compare. If you don't you will end up doing exactly what you did over writing files that don't need to be overwritten.

Help would be appreciated ..here my problem i installed COWOA new installation i place all files in there corresponding place and install the COWOA full install .sql everything worked great except when i place the tpl_header in the common folder it messed up my top navigation bar but when i put the original template tpl_header it goes back out normal... can i use the original tpl_header or do i need to modify the COWOA tpl_header im using the pure blue template My website is www.isaifishing.com

Quote:

---

Originally Posted by isaifishing

Help would be appreciated ..here my problem i installed COWOA new installation i place all files in there corresponding place and install the COWOA full install .sql everything worked great except when i place the tpl_header in the common folder it messed up my top navigation bar but when i put the original template tpl_header it goes back out normal... can i use the original tpl_header or do i need to modify the COWOA tpl_header im using the pure blue template My website is www.isaifishing.com

---

Which template are you using again? I don't see the one you are talking about in the plugins. I link to the template you are using would be helpful in determining what the problem is with the tpl_header.php.

im using this the pure blue http://www.12leaves.com/store/purebl...-template.html when i put the tpl_header.php from the cowoa it puts a new navigation bar (white u need to hover or to see it) n pushing the navigation bar up getting rid of the blue bar n pushing my logo down

Quote:

---

Originally Posted by isaifishing

Help would be appreciated ..here my problem i installed COWOA new installation i place all files in there corresponding place and install the COWOA full install .sql everything worked great except when i place the tpl_header in the common folder it messed up my top navigation bar but when i put the original template tpl_header it goes back out normal... can i use the original tpl_header or do i need to modify the COWOA tpl_header im using the pure blue template My website is www.isaifishing.com

---

The solution is below.. Sounds like you overwrote instead of merging your files as suggested in the COWOA readme..

Quote:

---

Originally Posted by countrycharm

Anytime you install a module and it uses the same files make sure you merge all files with the files it is over writing. Use a program like winmerge or the one I use is Beyond Compare. If you don't you will end up doing exactly what you did over writing files that don't need to be overwritten.

---

Quote:

---

Originally Posted by countrycharm

Anytime you install a module and it uses the same files make sure you merge all files with the files it is over writing. Use a program like winmerge or the one I use is Beyond Compare. If you don't you will end up doing exactly what you did over writing files that don't need to be overwritten.

---

Thanks Countrycharm! I reworked and merged the files again, but many problems still existed!! (layout still changed and the COWOA configure page is blank (no option to activate). Then I replaced the whole public_html folder with my backup files and uploaded the COWOA files one by one to my store directory. This time, everyting seems ok. But when I tried to check out without acc. the page showed "error 500" after I filled in all address information and sent out!
Attachment 12621

One more thing, when I install the SQL code, is showed the following image:
Attachment 12622

Could you tell me how to fix?

My template is aBagon-red
and My website is laughmoreshop.com

Thanks very much!!

Hi, I would like to report my status.

I found that the webpage layout changed because of the tpl_main_page.php didn't merged. After I merged it, all problems settled.
:smile:Thanks zen support team again!

P.S. The COWOA 2.4 installation readme core files does not list this file.

And here's a great example of why Check Out without account (COWOA) is a must.

>> http://www.youtube.com/watch?v=3Sk7c...=TLvRV7MdBdSP4

Regards

Jamie

I just want to make sure I install this right. I install version COWOA for Zen Cart 1.3.9 first then COWOA 2.4. Since I didn't see anything in the instructions

oooops, never mind