Jump to content

Recommended Posts

Hi All 

I tried to purchase a hosting package on mt whmcs and when i click the checkout button after filling out my details this error comes up. I have also checked with my payment gateway provider and they say it is whmcs problem. The site which i am referring to is https://skyehost.co.za/client/ I have also attached the error message below.


If the community could be so kind to help me with this problem.



Oops- (2).png

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Similar Content

    • By Manchester Web Hosting
      Hello everyone,
      Hoping someone can point me in the right direction. Bascially  after reviewing our video heatmaps we have found loads of drop offs on our checkout page due to potential new customers getting frustrted with having to keep inputting the password and security question IF the checkout form has any errors OR hasnt been filled out with all the required details.
      IF thats the case then the form refreshes and points out the errors. Now what we noiced is that the customer would the fill out OR correct the errors being pointed too and then submit BUT they dont fill out the password OR security question again as (I ASSUME) they think its already present when in fact its been cleared.
      Have seen potential customers going through the checkout form up to 10 times (I know right!) filling out the form and adding in missing OR fields that contain errors. Would be ideal IF they looked at everything and ensured that they filled out everything the first time round. A perfect customer alas thats not the case.
      SO trying to figure out how to keep anything inserted in the password and security answer fields at the very least saved AS they are for the personal fields (name + address) in case there is an error and the page spits out which errors those are. At the very least they wont have to add in those details again (as thats whats making them go round and round in circles!!!)
      Further, it would be great if that can also be applied to the card number and expiry field NOT the cvv tho for abovious reasons...
      I have checked the following files and cannot see where that removal takes place:
      js/jquery.payment.js js/scripts.min.js Also checked the HTML to see if there is any indicators there but cannot find anything. Pretty sure I am misssing something here i.e where the validation uccors maybe thats where those fileds are getting stripped?
      Any pointers to what I am missing OR how to implement that? I was thinking that dding in a class OR additional bootstrap class direct into the HTML field output would help?
    • By xnetco
      We've recently moved to Stripe and it's working very well for existing recurring card payments. However existing store credit cards don't appear on the checkout page. Do you know if it's possible to add them or migrate them all over to Stripe?
    • By hostblitz
      Got the: Oops! Something went wrong and we couldn't process your request. Please go back to the previous page and try again.
      Getting this error after upgrading from 7.9 to 8.02 
      Exception: Laminas\HttpHandlerRunner\Exception\EmitterException: Output has been emitted previously; cannot emit response in /public_html/billing/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php:24 Stack trace: #0 /public_html/billing/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitterTrait.php(40): Laminas\HttpHandlerRunner\Exception\EmitterException::forOutputSent() #1 public_html/billing/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitter.php(27): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->assertNoPreviousOutput() #2 /public_html/billing/index.php(0): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->emit(Object(WHMCS\ClientArea)) #3 {main}
      When I switch back to a really old template like the six or portal, the error does go away, but not any recent versions. Not really sure what is happening. 
      On PHP 7.3, but tried 7.2, 7.1, 7.0... to see if I could get the error to disappear. 
    • By Web Host Pro
      We have two credit card processors. One is only for existing customers and one is for new sign ups. I was wondering if we could disable a processor just in the public checkout, but still have it for existing customers that have a product.
      Basically disable a processor in the main checkout, then have it when adding products after the customer has a product.
    • By Web Host Pro
      I normally use Automatically take the user to the invoice, just wondering  which is more common and maybe some feedback on why.
  • Recently Browsing   0 members

    No registered users viewing this page.

  • 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