COWOA Module (my update for ZC v1.3.x)

JTheed:

Can't help with the information you have provided.

with COWOA turned on, when you go to make an order and fill out your information and click to continue all it does is refresh that page, so it is impossible to complete an order.

jeremy0203:

with COWOA turned on, when you go to make an order and fill out your information and click to continue all it does is refresh that page, so it is impossible to complete an order.

This usually happens when you don't add them to your template folder. If you do not have templates other than the original, then rename YOUR_TEMPLATE to classic.
Also check to make sure you have renamed ALL of the YOUR_TEMPLATE folders to the name of your modified template or classic. In Version 2.0C1 there are:

includes/languages/english/YOUR_TEMPLATE
includes/modules/YOUR_TEMPLATE
includes/templates/YOUR_TEMPLATE

from the install instructions:

STEP 0-A If you have a Brand New Zen Cart 139 installation, just merge these files into yours. If you do not have a new template, erase the YOUR-TEMPLATE folder.

JT, if a zen cart does not have a custom template, do you literally mean to erase the YOUR-TEMPLATE directory (and everything in it)? What do you mean by the word "erase," since the files in that directory are needed for this mod?

additional question before I start install:

I installed PayPal EC and it is working beautifully. I want to install COWOA for customers who may not want to use PPEC, but who do want to buy something from me, w/o creating an account. So, will I need to hack and merge several files in order to install COWOA over the top of PPEC?

For example, the page for login/createaccount/optionPPEC is going to also need the new COWOA message to the customer and link to continue CO process. That seems like an obvious page that will need to be merged. Any others? Is merging that page difficult to do? thank you..

please disregard my post about modifying files, but I don't want to foul anything up, so I have this question:

although this is mentioned three posts above, is there an important reason that the install.txt file does not say to rename these directories? Only the templates directory is mentioned for renaming in the install.txt file.

includes/languages/english/YOUR_TEMPLATE
includes/modules/YOUR_TEMPLATE

finlander:

from the install instructions:

JT, if a zen cart does not have a custom template, do you literally mean to erase the YOUR-TEMPLATE directory (and everything in it)? What do you mean by the word "erase," since the files in that directory are needed for this mod?

Looking at it now, that INSTRUCTION should have been erased. If you do not have any Modified Template, rename YOUR_TEMPLATE to classic, which is the default Zen Cart template.

thanks JT,
hey, I'm just plugging along here merging files so I will have the COWOA code and the most recent zen code. There is quite a lot of newer zen code since even last summer, but especially since some of the code I'm seeing from 2007.
Anyway, I noticed that this file
/includes/languages/english/checkout_process.php
is also a modified file, but it's not in your list of modified files in the install.txt. It was easy to spot, not every one may spot it.
just fyi..

finlander:

thanks JT,
hey, I'm just plugging along here merging files so I will have the COWOA code and the most recent zen code. There is quite a lot of newer zen code since even last summer, but especially since some of the code I'm seeing from 2007.
Anyway, I noticed that this file
/includes/languages/english/checkout_process.php
is also a modified file, but it's not in your list of modified files in the install.txt. It was easy to spot, not every one may spot it.
just fyi..

Thanks...
There are actually a few more than that. I didn't really update the install.txt file as I should the last go round. I just made the mod go by the override rules wherever I could. Next time I change something I will be sure to change those instructions.

Is replacement intentional of the php closing tag (in stock zen files) with the '// eof' tag (in COWOA files)?

The gv_redeem file in languages is one where I saw this replacement. There may be others. Is this a good idea?

Quote:
Originally Posted by finlander
thanks JT,
hey, I'm just plugging along here merging files so I will have the COWOA code and the most recent zen code. There is quite a lot of newer zen code since even last summer, but especially since some of the code I'm seeing from 2007.
Anyway, I noticed that this file
/includes/languages/english/checkout_process.php
is also a modified file, but it's not in your list of modified files in the install.txt. It was easy to spot, not every one may spot it.
just fyi..

Thanks...
There are actually a few more than that. I didn't really update the install.txt file as I should the last go round. I just made the mod go by the override rules wherever I could. Next time I change something I will be sure to change those instructions.

So true, if they are in override, it's not a huge deal, but I may run into some code from newer stock zen that is needed, especially 'cause I've got that PayPal EC stock mod installed -- it works perfect and I don't want to mess it up. I should be able to spot the ones that may need a merge.

finlander:

Is replacement intentional of the php closing tag (in stock zen files) with the '// eof' tag (in COWOA files)?

The gv_redeem file in languages is one where I saw this replacement. There may be others. Is this a good idea?

// is nothing more than a comment line. They won't effect anything.

I am not the one who originally wrote this mod, just made some changes and have been supporting it. The // lines were put in by the original coder, J Schilz.

If running Superorders, are we supposed to add the COWOA code applied to admin/orders.php also to admin/superorders?

hi JT,

I've about got the COWOA working almost perfectly ... just one thing that I can see. I didn't see mention of it in install file, but I do recall seeing some text in the code about it.

I was meticulous about merging the COWOA files w/ zen files that include my PayPal EC module. Everything is working great, except that a COWOA shopper that has at least entered through step 1 of 5, and then tries to login as an account holder (or create account), cannot get to the login screen to login as an account holder. In this circumstance, the login link takes the COWOA customer to the My Account page (but only as a COWOA visitor), so the customer is in limbo if wanting to actually login (or create account).

If I manually type logoff in the URL, I can force the visitor logoff, but I am wondering about this behavior, as I thought a COWOA customer could choose at any time to login, and even have any cart contents merged that happened to be hanging in either place.

https://www.vintage-adventures.com

oh no!

Parse error: syntax error, unexpected T_CASE in /home6/vintagp1/public_html/zc_admin/orders.php on line 229

This happens on both a merged install and a clean install of the COWOA orders.php file. Could I be lucky enough that it's an easy fix?

dw08gm:

If running Superorders, are we supposed to add the COWOA code applied to admin/orders.php also to admin/superorders?

Actually, in super_orders.php, there are only two entries for COWOA

Look for ```
$check_status = $db->Execute("select customers_name, customers_email_address, orders_status,
date_purchased from " . TABLE_ORDERS . "
where orders_id = '" . (int)$oID . "'");

and add the COWOA_order so it looks like this ```
        $check_status = $db->Execute("select customers_name, customers_email_address, orders_status,
                                      date_purchased, [B]COWOA_order[/B] from " . TABLE_ORDERS . "
                                      where orders_id = '" . (int)$oID . "'");

This code is in 2 places in super_orders.

The email part that is added in orders.php goes into the super_orders_functions.php file. Rather than go into all the details, grab the ZenCart Installation program from my mods site and you can compare your admin/super_orders files against it.

finlander:

hi JT,

I've about got the COWOA working almost perfectly ... just one thing that I can see. I didn't see mention of it in install file, but I do recall seeing some text in the code about it.

I was meticulous about merging the COWOA files w/ zen files that include my PayPal EC module. Everything is working great, except that a COWOA shopper that has at least entered through step 1 of 5, and then tries to login as an account holder (or create account), cannot get to the login screen to login as an account holder. In this circumstance, the login link takes the COWOA customer to the My Account page (but only as a COWOA visitor), so the customer is in limbo if wanting to actually login (or create account).

If I manually type logoff in the URL, I can force the visitor logoff, but I am wondering about this behavior, as I thought a COWOA customer could choose at any time to login, and even have any cart contents merged that happened to be hanging in either place.

https://www.vintage-adventures.com

It seems that you have left out the code where it kills the COWOA's session, as it should be killing it after a purchase, and there should be NO MY Account page for a COWOA customer as they have NO Account. They should only be able to see there purchase via the Order Status Email link. Here is what is says on my cart after using COWOA to checkout.

If you used Checkout WithOut an Account (COWOA), you may browse the store but will not be able to purchase any more items without ending this session and starting a new one. If you have purchased a download file, you must wait for the Status E-Mail to arrive to access the download page.

Thank You for Shopping With Us..

finlander:

oh no!

Parse error: syntax error, unexpected T_CASE in /home6/vintagp1/public_html/zc_admin/orders.php on line 229

This happens on both a merged install and a clean install of the COWOA orders.php file. Could I be lucky enough that it's an easy fix?

What are you running your Zen Cart on? Is it an actual Server or one of those Wamp Servers?

The problem is not at that line as it has nothing to do with COWOA. You may have left off one of the { or } somewhere.

I just did a fresh install on 1.3.9h with NO OTHER MODS and it worked flawlessly.

thank you JT,

On the non-killed-session issue, it's when a COWOA shopper has started but not completed checkout. In that window of time, he can go out and click on the login link and get the My Account options, but can't actually login as a registered user, and can't logoff as a temp COWOA member. I say 'member' because Who's Online shows the COWOA user as a member. When I went all the way through checkout, the 'success' page just gave a logoff link and said to logoff so next user of computer couldn't access order receipt, etc. I didn't get the message you have, but I remember seeing it in the code last night when I was merging.

PS: I have not had force kill enabled when this happens.

On the orders.php issue, I am looking over the file and will need to grab a fresh one. I think I missed a brace syntax in the big section of code from about line 100 to line 200. I've put my old original online for the time being.

Dang, everything went so well. I'll fix the T Case error and then try to figure out if something is wrong w/ the aborted checkout for COWOA shopper, and if the end of checkout message should be the one you have.

oh, I'm on a Linux server that seems to work great .. that's probably not a problem.

T Case error is fixed -- it was a brace somewhere that I missed when merging. Lines 55, 92 and 101-187 COWOA inclusive, seems to do the trick. I could have just used the stock COWOA file, but wanted to keep 1.3.9h in case it had anything newer in it that should stay on the site.

Did you try to abort cowoa half way through checkout, or after finishing since I don't have kill turned on, to see how My Account is available? It could be entirely a prob of mine, but if not, then maybe being able to turn off force kill after purchase opens that door, and the door is always open for being in limbo and access to My Account for the halfway-throughers?

JTheed:

You must have merged something incorrectly and this is why you are getting the blank screen. Did you check for error logs in your cache folder?

Hi JTheed,

Thanks for the response. I figured the same thing, so I restored the site and then one file at a time copied them over to the appropriate directories and made the mods to the ones that had either been modified by my template or by me. I am now able to get into the Admin and see the COWOA attributes, but the site page is still blank. When I look at the page source of the site, it shows the same lines as the working site (without COWOA) but stops after the comment line "Header". So it appears as thought it isn't generating the full page. You can see the site before the COWOA installation at https://www.naughticorner.com/Store/ and after COWOA install at https://www.naughticorner.com/StoreNewCOWOA/.

I did notice that the instructions for installing COWOA weren't completely accurate. The list of files being changed and added wasn't complete and some of the paths were incorrect. I tried to make the right decisions for placement of each file, but maybe my assumptions aren't correct. Is there a corrected file list that I can work from?

Thanks for your help!

Michelle 8-)