COWOA (for ZC v1.5.x)

[Design75]

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.

[DivaVocals]

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

CHANGE-303 Add COWOA Contribution

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

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

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

[countrycharm]

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**

[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:

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

to:

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

and poof the problem goes away..

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!)

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

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)

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

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.

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

[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

[countrycharm]

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.

[PomND]

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.

[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:

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

[DivaVocals]

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:

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

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