gerrybakker

It also worked well for WHMCS 7.0.1 You can see it at work on my site at hosting.express I added it to several pages including the home page.

I would be interested in a DirectAdmin version of this module.

I downgraded to 5.2.12 in self defense - I would rather risk a hack than have my business put out of business because of all the bugs in 5.2.13 that brought my business to a halt. To downgrade I logged into phpmyadmin and edited the version field in "tblconfig" to say 5.2.12 and did a complete upload of 5.2.12 - then I went to the admin screen which told me to delete the install folder - you have to do it in that sequence or it will fail - don't delete the install folder first. I did this for this downgrade because it didn't involve any database changes between 5.2.12 and 5.2.13. Doing a backup and restore is quite unpractical in the real world because a lot of transactions are coming in much quicker than WHMCS seems to realize - many of us don't run hobby sized businesses. Doing a backup before an upgrade and restoring that backup after 2 frustrating days of discovery about broken features is not practical - it ignores $1000's of dollars in missing transactions. Quality control has definitely dropped through the floor since cPanel got involved directly. This is still the best product out there and I thoroughly respect Matt for his efforts but the cPanel distraction has not been good for WHMCS customers/users.

I can confirm I am also getting this WHOIS token on a number of my WHMCS licenses as well.

If you have created a custom "Admin" template based on the V4 template then you need to copy over the new V4 "head.js" to your custom template folder. You also need to replace the old search box code in your "header.tpl" from a previous version with the new code that matches that head.js code. For me I replaced this in the "header.tpl" file in my custom admin template: <input type="text" id="intellisearchval" /> <img src="images/icons/delete.png" alt="Cancel" width="16" height="16" class="absmiddle" id="intellisearchcancel" /> </div> with: <form id="frmintellisearch"> <input type="hidden" name="intellisearch" value="1" /> <input type="hidden" name="token" value="{$csrfToken}" /> <input type="text" id="intellisearchval" name="value" /> </form> <img src="images/icons/delete.png" alt="Cancel" width="16" height="16" class="absmiddle" id="intellisearchcancel" /> Which I found in the new V4 template -

I had the same problem until I upgraded my server ioncube_loader from 4.0.2 to 4.2.2 to match my upgrade to PHP 5.3.x.

The solution to this problem was too easy - all I had to do was "save" the "Setup/Automation Settings" to make things work again. Apparently a number of flags changed in the WHMCS back end and nobody at WHMCS bothered to let us all know that we should be re-saving our settings to rewrite those variables so the new CRON.php would know what to do with them. It was "segfaulting" when the cron job ran before those settings were saved. Once settings were re-saved the cron job performed perfectly. WHMCS developers should have anticipated this and forced a re-save of those settings during the upgrade process to 5.2.X to prevent this horrifying result. I'm glad it was easy to resolve.

The solution to this problem was too easy - all I had to do was "save" the "Setup/Automation Settings" to make things work again. Apparently a number of flags changed in the WHMCS back end and nobody at WHMCS bothered to let us all know that we should be re-saving our settings to rewrite those variables so the new CRON.php would know what to do with them. It was "segfaulting" when the cron job ran before those settings were saved. Once settings were re-saved the cron job performed perfectly. WHMCS developers should have anticipated this and forced a re-save of those settings during the upgrade process to 5.2.X to prevent this horrifying result. I'm glad it was easy to resolve.

Still a problem - renewal invoices are not being created and payments for outstanding invoices are not being processed ever since I upgraded to 5.2.X - this is seriously a problem - I have upgraded to 5.2.4 with no positive results - I can see the cron job executes every day but no "WHMCS Cron Job Activity" emails are being generated since those upgrades. I wasn't paying attention to this for 3 weeks until I noticed my revenue dropped off by 60% - what a shock!!!

No due or overdue invoices are being processed with the daily cron since upgrading to 5.2.X - something really wrong. The cron job runs but the "WHMCS Cron Job Activity" doesn't get generated to show how many transactions were processed or failed.

what was the fix?

It is because you are using an email address that is not in your PayPal account or it doesn't exist - you have to satisfy both conditions before it works.

What version of WHMCS? I had that problem with 4.4 - version 5 fixed it.

pwgen 1.0 http://www.whmcs.com/members/communityaddons.php?action=viewmod&id=35 Works great - the download link is missing. I still have the zip file I downloaded last year. Where can we make it available to everyone again? Note: In WHMCS version 5.X edit the /admin/templates/blend/header.tpl file for the admin side password features - it works great - should be a standard feature in WHMCS.

Is there a new version of Name Spinner for WHMCS version 5.X I hope so - this sure was a useful feature in version 4.X