COWOA (for ZC v1.5.x)

[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

[DivaVocals]

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

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

[DivaVocals]

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

[DivaVocals]

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

Source: http://www.zen-cart.com/showthread.p...42#post1252042

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

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

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

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

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

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

Source: http://www.zen-cart.com/showthread.p...42#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..

[tromak]

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.

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

[DivaVocals]

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

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.

Noted, and I'll update the install instructions accordingly..

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

[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