Jump to content

Integrated domain checker redirects to client login


redhot

Recommended Posts

Hi there,

 

I have the domain checker integrated into my website in a few places with the use of the integration code. This function was working properly on v5.2.13 before my most recent update to v5.2.16 (was on holiday for a bit so it hadn't been updated yet).

 

Whenever trying to check a domain name, it simply redirects to the client login page - even if I am already logged in on a user test account.

 

Here is the domain

/http://orbhost.co.nz/domain-names/

 

Both domain checkers on this page (below the navigation, and just before the footer begins) have this fault.

 

I've looked at the domain checker integration code and it appears to no longer have the following string as it used to:

 

<input type="hidden" name="token" value="75bf75a2261b32da9da8fdb60b64700b89f71319" />

 

The only difference as far as I can see with my code was the token value string, but I have tried removing this to no avail.

 

Here is my current integration code (mixed in with CSS, this was working properly at the end of last year):

<div class="domainsearch">
 <div class="row">
   <div class="twelve columns text-center">
<form action="https://orbhost.co.nz/clients/domainchecker.php" method="post">
<input type="hidden" name="direct" value="true" />
<div class="two columns formpadding">
<p>Domain Lookup</p>
</div>
     <div class="six columns formpadding">
       <input type="text" placeholder="(eg. business name)" name="domain" size="20" />
     </div>
     <div class="two columns formpadding">
     <select name="ext">
     <option>.co.nz</option>
     <option>.net.nz</option>
     <option>.org.nz</option>
     <option>.geek.nz</option>
     <option>.com</option>
     <option>.net</option>
     <option>.org</option>
     <option>.com.au</option>
     <option>.net.au</option>
     <option>.org.au</option>
     <option>.co.uk</option>
     <option>.org.uk</option>
   </select>
    </div>
     <div class="two columns formpadding">
       <input type="submit" value="Search" class="button" />
     </div>
</form>
</div>
</div>
</div>

 

Any help would be appreciated - did a search and couldn't find anything about my problem within the last 6mo.

 

Cheers.

Link to comment
Share on other sites

I don't know if this will help, but Chrome gives the following errors after submitting a test domain search to the search box near the footer...

 

The page at 'https://orbhost.co.nz/clients/clientarea.php' was loaded over HTTPS, but ran insecure content from 'http://fonts.googleapis.com/css?family=Droid+Sans:400,700': this content should also be loaded over HTTPS.

clientarea.php:21

 

Uncaught SyntaxError: Unexpected token , clientarea.php:28

I've quickly tested our integration code on 5.2.16 and it seems to be working fine.

Link to comment
Share on other sites

oh sorry forgot to mention that... the working integration code given by whmcs in v5.2.16 does NOT include a token value.

 

<form action="http://www.mydomain.com/domainchecker.php" method="post">
<input type="hidden" name="direct" value="true" />
Domain: <input type="text" name="domain" size="20" />
<select name="ext">
<option>.com</option>
<option>.net</option>
<option>.org</option>
</select>
<input type="submit" value="Go" />
</form>

Link to comment
Share on other sites

Thanks for that... have ended up changing it instead to the 'domain ordering' code as a bit of a workaround.

 

It redirects to the domain order form successfully now, but doesn't pass the actual search text into the form on this page.

 

Example: search test555.co.nz in one of the integrated domain checker boxes, and it redirects to the domain ordering page without the text - essentially making customers have to type it in again.

 

(banging head against wall)

 

May just add this to my 'to-do' list and come back to it shortly with a clear head...

Link to comment
Share on other sites

looking at your code, I think you've missed off two fields... here's the integration code from my whmcs..

 

<form action="http://www.mydomain.com/cart.php?a=add&domain=register" method="post">
Domain: <input type="text" name="sld" size="20" /> <select name="tld">
<option>.com</option>
<option>.net</option>
<option>.org</option>
</select>
<input type="submit" value="Go" />
</form>

there is probably no need for your hidden field - and you're not passing sld & tld in your form... perhaps this is why the entered domain / tld is not being passed to the cart?

Link to comment
Share on other sites

looking at your code, I think you've missed off two fields... here's the integration code from my whmcs..

 

<form action="http://www.mydomain.com/cart.php?a=add&domain=register" method="post">
Domain: <input type="text" name="sld" size="20" /> <select name="tld">
<option>.com</option>
<option>.net</option>
<option>.org</option>
</select>
<input type="submit" value="Go" />
</form>

there is probably no need for your hidden field - and you're not passing sld & tld in your form... perhaps this is why the entered domain / tld is not being passed to the cart?

 

:D!

 

I quickly changed the URL for the 'domain ordering' code and I hadn't noticed those other changes.

 

It's working now - thanks Brian! I've done away with the 'domain availability lookup' code as it seems like an extra step in the ordering process anyways.

 

Enjoy the rest of your weekend.

Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

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

Guest
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.

  • 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