DigitalEnigma

Hi, Looking really smart, one bug I have noticed in IE11 is when in a fixed width view the footer is miss-aligned and does not sit centre at the bottom on the central content.

Hi, I opened a ticket for this, below is the fix I was provided:- Open your /admin/templates/*your active template*/viewticket.tpl file and make the following modification: FIND: &blocksender=true REPLACE WITH: &blocksender=true&token={$csrfToken}

Hi, We've also had this issue, I've rolled back the /includes/ccfunctions.php file so I could process batch payments this morning until a proper fix is supplied.

Hi, Have you called SagePay to have Tokens enabled on your account, you'll need to have these enabled to make use of the Token module.

Hi Chris, It looks like you've been overzealous with the encoding of files and have encoded the config file in the /cron directory (5.2.6).

Hi, I've seen this happen when using the cron job to sync the renewal dates on domains. In our case an invoice would have generated already and be pending payment. The cron to sync the dates will run and happens to pickup a domain that needed to be synced and that already had an invoice pending. This resulted in another invoice getting generated on the next invoice generation run.

Hi, With the token module it only stores the token, last 4 digits, expiry date. I believe it also stored the start date and issue number if you have those enabled. If you select to not store card details even though this module is not actually storing them then WHMCS will not store the token details. If you allow clients to remove their card details it will remove the token both in WHMCS and from the sagepay servers. @SteveTalbot I believe the errors you were getting is due to the legacy code in the token module to convert from the old none token gateway to a token - though I have advised Matt this will not work and have sent them an updated module with a number of fixes - not sure they will use the updated module in the next release or provide it to anyone else.

Hi, It does under the Common Problems section on that page:- Local Delivery Failed Error Message If you receive a bounce email containing an error that states local delivery failed like the error shown below when sending an email in to your piped email address then the forwarder entry is not correct and the message is not being sent to the pipe.php script. pipe to |/home/username/public_html/whmcs/pipe/pipe.php generated by support@yourdomain.com local delivery failed To correct this, first ensure the /pipe/pipe.php file is chmod to 755. From the error you are getting now it looks like the script is failing to connect to the database.

Hi, Have you CHMOD pipe.php to 755 as per the documentation so it can be executed?

Thanks for the confirmation.

Hi, I noticed yesterday the latest tweets have suddenly stopped showing up on the main page of both our live and development installs. This also appears to be the case with the WHMCS demo too. Have twitter changed something that causing these to no longer show?

Sign me up please.

If you're upgrading to 5.2.4 from 5.2.3 you don't need to run the installer, it was only a patch release.

Hi, By any chance do these clients have the extra contact with no company name set as the billing contact for their account, if they do this would explain why the company name is not showing on the invoice.

Hi Duncan, Which cart style are you using? I've just given this a try in our dev environment and was unable to re-produce this with the modern style cart.

Hi, If you are using a custom template have you updated the templates as there is a new template file which I believe relates to this in the 5.2.3 release:- logintwofa.tpl

Hi, The search function on the two templates for the downloads section is not functioning due to the test field having it's name set to "q", changing this to "search" fixes the search box for the download section when using the Default template.

Hi, If the client orders this as an addon at a later date it would charge them once with a standalone invoice, it then adds the fee to the domain recurring amount and the service then renews at the same time as the domain.

Hi Steve, I've been helping Matt test a fixed version of the module which works and resolves a few other issues with the older version of the module too. I confirmed with Matt the final issue we were seeing with tokens not removing on the test server was down to a bug on SagePay's part which they have fixed. I've not been able to test on the live servers yet as holding off getting tokens enabled on live till we ready to roll the 5.2 update to live.

Hi David, It may well be, hoping for a quick solution from SagePay to fix the token removal then the module should all be working.

Hi, I've been testing an updated module provided by Matt, this is working bar the removal of the token if a customer wishes to remove their card details, selects to not store them or we as admin remove them. I have a support case logged with SagePay for this as the correct details are being passed by the module but for some reason it is returning an error that the token was not created by our vendor name. Hopefully they'll have some answers on this so Matt can push the new module soon.

Hi, Mine was also doing this late last night but it working again at present.

Hi, This is broken with 5.2, it was reported during the beta. Matt is looking into fixing this module. I'm currently waiting on an update from him for this.

The logic isn't flawed, I'm saying this is what should be happening moving forward from the mess that was the 5.2.1 release.

I think lessons can be learnt from this release for both sides of the fence. From WHMCS side, more testing pre-release with a proper structured beta testing process. Several beta releases allowing for fixed bugs to be tested between releases and any new issued that have cropped up to be reported and fixed. Once all reported issued have been resolved push an RC release for testing, again repeat the cycle if needed fix any issues that are reported and push another RC for further testing. Assuming all is ok following that push for stable release. If bugs are still discovered after release (everyone’s environment differs) then issue a bug fix release and bump the version number rather than as has happened in the past and the version has been silently patched. From our side, don’t put a stable release into a live environment WHMCS will provide a development licence so you can test before putting live… use it! We've never jumped on a stable release on the day of release and let is loose on our live environment without having tested it in our development environment to make sure all is working as it should for a few weeks following the original release.