Jump to content

mcpacific

Member
  • Posts

    118
  • Joined

  • Last visited

About mcpacific

mcpacific's Achievements

Senior Member

Senior Member (3/3)

0

Reputation

  1. Apparently the "Login as Owner" function will not work with NGINX. Support is no help. Have you found a solution for that?
  2. This is really a shame, and in my opinion a step backwards for user experience.
  3. Hi, I noticed with my WHMS installation, when a customer places an order for domain (only) they get a "go to cart" button and get redirected to the view cart page right after they select their domain, without going to the configure domain page. Is there a way to get the flow to go to the domain configuration page next, before going to the cart?
  4. No, I am using the built-in native domain search.
  5. I double-checked, no extra | anywhere. Also, the domains immediately before and after .cloud work. Pretty much anything I put in with .cloud doesn't work (says it's not available). This is what the module log shows: <?xml version="1.0" encoding="utf-8"?> <interface-response> <Domain>microsoftthgffngfgh.cloud</Domain> <RRPCode>541</RRPCode> <RRPText>TLD is not live</RRPText> <Domain>microsoftthgffngfgh.com</Domain> <RRPCode>210</RRPCode> <RRPText>Domain available</RRPText>
  6. .club|whois.nic.club|Not found
  7. I get this: Sorry! seejay2.cloud is already taken!
  8. That's what I thought but it fails on every query.
  9. Anyone know the whois for .cloud?
  10. It seems that there should be a way to use hooks to do this, but perhaps only to add new panels (and change things like color using custom.css). Anyone else have any thoughts at all on this?
  11. I've seen the examples for creating new panels, but what about updating existing (default) ones? How would I update the color, for example?
  12. I downloaded their most recent version at https://forge.kayako.com/projects/whmcs and it works fine with v6 (I'm just upgraded to v6.0.2). I use it for both support tickets and KB. When I had the same problem they told me to do this: Replace: error_reporting(E_ALL ^ E_NOTICE ^ E_WARNING); ===== With: ===== error_reporting(E_ALL ^ E_NOTICE ^ E_WARNING ^ E_STRICT); I also stopped seeing warnings when I turned off (unchecked) Display Errors under Setup > General Settings > Other.
  13. I'm not sure if this is new to v6.0.1, but I see from the Module Log that the Enom name check sends out the sld, along with the list of all tlds that are configured in the domain pricing table (ie. TLDList). Although Enom's API documentation specifies only 30 tlds are allowed in the TLDList, the API still responds with up to 50 domain names. The problem is that if the tld being checked is beyond #50 in your domain pricing table, the Enom API fails to reply with the specified tld at all and WHMCS returns "sld.com" is not available (if .com is indeed, not available, presumably because .com is first in the domain pricing table). If sld.com IS available, it returns with a positive search result (for the .com but not the tld specified). It seems that the Enom check command should insert the searched tld(s) at the front of the TLDList to yield proper results. I assume this means a bug fix for the domainchecker.php file. This seems to only be an issue if Enom NameSpinner is enabled under Setup > General Settings > Domains > Domain Lookup.
  14. I have a custom page for a module I built, and I noticed when trying to migrate to the v6 template, it does't work as expected. First of all, I'm unable to get the whole page to load in the client area. Instead, it loads the page in the main content div. Due to the width requirements of tabular data, it would be better as a whole page. I guess if this can't be avoided I'll have to scale font sizes lower but it might have a readability issue. Also, I noticed that hyperlinks in my custom template page don't work. They are there, but when I click on them nothing happens. Strangely, they do work if you right-click on them, then click "Open". So weird. Any ideas anyone?
×
×
  • Create New...

Important Information

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