Jump to content


Senior Member
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About shoelaced

  • Rank
  1. Checking out 7.10, looks cool so far. I was wondering about the new TLD sync feature. The importer only gives the option of markups, but I prefer to sell all my TLDs at the same price, which means different markups for different TLDs. If I sync the TLDs I currently sell, can I just leave the markup field blank and keep the prices I currently have set? Or am I misunderstanding the purpose of this tool? Is it necessary to sync TLDs that were set up via WHMCS in the first place, or is this tool only intended for TLDs that were set up directly with the registrar?
  2. I tried that, doesn't seem to work - although setting it to Basic URLs makes it do what it was doing before, where it would just stay on the login screen and print a message about the page being restricted. Maybe because I have the "always redirect to login" option turned on... I'll have to try turning that off when I have a sec. I only use it for my private clients for whom I manually make accounts, so the whole site is only accessible after logging in.
  3. Ha. Okay, well... any ideas on how I can debug this?
  4. Thanks for the reply. Just tested the Six template and it doesn't work either. When I hover over the button Chrome does say that it leads to https://mydomain.com/password/reset/begin, but the url in the url bar is https://mydomain.com/password/reset/login.php, and it gives me the too many redirects error. If I put the /password/reset/begin url into Redirect Checker, it produces the following (obviously I used my real domain): Result https://mydomain.com/password/reset/begin 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found login.php 302 Found So for some reason it appears to be getting caught in an infinite loop back to login.php. In my WHMCS settings I have the Friendly URLs on "Full Friendly Rewrite," which is the system-detected setting and I've clicked the little refresh icon there, which opts for Full Friendly Rewrite as well. But I've tried all the other URL settings and none of them work either. One thing I'm noticing is that when browsing around in the client area (everything else works fine), the URLs are all things like ?action=invoices, whereas I thought the Full Friendly Rewrite would make it something like /invoices. Is that normal?
  5. I have, as far as I know. I keep my custom theme in a Git repository so whenever there's an update I just delete my theme, FTP into the Six directory, copy everything down, and then just go through and discard all my changes that I want to keep (which are very minimal and mostly CSS) from the commit. Assuming the Six theme in my WHMCS installation gets updated along with everything else, my custom theme should practically just be a re-styled version of the latest Six. I just checked and my pwreset.tpl template is in fact empty... Is https://mydomain.com/password/reset/login.php the correct url for the password reset form? I'm not sure why it would be going through too many redirects after syncing the rewrite rules, given that previously my .htacces was completely empty. Now it only contains the auto-generated WHMCS rules.
  6. Update - I found that my "URI rewrite management" rules were out-of-sync and the auto-managed rewrite was turned off, and I am on an Apache server so I tried turning it on and syncing it. Now the password reset button tries to send me to "https://mydomain.com/password/reset/login.php" but it gives me a "too many redirects" error in the browser (Chrome). mydomain.com/pwreset.php still works though, so I suppose I'll just keep updating my theme to that...
  7. Hi all, The password reset button hasn't worked for a long time for me - I keep hoping a new update or a hotfix will fix it but I just updated to 7.9.2 and still nope. What happens is that when the user clicks the password reset button, it stays on the login screen and says "restricted." In order to fix it I have to go into my (custom) theme and change the placeholder in the button's `href` attribute to a hard-coded link to https://mydomain.com/pwreset.php. After that it works fine. It's been an issue for several releases and I figured if it was an actual bug there'd already be a fix for it, but I'm not finding other reports about it, so I'm guessing it's on my end somewhere but I have no idea what could be the issue. Has anyone else experienced this?
  8. @WHMCS John , Thanks for the reply. Yes, I've just tested it and it also happens when I switch to Six.
  9. Hm, okay update - If I choose PayPal Basic in the invoice, the buttons show up, but if I choose the new PayPal module, there are no buttons at all. Obviously this means I'm going to have to use the PayPal Basic module instead of the new one, so I assume this is a bug in the new module?
  10. Also I should note that I am using a custom template, but I've already updated it and ensured that the code there is correct.
  11. So I just updated from 7.8x to 7.9.1. Then I activated the new PayPal module and de-activated the old PayPal Express and PayPal Basic modules, then I read that we apparently still need the PayPal Basic module for subscriptions, so I re-activated it and added my API creds back in. Now it seems that there are no buttons in the invoices where the PayPal method is selected. If I set it to Credit Card the "pay" button shows up, but when I switch it to PayPal there are no buttons at all. So... is this an issue anyone else has noticed and is there a way to fix it?
  12. @bigsean My issue (I think?) seems to be okay now after I installed the Payment Gateway hotfix, but I still have no idea about the others, and I haven't installed them. If @brian! says to install them in that order then I'll probably try that too. Frankly, as @brian! also mentioned, I can't understand why they don't update the core when new hotfixes are released or bump the minor version so we can just install the damn things from the admin. This makes it a huge pain and we never know there's an issue or a hotfix until a CUSTOMER points it out, which obviously is very non-ideal. Hope they do something about it someday. As full-featured as WHMCS is it'd be nice if they started making it less clunky.
  13. @WHMCS ChrisD - sorry, where do I open a support ticket? WHMCS comes included with my reseller hosting plan through my host, so I'm only aware of this site.
  14. Thanks for the responses. So @WHMCS ChrisD, is the most recent one based on when it was posted, or when it says it was updated? For example for 7.8.3 it says that the Payment Gateway Issues one was most recently updated, but the Call to undefined function one was most recently posted in the first place.
  15. I have a question about the Hotfixes - if there are multiple for the same version of WHMCS and they contain the same file, are we supposed to manually combine the two versions of said file? For example, if I apply the CORE-13801 for v. 7.8.3, and then also want to apply the Payment Gateway Issues hotfix for v. 7.8.3, they both contain some of the same files, so if I download and replace as the instructions say, won't the second hotfix un-do the changes from the first? How do we apply multiple hotfixes?
  • 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