COWOA (for ZC v1.5.x)

delia:

Well, it's certainly not what I want to do, believe me. We had a big wrangle about it.

Can't remember where it came from, but I already have a switch for COWOA only site... Basically turns off all and any login/logoff fields and checkout is pushed through as COWOA only. I use it at times for testing things and just kept it in the code.

davewest:

I agree that the order status code can use better sanitizing and protection... will work on that.

OK... so looking at mine and the 2.6 order status pages, I had a bit of difference between them. So what I did was updated both to more consistent code with other ZC files. Changes to both template and header file was allot so fully replace for ZC 1.5.4 and 1.5.5.. I don't have anything less then 1.5.4 installed so not tested below that point.

What's new!
Spam and bot code testing by honey pot, not sure spam bot testing is really needed, but can't heart.
Delay for rapid hit abuse, change the delay time in the header define.
I think better sanitizing of the input fields.
Off switches for display of product, shipping, and payment fields.. defines are in the template, could code into the config, but not sure why!
Testing for customer that are logged in already, redirects them to the order history page instead of order status.
tests for non-existent email address's.
Added 'number' and 'email' to input fields for mobile tech... remove if this drives you nuts...

No changes in display was done, tables show up as responsive for me so left them alone. attaching zip

davewest:

Can't remember where it came from, but I already have a switch for COWOA only site... Basically turns off all and any login/logoff fields and checkout is pushed through as COWOA only. I use it at times for testing things and just kept it in the code.

OK... so looking at mine and the 2.6 order status pages, I had a bit of difference between them. So what I did was updated both to more consistent code with other ZC files. Changes to both template and header file was allot so fully replace for ZC 1.5.4 and 1.5.5.. I don't have anything less then 1.5.4 installed so not tested below that point.

What's new!
Spam and bot code testing by honey pot, not sure spam bot testing is really needed, but can't heart.
Delay for rapid hit abuse, change the delay time in the header define.
I think better sanitizing of the input fields.
Off switches for display of product, shipping, and payment fields.. defines are in the template, could code into the config, but not sure why!
Testing for customer that are logged in already, redirects them to the order history page instead of order status.
tests for non-existent email address's.
Added 'number' and 'email' to input fields for mobile tech... remove if this drives you nuts...

No changes in display was done, tables show up as responsive for me so left them alone. attaching zip

Not sure how much of this zip file should be incorporated into the current COWOA beta.. Is this code for someone who wants a COWOA ONLY shop or is there anything in this zip file that should/could be incorporated into COWOA beta?? If there are only specific bits that should/could be incorporated, could you possibly submit those changes as a PR in the Github repo for COWOA since you know which bits should be incorporated?? Purty please... :blush:

DivaVocals:

Not sure how much of this zip file should be incorporated into the current COWOA beta.. Is this code for someone who wants a COWOA ONLY shop or is there anything in this zip file that should/could be incorporated into COWOA beta?? If there are only specific bits that should/could be incorporated, could you possibly submit those changes as a PR in the Github repo for COWOA since you know which bits should be incorporated?? Purty please... :blush:

The zip was just the order status page. The COWOA only switch is not included. I'll look at github and see what I can do.. I disconnected my fork for I went down a different hole... just found a new rabbit to chase so may be taking it down again and rewriting it..

davewest:

The zip was just the order status page. The COWOA only switch is not included. I'll look at github and see what I can do.. I disconnected my fork for I went down a different hole... just found a new rabbit to chase so may be taking it down again and rewriting it..

If this is just an update to the order status page, I can incorporate your zip file into COWOA..

Can I use the Cowoa Beta version on a live 1.5.5 website, as it all seems to be working OK? If not, do you know when it will be added to the plugins section?

I have a problem in 1.5.1 that I actually don't think is COWOA related but need to check to see if this rings a bell with anyone.

Free shipping over $50 is enabled and now that is the only shipping choice showing. Everything else disappears. The options do show when the total is under $50.

If this is due to COWOA, it would simply have been something I've never witnessed as most sites I work on don't do free shipping too. It's also such a subtle change and wouldn't impact every site that it just may not have been noticed before. I wouldn't bet on that though. and this is a 1.5.1 site.

and we also tried turning off the $50 free shipping to have it all start working normally again. So this has something to do with free shipping only as I suspected.

This particular cart does have a reoccurring error that was introduced last year. It was unnoticed til now though I still don't know what's causing it. In the shopping cart, the page does not display the estimate shipping information, and throws an error

Cannot redeclare class order in /home/xxxxxx/public_html/includes/classes/order.php on line 1054

There's nothing wrong with that file as I had uploaded the original one from 1.5.1 and the problem still occurs. I don't know if this is part of this problem or not so I hesitated to mention it. But... maybe.... it might give a clue as to what's going on.

was given the code to fix that php error so that is not part of the shipping options problem

Problem solved: Files which do
require(DIR_WS_CLASSES . 'order.php');

must be changed to

require_once(DIR_WS_CLASSES . 'order.php');

(notably includes/modules/shipping_estimator.php)

Yes, that was the error fix. Thanks, Scott.

still got no options showing up for shipping besides free

delia:

Yes, that was the error fix. Thanks, Scott.

still got no options showing up for shipping besides free

is this just the shipping step page? or shipping/payment/order total page... i've tested for every shipping i could think of so will have to run some things down.. one issue comes to mind is to see if shipping is getting called which builds the list of active shiipping options..

i've had order,php error before... but found it wasn't needed again... deleted the extra calls.. will look into changing to require_once

i'm out of town now so don't have my work station with me to look at.

the issue is that only the free shipping shows on the shipping page and the estimate shipping.

I've got a client that's "kicking the tires" on the COWOA plugin. He noticed that you can't go through guest-checkout if you already have an account. Is there any way for that functionality to occur (other than deleting all customers' records)?

delia:

the issue is that only the free shipping shows on the shipping page and the estimate shipping.
still looking at this, but so far not getting an error to show up. I'm getting it to show with other shipping options over the set amount and not show when under set amount..

lat9:

I've got a client that's "kicking the tires" on the COWOA plugin. He noticed that you can't go through guest-checkout if you already have an account. Is there any way for that functionality to occur (other than deleting all customers' records)?
so the customer with an account doesn't want to log in! I think this version of COWOA only has an off switch.. The one I've been playing with and running on my own site has an only COWOA switch which totally hides the account side of Zen Cart. Also an admin switch to change accounts to COWOA and back to Standard..

I think it would be possible to change the logic of COWOA to make it work. Currently not something in COWOA. We use the customer email address to figure out the user ID for both types of accounts and added password for the standard account. So some of the same rules would still need to be in place so when the account holder do login, they can see past orders.

twas settings. I had to look up how it was supposed to be done for later versions of zen cart. The settings for free shipping were different and working. So it wasn't the COWOA.

davewest:

... so the customer with an account doesn't want to log in! I think this version of COWOA only has an off switch.. The one I've been playing with and running on my own site has an only COWOA switch which totally hides the account side of Zen Cart. Also an admin switch to change accounts to COWOA and back to Standard..
It's not that they don't want to log in; the site's products are seasonal and the returning customers, many times, don't remember their password and can't "find" the password-forgotten emails to actually log in.

I started playing with the beta release - having not touched anybody else's version in a long time. I just recently made my version responsive - and ran into an issue with the beta release. I don't see how to create an issue on github - it's not a code thing but a usability issue that needs discussing. Shall I mention it here?

lat9:

It's not that they don't want to log in; the site's products are seasonal and the returning customers, many times, don't remember their password and can't "find" the password-forgotten emails to actually log in.
That's why I changed my password reset system...

delia:

I started playing with the beta release - having not touched anybody else's version in a long time. I just recently made my version responsive - and ran into an issue with the beta release. I don't see how to create an issue on github - it's not a code thing but a usability issue that needs discussing. Shall I mention it here?
It's always a pain degrading the template back to the basic, but the idea is that it would make it easier for the user to upgrade or match their site. With the new responsive basic adds another one to the list.. If I give up and do what I know, would that make it hard for a non-coder to modify and match their site! Perhaps a good discussing in a new thread for it's something to think about in all mods that modify template forms.

delia:

I started playing with the beta release - having not touched anybody else's version in a long time. I just recently made my version responsive - and ran into an issue with the beta release. I don't see how to create an issue on github - it's not a code thing but a usability issue that needs discussing. Shall I mention it here?

No.. any discussions for the beta version need to be logged on Github.. not sure why you don't see the issues tab.. it's in the same location as any other Github repo: https://github.com/DivaVocals/zen_COWOA/issues

First of all thanks for the work on getting this going for 1.5.5. COWOA (guest checkout) is a great needed feature.

I have a question/request that I have brought up before. I would love to see the possibility to allow guest checkout even when there is already an existing registered account for this email. Is this technically possible without screwing up the zencart customer or order db's?

Currently you can not use the guest checkout with an already registered email. Say a returning registered customer comes back to our site and just wants to do a guest checkout this time, won't work. Reality is many customers are not remembering the correct password and dealing with the password reset function is more cumbersome to them than simply go with the guest checkout. So they go with guest checkout only to find out they can't because they have already a registered account with us with this email. Now frustration sets in and we ether loose the sale or I get frustrated calls from them. Some try the reset password function but the reset email lands in spam too often leading them to multiple tries at the reset function, more frustration sets in.

We IT folks might think this is not big deal, just use another email or go to your spam folder and look a bit harder.... well your average site visitor is not always that computer savvy.