Hi, 3.a) This is technically and legally okay. But it is bad for the shop owner. The customer often does not know if they are already a newsletter subscriber or not. Even if you write a hint to the newsletter input: "Please activate the newsletter if you are a subscriber ..." they do not read it or they are not sure and let it empty. You are loosing subscribers.
3.b) It's a bug I would say. The position of asking to subscribe to the newsletter is not the best in Oxid. Why do not put it into the thankyou.tpl? The e-mail adress of existing subscribers could be validated before because it's known. Regards, Frank Viele Grüße, Frank Lehmann high feelings Claudia Liebold und Frank Lehmann GbR Flachstr. 11 65197 Wiesbaden Deutschland Telefon: +49 (0) 611 40 80 75 90 Telefax: +49 (0) 611 40 80 75 91 E-Mail: mailto:[email protected] Internet: http://www.high-feelings.de/ high feelings Newsletter - Immer aktuell bleiben >> Jetzt anmelden: http://www.high-feelings.de/service/newsletter.html high feelings auf Facebook >> Jetzt Fan werden: http://www.facebook.com/highfeelings -----Ursprüngliche Daten----- Datum: 13.05.2011 09:00:28 Von: anzido GmbH <[email protected]> An: <[email protected]> Betreff: Re: [oxid-dev-general] User registration after Newslettersubscription Vorgang: T-JQCJ4YW6ED-79 > Hi, > > 3.a) sounds correct to me: a newsletter checkbox is offered, and > independently of what the user chose before, if the user now does not check > the newsletter checkbox now, then this is a decision not to receive the > newsletter. This is an opt-out that has been deliberately chosen by the user > when filling out the registration form. > Apart from this, I don't think there is any other way to handle this: users > that didn't register for the newsletter before need the option to chose > whether to receive the newsletter when registering, and you cannot look up an > existing newsletter registration until the user has entered an email address > in the registration form and submitted it. The only way to deal with this in > another way would be an additional screen asking whether to really cancel the > previous newsletter subscription... > Another thing to take into account is that if a user deliberately registers > without an account (without setting a password), then pre-selecting the > newsletter checkbox or asking whether to cancel an existing newsletter > registration would appear as a clear violation of privacy expectations: when > ordering without opening a customer account, i would not expect the shop to > know anything about me the next time i interact with the shop ;-) > > 3.b) I would consider this a bug. If the email address has been previously > registered for the newsletter and the opt-in has already been confirmed, then > there is no reason for a second opt-in for the same email address. > Beste Grüße aus Dortmund! > Robert Rosendahl | Entwicklung u. Support > > -- > anzido GmbH > Kirchhörder Str. 12 > 44229 Dortmund > Tel.: 0231 - 60 71 079 > Fax.: 0231 - 60 71 081 > Mobil:0176 - 8325 1488 > Email: [email protected] > Web: http://www.anzido.com ( http://www.anzido.com/ ) > > > USt-ID: DE257982972 > Geschäftsführung: Andreas Ziethen > Amtsgericht Dortmund HRB 20883 > > > > > > > -----Ursprüngliche Daten----- > Datum: 12.05.2011 22:00:13 > Von: .NFQ | Martin Bornack <[email protected]> > An: [email protected] <[email protected]> > Betreff: [oxid-dev-general] User registration after Newsletter subscription > Vorgang: T-JQCJ4YW6ED-79 > > > Hi, > > > > > > > > we stumbled upon a certain shop behavior concerning the newsletter > > registration which is a bug in our eyes and just wanted to know if you see > > it differently or agree with us. ;) > > > > > > > > 1. A user comes to the shop and subscribes to the newsletter. -> oxuser > > entry and oxnewssubscribed entry (oxdboptin = 2, oxsubscribed = now(), > > oxunsubscribed is empty) added. > > > > 2. The user clicks the double optin. -> oxnewssubscribed entry is changed > > (oxdboptin = 1). > > > > 3. Then the user registers in the shop ndash no matter if he registers with > > or bdquowithout accountldquo (bdquowithout passwordldquo is more like it) > > and > > > > a. does NOT set the NL flag (hellipagain ndash he is already registered) -> > > oxnewssubscribed entry is changed (oxdboptin = 0). > > > > b. DOES set the NL flag -> oxnewssubscribed entry is changed (oxdboptin = > > 2, oxsubscribed = now()). User getrsquos a new double optin mail > > > > > > > > In the first case the user wonrsquot get the NL anymore without any notice, > > in the second case he has to revalidate his emailhellip > > > > > > > > > > > > Best regards, > > > > i.A. Martin Bornack > > > > > > > > ----------------------------------------------------- > > > > [ . nfq] netzfrequenz GmbH > > > > manager technical development > > > > martin bornack > > > > bergiusstraße 13 > > > > 86199 augsburg > > > > > > > > telefon: +49 (821) 9000 611 > > > > fax: +49 (821) 9000 619 > > > > > > > > http://www.nfq.de > > > > http://www.nfq-module.de > > > > ----------------------------------------------------- > > > > > > > > > > > >
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
