Jump to content

MarceloPe

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

1 Neutral

About MarceloPe

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. yep, I unticked the options manually. Yet, I forgot to remove the ID Protect from the individual accounts, and given I deactivated it from enom, WHMCS says it cannot be deactivated, dah! so, I also run this query: UPDATE tbldomains SET idprotection = 0
  2. Thank you brian! Yes, users of ID Protect are less than 10 and they really won't notice the difference as enom already hide the whois information. I just sent a notification saying it won't be renewed as it's basically a defacto feature in the enom whois.
  3. Thank you very much, steven99, I didn't see that options. It's ok now. Best regards
  4. Hello everybody. Given that after GDPR implementation, vast majority of whois services don't publish specific information about owners of domains, it's a nonsense to continue selling ID Protect. Thus, I'm looking for a way to completely disable in my WHMCS. Is this possible? Otherwise I should charge a super expensive price for it in order to discourage people from purchasing it, not fair, right? If not possible right now, can you consider the possibility to add a switch in the configuration to shut down the option? or at the very least let me know what string should I edit to alter its description and discoourage those useless purchases to the people. Thanks in advance. Best regards.
  5. It worked great. THANK YOU GUYS!!
  6. MarceloPe

    How is 7.6 going for you so far?

    Hey there. Is there any public url where these bugs are published for us to read/subscribe/be_aware_of?
  7. Hello guys, after upgrading, I noticed that registered domains aren't showing the assigned DNS anymore. The DNS are alright when viewed from eNom.com UI itself, and are also visible when viewed as the customer. Only not working from the admin view. Fix this asap please! I still didn't tried to register/transfer a new domain, but this monday I surely have to, and I'm scared if those processes may have some bugs, too. Check it out please. I attached some images.
  8. Hello penguin, I've noticed this issue too. We set the new feature to delete users with more than 12 months, and it deleted newly created users on the last week 😞 The workaround I found is to enable the option "Disable Automatic Status Update" in the user profiles you don't want to be purged. That worked here. Hope to see a fix to this issue soon, as this is becoming a PITA cause if you forget to "protect" the status update of new users, you just lose them, and it's embarassing to ask them to re-register again whenever they claim they wanted to purchase something and could not find their account.
  9. MarceloPe

    ''AuxBilling contact Details are not vaild"

    Nope, they (eNom) just fixed the issue and the WHMCS integration returned back to normal operation
  10. MarceloPe

    ''AuxBilling contact Details are not vaild"

    Hey guys, I got some feedback from an eNom representative and after retrying changing ownership of a domain I can confirm IT NOW WORKS AS EXPECTED!!! So, sorry WHMCS' staff for bothering, and thanks to eNom tech staff if they can read this sometime
  11. MarceloPe

    ''AuxBilling contact Details are not vaild"

    Hello, same issue here. From what I understand, then eNom should make sure that aux/biling contacts become optional again? This issue is causing a lot of headaches on our side, as automated transfers are being putting us as the registrant, which is being perceived by some customers as hijacking domains. We don't like that and manually editing registrant info is a great undeisred workload. May you release an update that allow WHMCS customers to send aux/billing details as well to avoid this? Cause if eNom itself is taking that much time to solve it, you should release an updated module to help us, your customers I hope you can consider this seriously and release an update soon as adding those extra fields should be a no brainer for your developers. Don't you agree? I would be please to help adding the fix to the code if it weren't encoded, but it's not available, so it's up to you guys. Help us please. Very thanks in advance!!
×

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated