<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: PWA &amp; STS &#8211; Merging osCommerce Contributions</title>
	<atom:link href="http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html</link>
	<description>Showcasing osCommerce...the good, the bad and the ugly!</description>
	<lastBuildDate>Mon, 30 Jan 2012 16:32:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Sam</title>
		<link>http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html/comment-page-1#comment-4005</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Tue, 09 Feb 2010 12:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html#comment-4005</guid>
		<description>I have created an add-on that now incorporates the ideas given here:

Sam&#039;s Anti-hacker Account Mods V1.4

Features:

Provides a option to Remove password input requirement, if enabled visitors are redirected to checkout on completion and makes the personal details input a seamless part of the checkout.
A new option is added to require the user to input a &#039;strong&#039; password, or ensure generated passwords are &#039;strong&#039;. 
The date of birth field is now a drop down which automatically formats according to the store country, this ensures the format is correct, slashes (/) can still be sanitized and the visitor cannot transpose days &amp; months. 
The telephone field is checked its numeric (if entered) and contains only limited allowed chars. 
The fax field is checked its numeric (if entered) and contains only limited allowed chars. 
The post code field is checked for the correct format, but only for UK, USA, Canada, Australia &amp; France addresses, valid inputs will be reformated to standard code format. 
If strong password is enabled, password forgotten will generate strong passwords. 
The State/Province/County: field is pre-filled with the zones for the store country, rather than a blank field that gets populated on submit! 
The Country drop down is pre-selected to the store country. 
Ajax code is used to auto update the county drop down on change of Country Selection, operation is as similar as possible with javascript off. 
Name, Address, Suburb and City Fields are subject to additional validation, limiting word &amp; character count. 
Has new modules for name &amp; address validation used by all account pages. 
Has new &#039;single&#039; address input module (again used by all account pages) that orders the input adddress fields according to the supplied country address format. 
Contact Us is expanded with details based on ideas in Super Contact Us add-on, but orders id is taken from dBase &amp; provided as drop down. 
All input fields (post vars) are sanitized, any &#039;latin&#039; characters are allowed

Add-on is at http://addons.oscommerce.com/info/7202</description>
		<content:encoded><![CDATA[<p>I have created an add-on that now incorporates the ideas given here:</p>
<p>Sam&#039;s Anti-hacker Account Mods V1.4</p>
<p>Features:</p>
<p>Provides a option to Remove password input requirement, if enabled visitors are redirected to checkout on completion and makes the personal details input a seamless part of the checkout.<br />
A new option is added to require the user to input a &#039;strong&#039; password, or ensure generated passwords are &#039;strong&#039;.<br />
The date of birth field is now a drop down which automatically formats according to the store country, this ensures the format is correct, slashes (/) can still be sanitized and the visitor cannot transpose days &amp; months.<br />
The telephone field is checked its numeric (if entered) and contains only limited allowed chars.<br />
The fax field is checked its numeric (if entered) and contains only limited allowed chars.<br />
The post code field is checked for the correct format, but only for UK, USA, Canada, Australia &amp; France addresses, valid inputs will be reformated to standard code format.<br />
If strong password is enabled, password forgotten will generate strong passwords.<br />
The State/Province/County: field is pre-filled with the zones for the store country, rather than a blank field that gets populated on submit!<br />
The Country drop down is pre-selected to the store country.<br />
Ajax code is used to auto update the county drop down on change of Country Selection, operation is as similar as possible with javascript off.<br />
Name, Address, Suburb and City Fields are subject to additional validation, limiting word &amp; character count.<br />
Has new modules for name &amp; address validation used by all account pages.<br />
Has new &#039;single&#039; address input module (again used by all account pages) that orders the input adddress fields according to the supplied country address format.<br />
Contact Us is expanded with details based on ideas in Super Contact Us add-on, but orders id is taken from dBase &amp; provided as drop down.<br />
All input fields (post vars) are sanitized, any &#039;latin&#039; characters are allowed</p>
<p>Add-on is at <a href="http://addons.oscommerce.com/info/7202" rel="nofollow">http://addons.oscommerce.com/info/7202</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith W.</title>
		<link>http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html/comment-page-1#comment-3159</link>
		<dc:creator>Keith W.</dc:creator>
		<pubDate>Mon, 22 Jun 2009 21:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html#comment-3159</guid>
		<description>Well said.</description>
		<content:encoded><![CDATA[<p>Well said.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary</title>
		<link>http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html/comment-page-1#comment-3157</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Fri, 19 Jun 2009 09:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html#comment-3157</guid>
		<description>You, I and Brian all agree.  We just see things from different angles.</description>
		<content:encoded><![CDATA[<p>You, I and Brian all agree.  We just see things from different angles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith W</title>
		<link>http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html/comment-page-1#comment-3156</link>
		<dc:creator>Keith W</dc:creator>
		<pubDate>Fri, 19 Jun 2009 01:09:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html#comment-3156</guid>
		<description>Good to know someone has tried that, I guess we&#039;ll avoid the route allowing them to signup again and again, how does it ruin the admin area specifically? Does it cause any performance issues?

In regards to purchasing without an account it is a commonly held belief that it not requiring customers to create an account increases sales, it has been tested time and time again, every conference I go to including the Internet Retailer conference says to get rid of the registering. Here&#039;s just one of the articles from Bryan Eisenberg&#039;s company (Future Now or grokdotdom.com) about it, which I&#039;m sure you know he is very knowledgeable in the optimization field, there are dozens more articles about the forced creating account causing lost sales on their too.... http://www.grokdotcom.com/2007/10/03/yes-or-no-why-must-i-choose/</description>
		<content:encoded><![CDATA[<p>Good to know someone has tried that, I guess we&#039;ll avoid the route allowing them to signup again and again, how does it ruin the admin area specifically? Does it cause any performance issues?</p>
<p>In regards to purchasing without an account it is a commonly held belief that it not requiring customers to create an account increases sales, it has been tested time and time again, every conference I go to including the Internet Retailer conference says to get rid of the registering. Here&#039;s just one of the articles from Bryan Eisenberg&#039;s company (Future Now or grokdotdom.com) about it, which I&#039;m sure you know he is very knowledgeable in the optimization field, there are dozens more articles about the forced creating account causing lost sales on their too&#8230;. <a href="http://www.grokdotcom.com/2007/10/03/yes-or-no-why-must-i-choose/" rel="nofollow">http://www.grokdotcom.com/2007/10/03/yes-or-no-why-must-i-choose/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary</title>
		<link>http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html/comment-page-1#comment-3150</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Wed, 17 Jun 2009 13:55:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.clubosc.com/pwa-sts-merging-oscommerce-contributions.html#comment-3150</guid>
		<description>Oh - I do webmaster a site in which we have the ability for customers to keep signing up again and again.  It&#039;s not great, as it ruins the admin area - of course with lots more work I could code up a solution to tie up all the same customers, but it&#039;s simply not viable to do so.

I think you are thinking too much ;)</description>
		<content:encoded><![CDATA[<p>Oh &#8211; I do webmaster a site in which we have the ability for customers to keep signing up again and again.  It&#039;s not great, as it ruins the admin area &#8211; of course with lots more work I could code up a solution to tie up all the same customers, but it&#039;s simply not viable to do so.</p>
<p>I think you are thinking too much <img src='http://www.clubosc.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

