Request to upvote -> WHMCS Registrar Lock Feature Extension/Review

[PapaKai]

Please, add your votes to that feature request. This is improving registrar integrations in direction to specific ccTLDs and leads to a smoother domain registrar integration and page load improvement.
I've seen that topic often enough addressed via customer support on our end (and even here in the community board).

Thanks guys!

 

-> https://requests.whmcs.com/idea/hide-register-lock-menu-from-the-domain-which-cant-be-locked

Edited August 19 by PapaKai

[Evolve Web Hosting]

@PapaKai Just added my vote!

[Remitur]

Just voted!!!! (even if, as we sadly know, feature request is completely useless...)

[PapaKai]

@Remitur @Evolve Web Hosting thanks so much!

 

Yes, the feature request section is useless. Still, if most of our WHMCS  customers would upvote feature requests that are of help for us, the number of upvotes would push WHMCS to work on that.
By that I am giving it try...

[Mytihost]

Couldn't this be achieved by using a hook to disable the specific features for .eu domains etc

[PapaKai]

Please navigate to the last page of the feature request. I provided there more insights. Someone spam commented the feature request and made that part by that no longer directly accessible to others.

[Remitur]

7 hours ago, PapaKai said:

Please navigate to the last page of the feature request. I provided there more insights. Someone spam commented the feature request and made that part by that no longer directly accessible to others.

It's crazy that WHMCS is not able to manage spam on its own site...  😶

I have here a note about your comment:

A workaround is possible editing clientareadomaindetails.tpl, with something like this:

        {if $lockstatus eq "unlocked"}
            {if $domain|substr:-3 == '.eu' ||  $domain|substr:-3 == '.ru'}
            {else}
               {capture name="domainUnlockedMsg"}<strong>{$LANG.domaincurrentlyunlocked}</strong><br />{$LANG.domaincurrentlyunlockedexp}{/capture}
               {include file="$template/includes/alert.tpl" type="error" msg=$smarty.capture.domainUnlockedMsg}
             {/if}   
        {/if}

This prevents the "domain unlocked" alert banner for .eu and .ru domains...

I see that there's also the $managementoptions.locking smarty variable which maybe can be useful...

Edited August 26 by Remitur

[PapaKai]

While I enjoy getting ideas at hand, I have to admit that I am looking for an entirely registrar module driven solution. Let me call it "the right way" 🙂

Yes, template changes work. WHMCS should move giving domain registrars and their resellers finally a better experience than let them deal with hacks and workarounds.
Basically, using a hook you can override those template vars as well. That's what we're doing. We just noticed that whenever Registrar X and Registrar Y following that hook approach that Registrar Y (alphabetic order) is overriding the template vars returned by Registrar X. Template Variables are by that a more stable solution.

While it sounds ideal hardcoding it there, it is still the scope of registrar integrations handling that.

• domain registrar systems know about which TLDs support Registrar Lock
• so, no template changes required
• so, no hook subscriptions required (that finally slow down the page load when combined with real-time registrar-api data lookup)
• straight forward
• improved UX / UI 

Cheers

[PapaKai]

bump - if you could vote again please 🙂