Contributions

if ((ALLOW_AUTOLOGONLOGON == 'false') || ($HTTP_POST_VARS['remember_me'] == '')) {

should be

if ((ALLOW_AUTOLOGON == 'false') || ($HTTP_POST_VARS['remember_me'] == '')) {

With the current logoff.php modification the user is never able to logoff creating a potential security risk.

The programmer forgot to put the value parameter when cleaning the cookies.

These are the lines that need to be changed:
From:
setcookie('email_address', time() - 3600, $cookie_path);
setcookie('password', time() - 3600, $cookie_path);

To:
setcookie('email_address', '', time() - 3600, $cookie_path);
setcookie('password', '', time() - 3600, $cookie_path);

Please note that, obviously, they are two single quotes in each line.

I attach the corrected file only.

This is only a modification of the german language file! -> info_autologon.php

Full package with .zip
That's all.
original credits to the contributor.

Hi all,

this is only a zip file containing all last changes and all laguages files.

just to have a full package to download.

All credit to the great people who made this mod and update it.

bye

The SEO update below is great, but it gave me an error and I checked the code, there's a parentheses missing.

This is the exact same file as HallMarc's below, with just the change added. So download this one, or download his and do this change to catalog/login.php instead:

In catalog/login.php


Change:
if(ALLOW_AUTOLOGON != 'false') {

to:

if((ALLOW_AUTOLOGON != 'false') && ($cookies_on == true)) {

that's it. All credit to the great people who made this mod and update it.

I noticed that my site wasn't appearing in any organic SERP's! I ran my URL through a spider simulator and nothing was coming back. I searched and searched for the cause and finally found it here.

All I did was put it all together for others and upload it here. All thanks should go to th original author, dreamscape and allymacneil.

support for this can be found at http://forums.oscommerce.com/index.php?showtopic=33523&hl=Autologon&st=0

I've encountered a problem with indexing of a site with this contrib used. All SEO tools are unable to access site because of this module. I solve this problem. Not sure if it's right but sollution is in the appended file.

v1.08a Translated for brasilian portuguese and altered Login Box in main page for autologon too.

this is not full package... get Damiel Harrison's 1.08

If you have trouble when you click logoff after enabling this mod, my error was 'expected $ or T_string or sth like that'

login.php mod has little problem....

This fixes it!!!

This file contains two files...

if you have no changes done in catalog/login.php prior to this mod, just replace to one I have in there.

otherwise, use text file and add that

Hope this helps!!!

Cosmetic Changes.

English description file still contained Spanish headings. Modified readme.txt to make installation instructions for catalog/includes/functions/password_funcs.php more understandable.

Package contains all files from v1.07

Previous contributor did corrupt the english file with his spanish version.
Renamed the spanish directory to espanol for consistency with the official distrib.
Removed copypaste directory, too unsafe.
French version added.

This is just a little modification of the german language file!

v1.06: Minor update, included complete files for copy/paste installation (optional). Added missing info in the Readme file and Spanish Translation.

Only tested in my OSC2.2-MS2 Store, and with I.E 6

Seems that this contribution doesn't work with ip type url's. Ex. 64.19.284.23/yourstore/

There are a forum about this contribution in:
http://forums.oscommerce.com/index.php?showtopic=45288&hl=autologon

besseres deutsch - nur schnell übersetzt, also wer was besseres weiß, nur her damit ;)

better translation

I've made two changes to this contribution because it did not work in my case. That's maybe because I use a subdomain.
See text file for details.

Updated so this should now work on a virgin install of OSC 2.2 MS2

Now should work with MS2 (no more Query was empty errors). + Polish translation

Around jan 10, 2003 the OSC password-functions were changed. Not only the functionnames were changed, but the code which compared the input directly to the stored password in the database (thus making unencrypted passwords possible, but also allowed for encrypted password storing at the client-side) was removed. This effectivily breaks the AutoLogon contribution up to v1.02. This version corrects this. The logic of v1.03 also contains changes to adapt to the changed EmailAddress-cookie behaviour introduced in OSC on jan 14 2003. The EmailAddress-cookie is only saved when autologon is allowed (Admin setting) AND the customer wants to be remembered. I also changed the code to update the password-cookie when the customer changes his password through my-account. To wrapup things: I took the opportunity to speed things up a bit.

VERSION 1.03 CANNOT BE USED WITH SNAPSHOTS OLDER THAN JAN 17, 2003

Added missing JavaScript code to login.php.chg. This error lead to the readme-link not working. Thanks to Mattice for reporting this bug.

=====================

During testing of my "shop-to-be", I got tired of signing in each time. Furthermore the enthousiastic greeting from the standard OSC-software, calling me by name, but not really knowing who I was, became rapidly annoying. And when it annoys me, it probbably also annoys my customers! And annoyed customers is *not* what I want...

This contribution provides a way to deal with this. Basically, next to the email-address (which is already stored in a cookie by standard OSC-software), it also stores the md5-encrypted password. When the customer returns, this information is used to execute an automatic signin.

M@rcel

Sam (from Iberinternet Solutions S.L.) reported a missing '{' in application_top.chg. It's fixed.
Thank you, Sam!

During testing of my "shop-to-be", I got tired of signing in each time. Furthermore the enthousiastic greeting from the standard OSC-software, calling me by name, but not really knowing who I was, became rapidly annoying. And when it annoys me, it probbably also annoys my customers! And annoyed customers is *not* what I want...

This contribution provides a way to deal with this. Basically, next to the email-address (which is already stored in a cookie by standard OSC-software), it also stores the md5-encrypted password. When the customer returns, this information is used to execute an automatic signin.

During testing of my "shop-to-be", I got tired of signing in each time. Furthermore the enthousiastic greeting from the standard OSC-software, calling me by name, but not really knowing who I was, became rapidly annoying. And when it annoys me, it probbably also annoys my customers! And annoyed customers is *not* what I want...

This contribution provides a way to deal with this. Basically, next to the email-address (which is already stored in a cookie by standard OSC-software), it also stores the md5-encrypted password. When the customer returns, this information is used to execute an automatic signin.

The login.php language-files were missing. FIXED

During testing of my "shop-to-be", I got tired of signing on each time. Furthermore the enthousiastic greeting from the standard OSC-software, calling me by name, but not really knowing who I was, became rapidly annoying. And when it annoys me, it probbably also annoys my customers! And annoyed customers is *not* what I want...

This contribution provides a way to deal with this. Basically, next to the email-address (which is already stored in a cookie by standard OSC-software), it also stores the password (security: see readme.txt). When the customer returns, this information is used to execute an automatic signin.

A designflaw has been fixed, do NOT use older versions of this contribution.

During testing of my "shop-to-be", I got tired of signing on each time. Furthermore the enthousiastic greeting from the standard OSC-software, calling me by name, but not really knowing who I was, became rapidly annoying. And when it annoys me, it probbably also annoys my customers! And annoyed customers is *not* what I want...

This contribution provides a way to deal with this. Basically, next to the email-address (which is already stored in a cookie by standard OSC-software), it also stores the password (security: see readme.txt). When the customer returns, this information is used to execute an automatic signin.

Oops, missed a file in 0.90, sorry!

During testing of my "shop-to-be", I got tired of signing on each time. Furthermore the enthousiastic greeting from the standard OSC-software, calling me by name, but not really knowing who I was, became rapidly annoying. And when it annoys me, it probbably also annoys my customers! And annoyed customers is *not* what I want...

This contribution provides a way to deal with this. Basically, next to the email-address (which is already stored in a cookie by standard OSC-software), it also stores the password (security: see readme.txt). When the customer returns, this information is used to execute an automatic signin.

During testing of my "shop-to-be", I got tired of signing on each time. Furthermore the enthousiastic greeting from the standard OSC-software, calling me by name, but not really knowing who I was, became rapidly annoying. And when it annoys me, it probbably also annoys my customers! And annoyed customers is *not* what I want...

This contribution provides a way to deal with this. Basically, next to the email-address (which is already stored in a cookie by standard OSC-software), it also stores the password (security: see readme.txt). When the customer returns, this information is used to execute an automatic signin.