Jump to content

[FIXED] Security Update Patch - Domain Reg error


Recommended Posts

For 5.1.4, yes - Ironing the rest out across the board right now. ATTN: Chris

 

As of when? I use 5.1.3 and uploaded the 5.1.4 security patch (downloaded off the site just 20 minutes ago) and I too have the domain reg issue. No way am I upgrading to 5.2 yet. (I'm happy to let others do the final beta testing on a 'stable' release this time round after the last full upgrade) :-)

Link to comment
Share on other sites

OK, there's definitely an issue with the new domainchecker.php file in the 5.1.4 patch.

 

I re-downloaded 3 minutes ago and uploaded the updated files. Still no joy with domainchecker.php. (It redirects to clientarea.php)

 

So, I uploaded the old domainchecker.php file from 5.1.3 and voila, everything works as expected. So something is definitely amiss in the patched file.

Link to comment
Share on other sites

There appears to be issues with creditcard.php as well When client makes a payment and passes 3D Secure, the page does not re load, no payment confirmation email is sent to client, or added to the gateway log, yet the invoice is marked as paid.

 

When making an attempt capture from the Admin side, this works with no problems, and the confirmation email is sent as well, it is only broken from the client side, which is rather important.

Edited by DF-Duncan
Link to comment
Share on other sites

Oh dear, this doesn't look good. Upgrades I can hold off on doing until a few months of proven stability, but when security patches are released, you feel its imperative to upload them. Now, even with them I'm not so sure. I can really do without a repeat of the grief from the last update again. WHMCS? What is going on. You never would have had these issues a couple of years back?

 

Should we roll back to 5.1.3?

Edited by Si
Link to comment
Share on other sites

This security patch is a mess.

 

Why would they release a security path that hasn't been properly tested on the same day as a full new release? It would have been much better to release just the patch today and focus on making sure it worked rather than releasing a new version along with it!

Link to comment
Share on other sites

It was just re-released and it should have received a version number increase again as now we don't really know if the one we have was new or not. We replaced it anyways...but it's getting very difficult to track security updates as you only recently started upgrading the version #'s when you patched something.

Link to comment
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.

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