plusplushosting Posted August 22, 2013 Share Posted August 22, 2013 Hi there, As yo uprobably know ICANN have made many changes in the policy to have alerts about domains expiry. I did open a ticket about it and we got a very useless reply saying we have to search in the fourm for a module done bu someone that cover it instead to have an official update about such an important update. Today i have received an email from NE1...this will also effect in all the others using LB platform with many changes about the gace period and also a possible Privacy Protection service switched to be paid. Wondering if someone at WHMCS is aware of it or if you wish i can forward the email to you. Mainly the following: - Renew Grace Period will be revised from 30 to 16 days for all .COM, .NET, .ORG, .INFO and .BIZ domain names. - The following TLDs will be changed from 40 to 36 days for .NAME, .CO, .PRO, .MOBI, .US, .ME and .TV domain names. Additionally, the Renew Grace Period for .IN domain names will be revised to 36 days from the current 15 days. After the 16th/36th day from expiry (depending on tld as listed above), the domain names will be queued for deletion by the system, and no modifications would be possible unless restored. The change to the 30 > 16 days (.COM, .NET, .ORG, .INFO and .BIZ) will take effect from 15th September 2013, the change from 40 to 36 days (.NAME, .CO, .PRO, .MOBI, .US, .ME and .TV) will be with immediate effect as well as .IN. Hopefully WHMCS come with an update for all these HIGH PRIORITY updates. Thanx! 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted August 22, 2013 Share Posted August 22, 2013 the renew grace periods can be modified by you in your configuration.php file... http://docs.whmcs.com/Domains_Configuration#Customising_Domain_Renewal_Restrictions i'm sure at some future update, WHMCS will modify the defaults to match the ICANN changes. 0 Quote Link to comment Share on other sites More sharing options...
plusplushosting Posted August 22, 2013 Author Share Posted August 22, 2013 Thanx Brian! to remind me about the configuration file...i have it somewhere in my mind Hopefully WHMC will come with an update for the rest of the icann changes. 0 Quote Link to comment Share on other sites More sharing options...
ethical Posted September 16, 2013 Share Posted September 16, 2013 further to this they are requiring specific notice about the changes to appear when a customer registers a domain name. right now we only have the ability to set special agreements for CIRA (.ca domains) so it would be really nice if we could also set special terms links that people have to view for these other TLD's as well. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted September 17, 2013 Share Posted September 17, 2013 further to this they are requiring specific notice about the changes to appear when a customer registers a domain name. right now we only have the ability to set special agreements for CIRA (.ca domains) so it would be really nice if we could also set special terms links that people have to view for these other TLD's as well. apologies if you knew this already, but the CIRA agreement is specified in additionaldomainfields.php - I don't think there's anything to stop you from copy&pasting for other tld's - though you would do it for each tld you wanted to set special terms for... i.e copy the following... $additionaldomainfields[".ca"][] = array("Name" => "CIRA Agreement", "LangVar" => "catldciraagreement", "Type" => "tickbox", "Description" => "Tick to confirm you agree to the CIRA Registration Agreement shown below<br /><blockquote>You have read, understood and agree to the terms and conditions of the Registrant Agreement, and that CIRA may, from time to time and at its discretion, amend any or all of the terms and conditions of the Registrant Agreement, as CIRA deems appropriate, by posting a notice of the changes on the CIRA website and by sending a notice of any material changes to Registrant. You meet all the requirements of the Registrant Agreement to be a Registrant, to apply for the registration of a Domain Name Registration, and to hold and maintain a Domain Name Registration, including without limitation CIRA's Canadian Presence Requirements for Registrants, at: http://www.cira.ca/assets/Documents/Legal/Registrants/CPR.pdf. CIRA will collect, use and disclose your personal information, as set out in CIRA's Privacy Policy, at: www.cira.ca/assets/Documents/Legal/Registrants/privacy.pdf</blockquote>",); and if you wanted to change it for "co.uk" domains, add the following in the uk section... $additionaldomainfields[".co.uk"][] = array("Name" => "Nominet Agreement", "LangVar" => "uktldciraagreement", "Type" => "tickbox", "Description" => "Tick to confirm you agree to the CIRA Registration Agreement shown below<br /><blockquote>You have read, understood and agree to the terms and conditions of the Registrant Agreement, and that CIRA may, from time to time and at its discretion, amend any or all of the terms and conditions of the Registrant Agreement, as CIRA deems appropriate, by posting a notice of the changes on the CIRA website and by sending a notice of any material changes to Registrant. You meet all the requirements of the Registrant Agreement to be a Registrant, to apply for the registration of a Domain Name Registration, and to hold and maintain a Domain Name Registration, including without limitation CIRA's Canadian Presence Requirements for Registrants, at: http://www.cira.ca/assets/Documents/Legal/Registrants/CPR.pdf. CIRA will collect, use and disclose your personal information, as set out in CIRA's Privacy Policy, at: www.cira.ca/assets/Documents/Legal/Registrants/privacy.pdf</blockquote>",); obviously, you would change the actual content of the message more than I have here(!)... but you just need to change the tld and "catldciraagreement" -> "uktldciraagreement" and you should be good to go... I gave it a quick test and it seemed to work fine. 0 Quote Link to comment Share on other sites More sharing options...
PhilB Posted June 16, 2014 Share Posted June 16, 2014 Related to this forum thread; please vote for the following feature request/enhancement to make it possible to "require" a checkbox be ticked (or any other arbitrary value be required, such as typing "I AGREE" in a text box): https://requests.whmcs.com/responses/additional-domain-fields-support-mandatory-compulsory-checkboxes-values 0 Quote Link to comment Share on other sites More sharing options...
malfunction Posted July 11, 2014 Share Posted July 11, 2014 Voted, but only three votes so far, so doesn't look like it's going anywhere Brian's idea is very good, and works, but inexplicably WHMCS doesn't stop you proceeding whether or not you check the box. Which is extremely lame. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted July 11, 2014 Share Posted July 11, 2014 Hi, Brian's idea is very good, and works, but inexplicably WHMCS doesn't stop you proceeding whether or not you check the box. Which is extremely lame. for some unknown reason, this isn't set to required by default in the additionaldomainfields.php file. as an example, if you amend the entry for .ca to include the REQUIRED variable, orders for these domains should not progress unless the checkbox is ticked... $additionaldomainfields[".ca"][] = array("Name" => "CIRA Agreement", "LangVar" => "catldciraagreement", "Type" => "tickbox", "Description" => "Tick to confirm you agree to the CIRA Registration Agreement shown below<br /><blockquote>You have read, understood and agree to the terms and conditions of the Registrant Agreement, and that CIRA may, from time to time and at its discretion, amend any or all of the terms and conditions of the Registrant Agreement, as CIRA deems appropriate, by posting a notice of the changes on the CIRA website and by sending a notice of any material changes to Registrant. You meet all the requirements of the Registrant Agreement to be a Registrant, to apply for the registration of a Domain Name Registration, and to hold and maintain a Domain Name Registration, including without limitation CIRA's Canadian Presence Requirements for Registrants, at: www.cira.ca/assets/Documents/Legal/Registrants/CPR.pdf. CIRA will collect, use and disclose your personal information, as set out in CIRA's Privacy Policy, at: www.cira.ca/assets/Documents/Legal/Registrants/privacy.pdf</blockquote>", "Required" => true,); so making this change to any similar entries should prevent the order progressing unless they are ticked. I think the latest version of the CIRA agreement might use a different second link - though the current pdf link redirects to the new page, so old settings should still work. if you wanted to modify the above and add hyperlinks that open in a new window, you could use the following: $additionaldomainfields[".ca"][] = array("Name" => "CIRA Agreement", "LangVar" => "catldciraagreement", "Type" => "tickbox", "Description" => "Tick to confirm you agree to the CIRA Registration Agreement shown below<br /><blockquote> You have read, understood and agree to the terms and conditions of the Registrant Agreement, and that CIRA may, from time to time and at its discretion, amend any or all of the terms and conditions of the Registrant Agreement, as CIRA deems appropriate, by posting a notice of the changes on the CIRA website and by sending a notice of any material changes to Registrants.<br><br>You meet all the requirements of the Registrant Agreement to be a Registrant, to apply for the registration of a Domain Name Registration, and to hold and maintain a Domain Name Registration, including without limitation CIRA's Canadian Presence Requirements for Registrants, at: <a href=\"http://www.cira.ca/assets/Documents/Legal/Registrants/CPR.pdf\" target=\"_blank\">www.cira.ca/assets/Documents/Legal/Registrants/CPR.pdf</a>.<br><br>CIRA will collect, use and disclose your personal information, as set out in CIRA's Privacy Policy, at: <a href=\"http://www.cira.ca/privacy/policy.html\" target=\"_blank\">www.cira.ca/privacy/policy.html</a>.</blockquote>", "Required" => true,); hope that helps. 0 Quote Link to comment Share on other sites More sharing options...
malfunction Posted July 12, 2014 Share Posted July 12, 2014 Yes it does help, good catch. Made that required for both Nominet and CIRA's terms which would seem to be the logical thing to do. Just have to remember to maintain it now. Thanks Brian. 0 Quote Link to comment Share on other sites More sharing options...
PhilB Posted July 13, 2014 Share Posted July 13, 2014 as an example, if you amend the entry for .ca to include the REQUIRED variable, orders for these domains should not progress unless the checkbox is ticked... No, not true. Try it; as per my conversation with WHMCS support, an "unchecked" checkbox is still "set" in HTML form terms and so passes the current "required" test in WHMCS. This is the reason for my feature request; I should have been more explicit that the current "required" functionality does not work in this case. In the case of CA domains my understanding is that the registry API requires the "CIRA Agreement agreed" value is passed at the registration call for it to succeed; so while the customer can order the domain it won't actually register when WHMCS tries to push it through. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted July 14, 2014 Share Posted July 14, 2014 No, not true. Try it; as per my conversation with WHMCS support, an "unchecked" checkbox is still "set" in HTML form terms and so passes the current "required" test in WHMCS. I did try it before posting - as I do with nearly all code that I post. with the required code added as above, an error message is displayed unless the checkbox is ticked - the order doesn't progress until it is ticked. In the case of CA domains my understanding is that the registry API requires the "CIRA Agreement agreed" value is passed at the registration call for it to succeed; so while the customer can order the domain it won't actually register when WHMCS tries to push it through. I didn't test it all the way to the registration stage as we don't sell .ca domains through whmcs, so I simply don't know whether the registration would go through or not... I read the issue as being that the checkbox needed to be required - how whmcs handles that info with the API is for the WHMCS coders to look at! 0 Quote Link to comment Share on other sites More sharing options...
PhilB Posted July 14, 2014 Share Posted July 14, 2014 (edited) I definitely tested this on windows with chrome using whmcs 5.3.7 and required did NOT stop the form being submitted with an unchecked box. I have a ticket and everything. There's nothing in the changelog for 5.3.8 to indicate this has been fixed. Hi, Thanks for contacting technical support. You can make a field required by adding the following to it's entry (there are some examples in the file already): "Required" => true However for checkboxes, both ticked and unticked are valid responses. Regrettably there isn't an option to require it to be ticked. However we welcome suggestions for new features on our feature request system: http://requests.whmcs.com Feel free to search existing feature requests, vote, comment and submit your ideas. If we can be of any more assistance, please don't hesitate to get back in contact. ------- Kind Regards, John Technical Analyst II ------- Have a great idea for WHMCS? http://requests.whmcs.com But I just tested it (again) on 5.3.7 and inexplicably it now works. I'm genuinely baffled. Edited July 14, 2014 by PhilB 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted July 14, 2014 Share Posted July 14, 2014 Hi Phil, But I just tested it (again) on 5.3.7 and inexplicably it now works. I'm genuinely baffled. WHMCS often has that effect on me too! 0 Quote Link to comment Share on other sites More sharing options...
malfunction Posted July 14, 2014 Share Posted July 14, 2014 Worked OK for me on 5.3.6, but I suppose i can look forward to it not working going forward by the sound of this. Gotta love WHMCS's use of words like "regrettably" like the whole thing is out of their control, followed by the standard "go bury your idea in the feature request system" (it's already there). 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted July 14, 2014 Share Posted July 14, 2014 at this stage, I wouldn't worry too much about it. i've had support tell me that something isn't possible before (after waiting 4 days for the reply!) - though in explaining to me how it wasn't possible to do it, it gave me a spark of an idea on a possible solution... which worked! the point being, support will have said that to me in good faith, but it might not necessarily be accurate - the only way to be sure is to try it and see. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.