DS-Dennis

Hello Smith, You explained my exact same issue and WHMCS support could not solve it while having full access to my system and I'm out of ideas as well. Were you able to solve this issue by this time? And if so, how did you manage? Regards, Dennis

This Addon does no longer work on WHMCS v6

Thank you for your advice and getting me on track. I overlooked the Sync setting on due dates which was also set to 0 days making it equal to expire dates. I could set it to 14 so invoices are send 14 days upfront plus this 14 days on domain renewals making it 28 days on domain renewals. But that is a global setting for any TLD so I'm not ok with that. Besides, autorenewal is done 30 days before expire date at eNom. So I disabled the sync on due dates and will switch to Hexonet for this particular TLD. eNom does not allow transfer in either while Hexonet does. What I found at Hexonet about this TLD: Restores can be processed in realtime. A restore is possible within 40 days upon deletion. I only have less profit but get a better situation in return.

It was renewed by the registrar due the automated renewal requirement for this TLD, to be precise, .be at eNom. After that, while the client did not yet pay the bill, WHMCS cronjob did run and sync the domain. I noticed that not only the expire date was synced but the renewal date as well. Now the client should still pay the bill and because of that, a year will be extended by WHMCS at eNom. I already did as you suggested and edited the domain record in the clients profile to have no registrar configured which I have to edit back after the payment. And of course edit the year back from 2016 to 2015 or wait till the cron corrects this. Either way, this is not an ideal situation on TLD's which are set to autorenewal at the registrar. I'll have to check if it still can be renewed if I switch of the auto renewal (if it supports early renewals). If so, then the client only risks his domain being lost if payment is not in time. If it does not, then I'm not sure yet what the best solution would be.

I would prefer to set the default nameservers at the registrar setup as different tld's may be registered through different registrars (Setup => Product/Services => Domain Registrars). So instead of a global setting it would be ideal to make this depended per domain registrar module the tld was registered at. I guess this is a feature request. - - - Updated - - - I searched and it was already been requested: https://requests.whmcs.com/responses/setting-default-dns-for-each-registrar

Hello, I just recently switched from a competitor so I monitor how WHMCS works closely. Now I noticed (I did enable sync domains) a domain was automated renewed according the TLD requirements. Then the cron runs and updates the domain expire date to November 2015 but the bill has yet to be paid by the customer. Now it is to be expected that if the customer does pay his bill, the system is going to renew the domain at the registrar. Which results his domain will expire November 2016 at the registrar, then after the cron runs the expire date will get updated so he is not going to be billed next year? I am just trying to foresee things as I am new to WHMCS or am just to worried and need some more confident in this system? If I am correct in this matter, what are the best options to avoid this behavior? Should I just disable the cronjob that syncs domains? Why would such sync be in place at all if it causes such havoc in terms of renewals?

I put my last request at the script developer of my cookie-law script. I dont think it has something to do with your analytics script.

Sir, you are correct again. The cookie-law requirement does work well now as I could verify by refreshing my page source and noticed the google analytics code appear/disappear when I enabled/disabled my cookie preferences on site. Now I may have an odd request maybe but I think it is common to enable and use cookies by default given the visitor the possibility to disable them. Currently I have a bar notifying my visitors that the site uses cookies. At that point analytics is disabled. When they hit the "Ok" button to close that bar, analytics will be enabled. However, on my configuration they notice now another tiny box which they can close, disable cookies or enable again. I would like to see cookies disabled when they specific disable them in this box, meaning that if they first visit the website cookies are enabled, when they hit the "Ok" for acknowledgement cookies are still enabled but when they hit "disable cookies" it obvious disappears. I think I have my website listed on my forum profile if you would want to see what I mean. Thanks for all the help thought.

Thank you panvagil, that was the case and after I unticked that option I could see the analytics code in the source of my pages. That is a nice feature so now I know this works I can tick this option again as I am not interested in my own visits. I do have an custom template, does that require some coding to think about? My previous question is also still valid about how I would get my cookie-law script to enable/disable User-ID tracking (or the entire analytics code) if the visitor disables cookies on my site.

On a side note, if I would get the code added into the my page header, how would I be able to edit this code to integrate with my cookie-law script? For example, google does require the webmaster to implement the option for visitors to agree or not to agree with Userd-ID tracking. As the google analytics account holder and webmaster you need to agree upon before google enables User-ID tracking. Your file is encoded so I don't see how I can get it to work with my cookie script. (I have your pro version)

I dont see any google tracking code added into the source of my pages. It does not seem to be working at all.

Nope but because of your link I found this topic and it seems pretty old as well: http://forum.whmcs.com/showthread.php?18031-eu-whois-server I am a new customer and downloaded the most recent version. I now question myself why such simple things did not made it within a released version to get a version that is working out of the box where possible ..... why leaving things to be fixed when a solution is provided? What more am I going to find while you all have fixed it before?

[uNCONFIRMED] Open and edit the file /includes/whoisservers.php Change: Into: Now we get an correct behavior on searching .eu domains.

I am in the progress of switching from an AWBS system to WHMCS and for so many TLD's it's a pain I have to go through. Because in AWBS we only set the prices for the first year. IF the extra years would be fine to add up, the system did the calculation. We only had to leave the prices set to 0.00 to make use of this. Lets say if the first year is sold at 9.45 and we set the price for five years to 0.00 the system would calculate 9.45x5=47.25 We only had to fill out all prices if we wanted prices outside this calculation schema. To make this work we need to set an extra config to tell the system what the minimum and maximum available years are for each TLD.