stef

Hi, We use the SecPay module to process payments but recently we had 2 invoices where the transaction was duplicated and 2 lots of payment were taken from our customers. I spoke to SecPay about this and they traced the requests and found that the setting to switch off duplicate checking isbeing sent ("dups=false") meaning that duplicate transactions are more likely to go through. On the SecPay website it recommends that this setting is not used for live systems and describes the option as follows: "By default SECPay will stop the same transaction id from the same user being used twice in the same hour (this is to stop duplicates), to turn this feature off use 'dups=false'." Has anyone else had problems with this? Could it be added as module setting so that we can enable or disable duplicate checking from the admin area? Thanks for any help

Having looked into this a lot more it seems that it's actually nothing to do with the recipients but occurs if you don't fill anything in in the subject field, i.e. it blanks out all the recipients and says "The criteria selected for this email has resulted in no recipients which means it cannot be sent" If you fill in a subject and submit it tries to send even if you haven't got any recipients in the box so it obviously doens't mind the fact that there are no recipients to send to, it just doesn't like it if you don't supply a subject! Could this be a problem with the error reporting? I tried to look for the error string in the lang files but couldn't find it anywhere.

Thanks, but I was hoping you'd be able to do it on a client by client basis as i'ts only one customer who wants us to do this for them and all the others we need to store details for. I take it that's not the case?

In the miscellaneous new features of version 4.1.1 it says the following is available: "Credit Card Handling – new options have been added to disable credit card storage for those who want to process payments and discard the card information rather than storing for automated rebilling in future aswell as an option you can enable to allow the customer to choose whether their card is saved" Can anyone tell me if this is still the case having upgraded to 4.2.1 and if so, how do you do it, I can't find any options anywehere to enable this? Thanks for any help

Thanks, but why allow me to enter / select different information and then overwrite it? Sorry, but I don't find that intuitive at all. On a different note, why does the pricing information on the configurable option drop downs not show anymore when initally creating an order in the admin back end. It still shows once you go into an order to edit it but not in the first screen. I'm sure this wasn't the case before the upgrade? Thanks again

When I go to create an addon in the pop up window, if I select a different billing cycle (other than monhtly) and edit the price to reflect this it always reverts back to monthly and the standard monthly price when I save the changes. If I then go back into the record and re-edit it,(select annually, edit the price) and save again it remembers my changes this time. I assume it is applying the pricing structure set up for the add on originally but I also assume that this is a bug because it gives you the option to override these values when you set up the addon for a client. Not realising that it has set the values back to the monthly option has caused a few problems for us with clients so not having to re-check every time would be great.

Thanks, sorry I couldn't find any previous threads. Surpised nothing has been done about it.

A customer recently requested that a domain he owned was allowed to lapse after receiving an 'Upcoming Domain Renewal Notice' about it. We logged in and checked the 'Do-not renew' field for the domain and all was updated successfully. However, the following month he received the another renewal email for the same domain and was understandably confused. Surely if a domain is set to 'do-not renew' then no more renewal emails should be sent to the client about it? Have I missed something in the setup to stop this happening as it can't be right? Thanks for any help.

Thanks for the reply. Is it only me that thinks this a problem? I.e., if an invoice has already been created and the customer then opts to not renew it's going to take money from them for the renewal unless an admin is lucky enough to spot it and cancel the invoice before it is due? Also, when domain renewal notices are sent out it asks the client to log in and renew it themselves. At this point it has also created an invoice for the renewal which will get paid automatically if they have credit card details saved. If the client does log in and renew the domain another invoice gets generated and therefore payment will presumably be taken twice. We are having to find a way to remove the 'Renew Now' button from the front end if an invoice has already been generated to stop this happenning - surely this can't be right, or am i missing something?

If a customer invoice is generated for a domain renewal which they subsequently log in and set to 'do not renew', does payment still get taken because the invoice still exists? During my testing it looks as if requesting that a domain is not renewed has no other effect and if an invoice is there and credit card details are set up for the client then it will automatically take the payment. Can anybody tell me if this is the case? Thanks for any help.

All I can get from the Nominet Registrar module is the following error : Error: Connecting to ssl://epp.nominet.org.uk on port 700. The error message was '' (code 0) or : Registrar Error Error: Connection closed by remote server Has anyone else had this problem? Any help on this would be great. Thanks very much

I have created a domain registrar module for Network Solutions but when I try to process a domain renewal request via the manage orders page the checkbox to 'Send to registrar' is always disabled so the request never gets sent to them. I have written the RenewDomain function so it's not and have tried setting the expiry date to a reasonable value but with no success. Anyone know why this field is disabled and how to make it available? Thanks a lot for any insight.