COWOA (for ZC v1.5.x)

I have rolled back and all is working fine. I will wait till the release and see what occurs with others. I also had a customer fall through without leaving their telephone number (although it's mandatory) I checked myself and sure enough I could purchase without filling this field. Now I am back to original COWOA it all works as it should.

For the info:
151 clean install
PHP 5.4.28
MySQL 5.1.73

Rizla:

I have rolled back and all is working fine. I will wait till the release and see what occurs with others. I also had a customer fall through without leaving their telephone number (although it's mandatory) I checked myself and sure enough I could purchase without filling this field. Now I am back to original COWOA it all works as it should.

For the info:
151 clean install
PHP 5.4.28
MySQL 5.1.73

Well Dave's testing mimics my own testing and I have this version in production for the stores I developed it for.. I suggest that you create a dev store and do your upgrade there so there's no pressure to fix a live store.. this is what you should be doing anyway before pushing updates to your live store..

Yes! Will do, but I will still await other comments... I am convinced there is an error in one of the files... Just my opinion. But I do like the work you have put into it and the presentation to the customer is far better.... Hope it works out.

Rizla:

Yes! Will do, but I will still await other comments... I am convinced there is an error in one of the files... Just my opinion. But I do like the work you have put into it and the presentation to the customer is far better.... Hope it works out.

Sorry.. gonna have to disagree with you.. Like I said I tested this a fair bit on the sites I developed it for.. Can't afford to have my clients live sites going down.. They are NOT having the issues you are reporting.. and JUST this morning, I just installed it on ANOTHER client's test site (I always keep a test site which is a parallel of the live production site running for all of my clients JUST for upgrades etc..) I did not have ANY of the issues you described.. Install script ran fine, no errors, blank pages, or errant behavior..

AND

This particular client site I have added additional customer fields (shipping phone number, email confirmation fields), and through careful merging of the files I didn't lose any of this functionality with the latest version of COWOA installed..

That said you are free to wait for more feedback, but I do believe the issue is in an errant merge that went awry in your install.. I CANNOT recreate ONE of the issues you described.. shrug Suggest you create a dev store and try again..

And here is the issue... Please note the highlighted section:

Source: http://www.zen-cart.com/showthread.php?196995-COWOA-%28for-ZC-v1-5-x%29/page48&p=1252042#post1252042

DivaVocals:

Here's the changelog:
v2.6 - 07/10/2014

• Updated for Zen Cart v1.5.3

• Fix bug with downloads being prevented for COWOA when 'Enable Forced Logoff' was turned on (dwest)

ref: http://www.zen-cart.com/showthread.php?196995-COWOA-(for-ZC-v1-5-x)&p=1246575#post1246575

• Additional improvements to onscreen text/labels

• MANY improvements to the login page:

• Eliminate the need for an unnecessary click to create an account by making the "Create Account" available on the login page.

• Addition of "Shop with Confidence" and "Customer Service" content boxes (admin control to turn on/off and content managed via the banner manager)

• Move guest checkout field-set to the top of the page for better user visibility

Would like folks to test and report back issues they find, and once it seems like everything is working okay, I will submit to the downloads..

Here's the link to the GitHub repo: https://github.com/DivaVocals/zen_COWOA

DivaVocals:

You also need to provide a LOT more information than you have provided.. (Zen Cart version, what version of COWOA you are upgrading from, and any other relevant information)

I just noticed this in your post from earlier today..

Rizla:

I have rolled back and all is working fine. I will wait till the release and see what occurs with others. I also had a customer fall through without leaving their telephone number (although it's mandatory) I checked myself and sure enough I could purchase without filling this field. Now I am back to original COWOA it all works as it should.

For the info:
151 clean install
PHP 5.4.28
MySQL 5.1.73

Rizla:

Yes! Will do, but I will still await other comments... I am convinced there is an error in one of the files... Just my opinion. But I do like the work you have put into it and the presentation to the customer is far better.... Hope it works out.

So the issue is that COWOA v2.06 is compatible with the LATEST version of Zen Cart (v1.5.3).. The error logs you are getting would be expected since the login module, functions, and classes in Zen Cart v1.5.3 are VERY different than v1.5.1. The issues you had with the install SQL can only be chalked up to user error as I CANNOT repeat them..

It is possible to apply the new COWOA changes to v1.5.1. You would have to do some merging to pull in the updates to COWOA while leaving behind the v1.5.3 specific code.

OR

you could spend some time trying to bring in the classes and functions needed from v1.5.3 into your v1.5.1 store to allow you to use COWOA v2.06 with Zen Cart v1.5.1. (NOT recommended)

I am NOT sure I will do ANY work to make this version of COWOA v1.5.1 compatible.. It's TOO MUCH work to maintain two versions where the core files are soooo different.. I submit module updates as I make them for my clients, and I will NOT be upgrading any of my v1.5.1 clients to this new version of COWOA until I upgrade their stores to v1.5.3. There are BIG differences between v1.5.1 and v1.5.3. Given that Zen Cart v1.6.0 will include COWOA as part of the core fileset, and there are many parts of the v1.5.3 fileset that come from the v1.6.0 dev. So, I'm not AT ALL inclined to maintain backwards compatibility with v1.5.1.

I am of the opinion that v1.5.0, and v1.5.1 shops should be upgrading to v1.5.3 NOW and not meandering about waiting to upgrade..

Just wanted to add one more thought..

This is one MORE reason why you DO NOT install ANY modules especially a BETA module on your LIVE store until you TEST TEST TEST THE SNOT OUT OF IT!!!!!! The PROPER way to do ANY upgrade (New module, upgraded module, new Zen Cart version) is to create a PROPER development environment and test your changes there BEFORE attempting to update your live site.. In fact I think that shopowners should get into the habit of maintaining an active dev/test/sandbox site. (like a localhost version)

The COWOA version on Github (https://github.com/DivaVocals/zen_COWOA) is a BETA, PRE-RELEASE version. It is NOT a SNEAK PEEK/ version and should not be treated as such unless you are sure what you are doing and test it on a proper dev/test/sandbox site before posting on your live site.. I posted the link to the Github repo to get TESTING feedback before submitting to the downloads. YES.. It IS in use on live stores, but you should TEST TEST TEST on a DEVELOPMENT SITE before using on your own live site..

DivaVocals:

And here is the issue... Please note the highlighted section:

Source: http://www.zen-cart.com/showthread.php?196995-COWOA-%28for-ZC-v1-5-x%29/page48&p=1252042#post1252042

I just noticed this in your post from earlier today..

So the issue is that COWOA v2.06 is compatible with the LATEST version of Zen Cart (v1.5.3).. The error logs you are getting would be expected since the login module, functions, and classes in Zen Cart v1.5.3 are VERY different than v1.5.1. The issues you had with the install SQL can only be chalked up to user error as I CANNOT repeat them..

It is possible to apply the new COWOA changes to v1.5.1. You would have to do some merging to pull in the updates to COWOA while leaving behind the v1.5.3 specific code.

OR

you could spend some time trying to bring in the classes and functions needed from v1.5.3 into your v1.5.1 store to allow you to use COWOA v2.06 with Zen Cart v1.5.1. (NOT recommended)

I am NOT sure I will do ANY work to make this version of COWOA v1.5.1 compatible.. It's TOO MUCH work to maintain two versions where the core files are soooo different.. I submit module updates as I make them for my clients, and I will NOT be upgrading any of my v1.5.1 clients to this new version of COWOA until I upgrade their stores to v1.5.3. There are BIG differences between v1.5.1 and v1.5.3. Given that Zen Cart v1.6.0 will include COWOA as part of the core fileset, and there are many parts of the v1.5.3 fileset that come from the v1.6.0 dev. So, I'm not AT ALL inclined to maintain backwards compatibility with v1.5.1.

I am of the opinion that v1.5.0, and v1.5.1 shops should be upgrading to v1.5.3 NOW and not meandering about waiting to upgrade..

DivaVocals:

Just wanted to add one more thought..

This is one MORE reason why you DO NOT install ANY modules especially a BETA module on your LIVE store until you TEST TEST TEST THE SNOT OUT OF IT!!!!!! The PROPER way to do ANY upgrade (New module, upgraded module, new Zen Cart version) is to create a PROPER development environment and test your changes there BEFORE attempting to update your live site.. In fact I think that shopowners should get into the habit of maintaining an active dev/test/sandbox site. (like a localhost version)

The COWOA version on Github (https://github.com/DivaVocals/zen_COWOA) is a BETA, PRE-RELEASE version. It is NOT a SNEAK PEEK/ version and should not be treated as such unless you are sure what you are doing and test it on a proper dev/test/sandbox site before posting on your live site.. I posted the link to the Github repo to get TESTING feedback before submitting to the downloads. YES.. It IS in use on live stores, but you should TEST TEST TEST on a DEVELOPMENT SITE before using on your own live site..

Amen to that!

I downloaded the Github version and installed it on a development site that was upgraded from 1.5.1 to 1.5.3. I wanted to let you know that the documentation didn't mention a couple of files that are modified by COWOA.

/includes/templates/custom_template/common/tpl_main_page.php
/includes/languages/english/custom_template/button_names.php

While the installation of the files went smoothly after the integration, when I went into admin to run the full install SQL file, admin stated that there was an error and to reload the page. When that failed, I checked the log and got the following error message.

[21-Jul-2014 21:10:35 America/Chicago] PHP Fatal error: 1054:Unknown column 'COWOA_account' in 'where clause' :: select count(*) as count from customers WHERE COWOA_account = '0' ==> (as called by) /home1/godsglor/public_html/develop/shop/admin/index.php on line 53 <== in /home1/godsglor/public_html/develop/shop/includes/classes/db/mysql/query_factory.php on line 155

I was still able to access the Install SQL Patches item from the Tools menu to upload the SQL file. After that, all was well. I'm not certain if it would be better to have the users install the SQL before uploading the modified files. While it didn't freak me out, it might concern others. :D

Finally, the tpl_header.php and tpl_main_page.php files in the /includes/templates/custom_template/common folder caused the styling to be off a bit with my template. I'm using Responsive Sheffield Blue. I had to replace both of them with the backups that I made. Replacing just one of those two caused the site to give a blank page. I'm not asking for any assistance with it for two reasons: 1) I want to see if the client is ok with the way it looks now and 2) it's probably something on my end. I'm going to compare the files tomorrow to see what the differences are.

I just wanted to report on the few issues that I've found, albeit minor ones. Thanks for developing a nice mod.

--Dustin

tromak:

Amen to that!

I downloaded the Github version and installed it on a development site that was upgraded from 1.5.1 to 1.5.3. I wanted to let you know that the documentation didn't mention a couple of files that are modified by COWOA.

/includes/templates/custom_template/common/tpl_main_page.php
/includes/languages/english/custom_template/button_names.php
Might be because I haven't updated the docs yet..

tromak:

While the installation of the files went smoothly after the integration, when I went into admin to run the full install SQL file, admin stated that there was an error and to reload the page. When that failed, I checked the log and got the following error message.

[21-Jul-2014 21:10:35 America/Chicago] PHP Fatal error: 1054:Unknown column 'COWOA_account' in 'where clause' :: select count(*) as count from customers WHERE COWOA_account = '0' ==> (as called by) /home1/godsglor/public_html/develop/shop/admin/index.php on line 53 <== in /home1/godsglor/public_html/develop/shop/includes/classes/db/mysql/query_factory.php on line 155

I was still able to access the Install SQL Patches item from the Tools menu to upload the SQL file. After that, all was well. I'm not certain if it would be better to have the users install the SQL before uploading the modified files. While it didn't freak me out, it might concern others. :DNoted, and I'll update the install instructions accordingly..

tromak:

Finally, the tpl_header.php and tpl_main_page.php files in the /includes/templates/custom_template/common folder caused the styling to be off a bit with my template. I'm using Responsive Sheffield Blue. I had to replace both of them with the backups that I made. Replacing just one of those two caused the site to give a blank page. I'm not asking for any assistance with it for two reasons: 1) I want to see if the client is ok with the way it looks now and 2) it's probably something on my end. I'm going to compare the files tomorrow to see what the differences are.

I just wanted to report on the few issues that I've found, albeit minor ones. Thanks for developing a nice mod.

--Dustin
The tpl_main_page.php changes turn off the sideboxes on the checkout pages if you turn on the admin flag.. You should be merging that change into your template's version of the file.. If you replaced it and your template modifies this file, I would expect that you WOULD see some unwanted style changes..

The tpl_header.php changes only add some COWOA flags to the login/logoff links.. Again you should be merging those changes into your template's version of the file.. If you replaced it and your template modifies this file, I would expect that you WOULD see some unwanted style changes..

These are not issues with COWOA, but in how you merged in the files with your own template..

Dear all, can I ask how we can simply let user buy using email without asking for his address details and newsletter subscription?

Many thanks!
EK

Even better if possible, upon clicking checkout button, automatically bring him to the page asking for his email or just name without even requiring him to choose and click on the guest checkout option. is that actually achievable?

Thanks again!
EK

Some help please, as i have been trying for a full day and still unable to achieve the above of entering just the email for purchase without any other billing info...

Many thanks!
EK

EngKiat:

Some help please, as i have been trying for a full day and still unable to achieve the above of entering just the email for purchase without any other billing info...

Many thanks!
EK

For the checkout button, just modify the link for it and make it go to the no account landing page. As for your request, no help can be made unless you give more info on what exactly you are offering. In short, in order to process payments billing info is needed for every customer.

EngKiat:

Dear all, can I ask how we can simply let user buy using email without asking for his address details and newsletter subscription?

Many thanks!
EK

EngKiat:

Even better if possible, upon clicking checkout button, automatically bring him to the page asking for his email or just name without even requiring him to choose and click on the guest checkout option. is that actually achievable?

Thanks again!
EK

If you are asking can COWOA be modified to include this capability then I have to agree with yaritai, you cannot SKIP the customer entering BILLING data.. see my previous response to someone else on this very same line of discussion..

DivaVocals:

You are VERY wrong..** If you are accepting PayPal or credit cards, then BILLING information is required, and this is something your customers CANNOT avoid entering.**. Your customers CANNOT pay via credit card on ANY site without entering BILLING information.. Your customers cannot pay via PayPal on ANY site without entering billing information.. You are spinning your wheels trying to FIX an issue that doesn't require FIXING..

Thanks a lot for reply!
Am actually helping to build a survey cart site that needs to provide anonymity to the shoppers~can we bypass any billing info and even exclude email address , for users to check out and 'buy' the product?

Thanks!

EngKiat:

Thanks a lot for reply!
Am actually helping to build a survey cart site that needs to provide anonymity to the shoppers~can we bypass any billing info and even exclude email address , for users to check out and 'buy' the product?

Thanks!

Ummm let me try answering this another way..

**NO!!! **unless payment processors are suddenly not requiring this information to process payments (HINT: none are.. they ALL need billing info passed to them..)

DivaVocals:

If you are accepting PayPal or credit cards, then BILLING information is required, and this is something your customers CANNOT avoid entering.. Your customers CANNOT pay via credit card on ANY site without entering BILLING information.. Your customers cannot pay via PayPal on ANY site without entering billing information..

shinypenguin:

Just finished getting the mod installed... there are several install files with discrepancies from the core files, possibly 1.3.9 files as another user suggested?

A few issues cropped up from preliminary testing:

(1) Couldn't log out of a COWOA account after checkout (have forced logoff enabled). Pages display the Log In link as though no account is logged in, but clicking the link goes directly to the account page for the COWOA account.

(2) After the original order confirmation email, subsequent order updates mailed to COWOA accounts have a link to the "account history" page, which requires a log in, rather than the "order lookup" page.

(3) After doing a sucessful order lookup with a COWOA account, adding an item to the cart breaks the shipping estimator. Also, clicking "checkout" goes directly to the COWOA checkout page without showing the account create/log-in page. On the shipping options page a blank address is entered (just a "," in the third line) -- presumably the reason for the broken shipping estimates.

(4) Having some major delays loading pages when testing the COWOA functionality. This may be a server issue, though they only seem to occur in IE9. Haven't noticed in either FF or chrome.

Certainly appreciate the contribution, just wanted to point out a couple install issues I had.

So what is the answer? I have the same exact issues as shinypenguin. v1.5.3 http://s l a d e w e b s-testarea.com/

loribug1:

So what is the answer? I have the same exact issues as shinypenguin. v1.5.3 http://s l a d e w e b s-testarea.com/

That post is from TWO YEARS and a few COWOA versions ago.. So the answer is to install the latest version of COWOA.. However, as has been stated in this support thread already, COWOA in the Zen Cart downloads/plugins section HAS NOT been updated for the latest version of Zen Cart.. There is a BETA version updated for v1.5.3 in Github.. It is NOT for use in a production site..

It would help if you tell us what version you have installed too..

After merging files and installing sql patch (I had to do this manually via phpMyAdmin, since there were errors through zen cart admin panel) I got empty page in Admin -> Configuration -> COWOA Configuration.
Also, I don't have column query_builder in my database, what to do with that?

jesus, this plugin is buggy...

Alright, I figured nice tip for those who have blank COWOA Configuration page.
If you type into Developers Tools Kit "COWOA_STATUS" (for example) in all-files search, there should pop up red option for searching database tables. If you click on this, and later "Edit", it should prompt correct COWOA Configuration, which is not accessible through Configuration dropdown.

Another problem: Now the last step of COWOA order gives me blank page. Something with the database again?

khejit:

After merging files and installing sql patch (I had to do this manually via phpMyAdmin, since there were errors through zen cart admin panel) I got empty page in Admin -> Configuration -> COWOA Configuration.
Also, I don't have column query_builder in my database, what to do with that?

jesus, this plugin is buggy...
Yeah.. so buggy that the Zen Cart devs are going to make this plugin part of the core..

COWOA is not buggy at all if installed normally.. based on your post you didn't go through normal install steps..

khejit:

Alright, I figured nice tip for those who have blank COWOA Configuration page.
If you type into Developers Tools Kit "COWOA_STATUS" (for example) in all-files search, there should pop up red option for searching database tables. If you click on this, and later "Edit", it should prompt correct COWOA Configuration, which is not accessible through Configuration dropdown.

Another problem: Now the last step of COWOA order gives me blank page. Something with the database again?Blank page means an error.. what's in your error logs..