New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
@fileMEDIA yep, the same here.
A workaround can be adding this in configuration.php:
Of course this is temporary solution until WHMCS bothers to release a patch. I opened a ticket with them about this, still haven't got a reply.
A thanks, i got a reply. No upgrade without any problems..
Fail..
Have they released an update to fix the addon problem yet?
Chris
I asked for an update but didn't receive a response yet.
Has a fix been released for the addon bug?
>
>
>
Just received this from WHMCS.
Yep looks like it's released: http://blog.whmcs.com/?t=76514
I just finished upgrading and can confirm that creating an addon for an existing product/service now works.
Are you able to process upgrades/downgrades from the admin side without issue? Seems to be an issue published.
LOL? http://puu.sh/3N7br/c30a09bec6.png
Update: Nevermind, loads now..
Anyone using SolusVM WHMCS module having problems creating new clients since these updates? I get "cannot create client" error and it tries to make the username the same as the hostname which is really strange. Communication with Solus master is fine and all other module functions seem to work ok. Can also create new products for existing clients. It's only when creating new clients.
Do I understand correctly that you aplly these updates in your live systems? That sounds risky to me for an application that handles all your orders. It would make more sense to update a test installation, run a standard test that covers most of your daily proces and when succesfull update the live system.
I haven't been having issues with this
There must be something else going on if nobody else is having that problem. I tried creating a new sign up user and it worked. I think maybe it didn't like the password the customer chose. That would be a first so still not convinced that's it. It was definitely complicated enough. Are there any illegal symbols or combination that whmcs will reject in a password?
Since we buy from WHMCS direct we do have a DEV license to run a test instance. It does get updated on there 1st. Sometimes you can't test every scenario though.