Martin C Posted October 26, 2010 Share Posted October 26, 2010 I wonder if somebody use the birthday module, I tested this module and it works really good, to good I believe.If a customer has a validated order and today is his birthday he will receive a voucher if a cronjob is running.But what will happen if he changed his birthday in his account to tomorrow.The cronjob is running again and yes he will receive a voucher again.Am I overlooking something or is it a possiblity to fraud!Martin Link to comment Share on other sites More sharing options...
rocky Posted October 27, 2010 Share Posted October 27, 2010 Yes, that it a problem. You could modify identify.tpl and disable or remove the birthday code from there. That way, the customer cannot change their birthday. They could only enter their birthday when registering. You'd need to add a note to authentication.tpl to let the customer know that they should enter their correct birthday when registering, since they can't change it afterwards. Link to comment Share on other sites More sharing options...
Martin C Posted October 27, 2010 Author Share Posted October 27, 2010 Thanks Rocky, That was also my idea to prevent duplicate vouchers Link to comment Share on other sites More sharing options...
deech123 Posted October 31, 2010 Share Posted October 31, 2010 rocky to commend out the part in your identity.tpl that's no problem.but when the customers tries to change something in his name or what ever, then when he pushed update, then his birthday becomes empty....any idea to solve this?ps, set the select to disabled works that the client can not change it, but still after update the date is empty. Link to comment Share on other sites More sharing options...
deech123 Posted October 31, 2010 Share Posted October 31, 2010 I found a correct way to solve this.first add before the select of the brithday this part. Now the user will see the birthday in a form field that is disabled.if he/she see that date is not correct they can contact you.go to the file in your theme folder/identify.tpland look for line 57 and then add/change this piece. {l s='Birthday'} <input type="birthday" name="birthday" id="birthday" value="{$smarty.post.birthday|date_format:'%d-%m-%Y'}" disabled/> and then the whole selection stuff you just hide it by the div.at : {l s='Birthday'} ...... - {foreach from=$years item=v} {$v|escape:'htmlall':'UTF-8'} {/foreach} so just add a div wrap around the whole select stuff.in that case when users change their name,password or whatever, then they don't change the date or reset it.hope this will help you out. Link to comment Share on other sites More sharing options...
ecoshop Posted November 29, 2010 Share Posted November 29, 2010 Hi !I had the same concern with the fraud problem. Thanks for the solution. But could you please be more specific to where (line #) and in what document we should make the change.Best regardsGonzalo Link to comment Share on other sites More sharing options...
deech123 Posted November 29, 2010 Share Posted November 29, 2010 I add the page and line in the post with the code. Link to comment Share on other sites More sharing options...
ecoshop Posted December 1, 2010 Share Posted December 1, 2010 That's right. Thanks Link to comment Share on other sites More sharing options...
deech123 Posted December 1, 2010 Share Posted December 1, 2010 change the subject to [sOLVED] if this problem is solved for you :-)greetz Link to comment Share on other sites More sharing options...
Recommended Posts