Jump to content

Chris74

Member
  • Content Count

    269
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Chris74

  1. That will do the job perfectly Brian - thanks for that.
  2. Using 7.8.3 currently. I noticed that if you create a sub account - even if it has no privileges it can use the "Payment methods" option and add / remove the main account payment methods. Can anyone confirm that this is fixed in a later version? I've checked the changelog and I can't find anything.
  3. This is probably quite simple but beyond my level of expertise. All I want to do is have an additional choice for another set of nameservers on the nameservers option of clientareadomaindetails.tpl When the client goes to change nameservers they are currently presented with two options... 1. Default Nameservers 2. Custom Nameservers I want to add another option 1. Default Nameservers 2. DNS Only Nameservers 3. Custom Nameservers I would also like the option to switch to these nameservers via single button click - so on a page where the domain ID is available - a single click of a button would update the domains nameservers to these (without navigating away from the page). If this is too complicated I'm happy with just the option on the nameservers page as above. Willing to pay a reasonable fee for this work to be done.
  4. In the General Settings > Invoices I have only Visa and Mastercard enabled. AMEX is not enabled. We are using Stripe. WHMCS is accepting AMEX payments. Is there a way to prevent this?
  5. Stripe module. Card with expiry date in the past was charged. Client's card was expired but then he was sent a new card with a new expiry date. Card details were not updated in WHMCS - so the old expiry date was still there. Problem 1. I thought WHMCS was supposed to automatically remove expired cards? There is an option in the automation settings to NOT delete expired cards if the box is ticked. The box is not ticked - therefore I would assume the card should be removed on expiry? Problem 2. WHMCS is still attempting payment on an expired card. Why? This was an issue for us today because the customer didn't want to renew - he assumed that the card in his account showing as expired would not be charged - but it was.
  6. You beat me too it! I'm an idiot. Nothing more to see here.
  7. Oh - I don't think commission is applied at all to domain registrations. That was a waste of 5 minutes posting on here. Sorry about that ๐Ÿ˜„
  8. Hi, is there a way to prevent affiliate commission being applied to domains?
  9. I recently moved our site to a new server which is IPV6 enabled. IPV6 is correctly configured and the servers IPV6 IP is added to our Nominet account for EPP Live. Port 700 is enabled in the firewall for outbound connections over IPV6 I don't specifically want to connect to Nominet over IPV6 but the WHMCS module will try IPV6 if it is available and it won't fall back to IPV4 if it has a problem. Unfortunately I'm getting "Error Connecting to tls://epp.nominet.org.uk on port 700". As soon as I disable IPV6 it connects over IPV4 again. I don't want to disable IPV6 on this server but I have to right now if I want the Nominet module to work. I was wondering if anyone here has successfully enabled IPV6 AND still been able to use the Nominet module in WHMCS. I'm trying to determine whether the issue is specific to my setup or whether the module just doesn't work over IPV6.
  10. Pretty bad that changing the case on an Email address causes such an error. I discovered this when a client set up their account with uppercase characters in their Email address and then tried to change it later to lowercase, they couldn't do it and received this error. It can be done successfully from the admin side though. I guess this is really a bug. @WHMCS John maybe something you need to fix? Also, I wonder why the error message is displayed when General Settings > Other > Display Errors is disabled?
  11. Excellent thank you. I wasn't ware there was a template for that!
  12. I really don't want to see error messages being displayed to my clients linking them back to the WHMCS documentation. Does anyone know how to stop that from happening? i.e to display a generic message without the debug info? I've looked through the settings inside WHMCS and I don't believe I have anything set up to show the full PHP error / stack trace to the client . Maybe I'm wrong there? I don't have General Settings > Other > Display Errors enabled. To re-create this problem, you only need to do something as simple as this... 1. Masquerade as a client by clicking the "Login as Client" option from within the WHMCS admin area. 2. Edit the clients profile details changing the first letter of their Email address to uppercase - i.e if their Email address was john.smith@blah.com - change it to John.smith@blah.com 3. Try to submit the changes - you will get this.... Oops! Something went wrong and we couldn't process your request. Please go back to the previous page and try again. If the problem persists, please contact us. Back to Homepage For additional assistance, please reference the WHMCS TroubleShooting Guide ยป WHMCS\Exception\Model\UniqueConstraint: A "WHMCS\User\Client" record with "email" value "John.smith@blah.com" already exists. in /home/username/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Model/Observer.php:0 Stack trace: #0 /home/username/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Model/Observer.php(0): WHMCS\Model\Observer->enforceUniqueConstraint(Object(WHMCS\User\Client)) #1 [internal function]: WHMCS\Model\Observer->updating(Object(WHMCS\User\Client)) #2 /home/username/public_html/clients/vendor/illuminate/events/Dispatcher.php(347): call_user_func_array(Array, Array) #3 [internal function]: Illuminate\Events\Dispatcher->Illuminate\Events\{closure}(Object(WHMCS\User\Client)) #4 /home/username/public_html/clients/vendor/illuminate/events/Dispatcher.php(221): call_user_func_array(Object(Closure), Array) #5 /home/username/public_html/clients/vendor/illuminate/events/Dispatcher.php(164): Illuminate\Events\Dispatcher->fire('eloquent.updati...', Array, true) #6 /home/username/public_html/clients/vendor/illuminate/database/Eloquent/Model.php(1675): Illuminate\Events\Dispatcher->until('eloquent.updati...', Object(WHMCS\User\Client)) #7 /home/username/public_html/clients/vendor/illuminate/database/Eloquent/Model.php(1534): Illuminate\Database\Eloquent\Model->fireModelEvent('eloquent.updati...') #8 /home/username/public_html/clients/vendor/illuminate/database/Eloquent/Model.php(1470): Illuminate\Database\Eloquent\Model->performUpdate(Object(Illuminate\Database\Eloquent\Builder), Array) #9 /home/username/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Client.php(0): Illuminate\Database\Eloquent\Model->save() #10 /home/username/public_html/clients/clientarea.php(0): WHMCS\Client->updateClient() #11 {main}
  13. @WHMCS John I'm not opening a ticket - your support is terrible and always results in you asking for access to my server. I'd rather gouge my eyes out with a spoon than pass on any sensitive data to your staff. I don't have any confidence that you will be able to help me via your helpdesk. I'd rather rely on community help than use your support. Sorry but that's the honest truth.
  14. Looking at the data in these tables - it's a complete mess. There are quite a lot of cards that are listed as American Express - but we don't accept Amex cards and we never have. The WHMCS settings are configured not to accept Amex. Something has happened during the upgrade to 7.8 which has completely messed up all the card data. There are a few problems relating to the "MyWorks Paypal billing" module that has also caused a mess. Customers now have in some cases three or four cards, when they only had one previously - in some cases at least two instances of the paypal billing "card" and normal card, and one with last four xxxx. I don't know where to start cleaning this up - other than to remove all payment methods and ask the clients to start again - but I really don't want to do that.
  15. Here's your PHP error... RuntimeException: Remote Storage Failed in /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Payment/PayMethod/Adapter/RemoteCreditCard.php:0 Stack trace: #0 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Payment/PayMethod/Adapter/RemoteCreditCard.php(0): WHMCS\Payment\PayMethod\Adapter\RemoteCreditCard->storeRemote('delete') #1 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/ClientArea/Account/PaymentMethodsController.php(0): WHMCS\Payment\PayMethod\Adapter\RemoteCreditCard->deleteRemote() #2 [internal function]: WHMCS\ClientArea\Account\PaymentMethodsController->delete(Object(WHMCS\Http\Message\ServerRequest)) #3 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/CallableHandler.php(26): call_user_func_array(Array, Array) #4 /home/USERNAME/public_html/clients/vendor/middlewares/fast-route/src/FastRoute.php(96): Middlewares\Utils\CallableHandler::execute(Array, Array) #5 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/HandleProcessor.php(0): Middlewares\FastRoute->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #6 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/AssumingMiddlewareTrait.php(0): WHMCS\Route\Middleware\HandleProcessor->_process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #7 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(76): WHMCS\Route\Middleware\HandleProcessor->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #8 [internal function]: Middlewares\Utils\Dispatcher->Middlewares\Utils\{closure}(Object(WHMCS\Http\Message\ServerRequest)) #9 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Delegate.php(31): call_user_func(Object(Closure), Object(WHMCS\Http\Message\ServerRequest)) #10 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/DelegatingMiddlewareTrait.php(0): Middlewares\Utils\Delegate->process(Object(WHMCS\Http\Message\ServerRequest)) #11 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Security/Middleware/Authorization.php(0): WHMCS\Security\Middleware\Authorization->delegateProcess(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #12 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/AbstractProxyMiddleware.php(0): WHMCS\Security\Middleware\Authorization->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #13 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/AssumingMiddlewareTrait.php(0): WHMCS\Route\Middleware\AbstractProxyMiddleware->_process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #14 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(76): WHMCS\Route\Middleware\AbstractProxyMiddleware->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #15 [internal function]: Middlewares\Utils\Dispatcher->Middlewares\Utils\{closure}(Object(WHMCS\Http\Message\ServerRequest)) #16 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Delegate.php(31): call_user_func(Object(Closure), Object(WHMCS\Http\Message\ServerRequest)) #17 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(56): Middlewares\Utils\Delegate->process(Object(WHMCS\Http\Message\ServerRequest)) #18 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/BackendDispatch.php(0): Middlewares\Utils\Dispatcher->dispatch(Object(WHMCS\Http\Message\ServerRequest)) #19 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/AssumingMiddlewareTrait.php(0): WHMCS\Route\Middleware\BackendDispatch->_process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #20 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(76): WHMCS\Route\Middleware\BackendDispatch->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #21 [internal function]: Middlewares\Utils\Dispatcher->Middlewares\Utils\{closure}(Object(WHMCS\Http\Message\ServerRequest)) #22 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Delegate.php(31): call_user_func(Object(Closure), Object(WHMCS\Http\Message\ServerRequest)) #23 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/RoutePathMatch.php(0): Middlewares\Utils\Delegate->process(Object(WHMCS\Http\Message\ServerRequest)) #24 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/AssumingMiddlewareTrait.php(0): WHMCS\Route\Middleware\RoutePathMatch->_process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #25 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(76): WHMCS\Route\Middleware\RoutePathMatch->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #26 [internal function]: Middlewares\Utils\Dispatcher->Middlewares\Utils\{closure}(Object(WHMCS\Http\Message\ServerRequest)) #27 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Delegate.php(31): call_user_func(Object(Closure), Object(WHMCS\Http\Message\ServerRequest)) #28 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/WhitelistFilter.php(0): Middlewares\Utils\Delegate->process(Object(WHMCS\Http\Message\ServerRequest)) #29 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/DelegatingMiddlewareTrait.php(0): WHMCS\Route\Middleware\WhitelistFilter->_process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #30 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(76): WHMCS\Route\Middleware\WhitelistFilter->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #31 [internal function]: Middlewares\Utils\Dispatcher->Middlewares\Utils\{closure}(Object(WHMCS\Http\Message\ServerRequest)) #32 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Delegate.php(31): call_user_func(Object(Closure), Object(WHMCS\Http\Message\ServerRequest)) #33 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/RoutableClientModuleRequest.php(0): Middlewares\Utils\Delegate->process(Object(WHMCS\Http\Message\ServerRequest)) #34 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/AssumingMiddlewareTrait.php(0): WHMCS\Route\Middleware\RoutableClientModuleRequest->_process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #35 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(76): WHMCS\Route\Middleware\RoutableClientModuleRequest->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #36 [internal function]: Middlewares\Utils\Dispatcher->Middlewares\Utils\{closure}(Object(WHMCS\Http\Message\ServerRequest)) #37 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Delegate.php(31): call_user_func(Object(Closure), Object(WHMCS\Http\Message\ServerRequest)) #38 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/RoutableAdminRequestUri.php(0): Middlewares\Utils\Delegate->process(Object(WHMCS\Http\Message\ServerRequest)) #39 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/AssumingMiddlewareTrait.php(0): WHMCS\Route\Middleware\RoutableAdminRequestUri->_process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #40 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(76): WHMCS\Route\Middleware\RoutableAdminRequestUri->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #41 [internal function]: Middlewares\Utils\Dispatcher->Middlewares\Utils\{closure}(Object(WHMCS\Http\Message\ServerRequest)) #42 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Delegate.php(31): call_user_func(Object(Closure), Object(WHMCS\Http\Message\ServerRequest)) #43 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/RoutableRequestUri.php(0): Middlewares\Utils\Delegate->process(Object(WHMCS\Http\Message\ServerRequest)) #44 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/AssumingMiddlewareTrait.php(0): WHMCS\Route\Middleware\RoutableRequestUri->_process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #45 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(76): WHMCS\Route\Middleware\RoutableRequestUri->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #46 [internal function]: Middlewares\Utils\Dispatcher->Middlewares\Utils\{closure}(Object(WHMCS\Http\Message\ServerRequest)) #47 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Delegate.php(31): call_user_func(Object(Closure), Object(WHMCS\Http\Message\ServerRequest)) #48 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/RoutableRequestQueryUri.php(0): Middlewares\Utils\Delegate->process(Object(WHMCS\Http\Message\ServerRequest)) #49 /home/USERNAME/public_html/clients/vendor/whmcs/whmcs-foundation/lib/Route/Middleware/Strategy/AssumingMiddlewareTrait.php(0): WHMCS\Route\Middleware\RoutableRequestQueryUri->_process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #50 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(76): WHMCS\Route\Middleware\RoutableRequestQueryUri->process(Object(WHMCS\Http\Message\ServerRequest), Object(Middlewares\Utils\Delegate)) #51 [internal function]: Middlewares\Utils\Dispatcher->Middlewares\Utils\{closure}(Object(WHMCS\Http\Message\ServerRequest)) #52 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Delegate.php(31): call_user_func(Object(Closure), Object(WHMCS\Http\Message\ServerRequest)) #53 /home/USERNAME/public_html/clients/vendor/middlewares/utils/src/Dispatcher.php(56): Middlewares\Utils\Delegate->process(Object(WHMCS\Http\Message\ServerRequest)) #54 /home/USERNAME/public_html/clients/index.php(0): Middlewares\Utils\Dispatcher->dispatch(Object(WHMCS\Http\Message\ServerRequest)) #55 {main}
  16. Thanks again @WHMCS John but so far I haven't got anywhere with this. Just to iterate what I want to achieve.... 1. I need to identify these rogue cards that you have set to XXXX I need to find them all. 2. I need to delete them all. Most of them appear to have an expiry date at least ten years into the future. EDIT - they ALL have an expiry date of 2029-12-31 00:00:00 So I've done a search in phpmyadmin and found 228 of these in tblcreditcards Can you please confirm the correct method / syntax to safely remove these cards.
  17. Thanks @WHMCS John Two problems with that... 1. If the card expiry date passed, the card cannot be used anyway. 2. Customer cannot remove these cards - there is a PHP error when they try. We can do it from admin - but they can't remove it. As per my original question, I'd like to remove all of these XXXX cards - can you provide a possible solution? I assume I can do this in PHPmyadmin? Could you provide a database query to identify them and let me know which record(s) needs deleting? Also, can you possibly answer my other question? What exactly happens if I use the " Delete Encrypted Credit Card Data" option in the security section of the config? Will this affect Stripe card data?
  18. delete me ta ๐Ÿ™‚
  19. Since upgrading to 7.8 I've noticed a lot of customers now have problems paying. We've only ever used Stripe for card payments so I'm not sure what the problem is exactly. One thing I notice is that some clients now have a payment method listed as Visa with Card-XXXX as the last four digits. They are unable to remove this card. We can do it from the admin side. I suppose my questions are... 1. Anyone else experiencing this issue? 2. How can we identify these problem cards and remove them on mass? Additionally, what exactly happens if I use the " Delete Encrypted Credit Card Data" option in the security section of the config? Will this only remove old stored card data "pre stripe"? Or will it remove all the tokens and current customer cards?
  20. Transaction failure on daily invoice cron. We're using Stripe. error => The PaymentMethod pm_xxx does not belong to the Customer you supplied cus_xxx. Please use this PaymentMethod with the Customer that it belongs to instead. detail => error => message => The PaymentMethod pm_xxx does not belong to the Customer you supplied cus_xxx. Please use this PaymentMethod with the Customer that it belongs to instead. param => payment_method type => invalid_request_error Customer went to pay the invoice manually later in the day and it worked. I'm pasting this here in case anyone else has the same issue.
  21. Nope. What I'm talking about is simply adding a .co.uk transfer to the cart and going to checkout. That's it. I can confirm that the error was happening before but it isn't now after applying the patch. Did you upload the files to your template folder? Assuming you are not using six.
  22. Just a zero priced transfer by itself. Not accompanying any other items. The checkout total was zero. We had the invalid positive integer message previously when customers were ordering a zero priced domain transfer in this way but now it's not happening.
  23. Ok I used one of our test accounts and added a card to it then placed an order for a free domain transfer. I noticed three things... 1. Even though I have VAT /TAX ID's disabled in the WHMCS configuration, the form when you add a card address asks for this info. BUG! Please take note @WHMCS John 2. I received an "invalid remote token" error at the checkout but it went through. This might be due to the account I used having previous stripe data - unsure about that. 3. I did not receive an "Invalid positive integer" error message.
  24. I can confirm that it is working fine for us now. You may have missed a file somewhere.
×
×
  • 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