Leaderboard

Version 3.5.0-b4 is now available. You can download it in the Client Area. This is a BETA feature release. This release is not considered stable enough for production use. Please report any bugs in the 3.5 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 3.5.0-b4. For older releases see all Change Logs.

SOAP is not working properly on the server Blesta is installed on for some reason. To see a more descriptive error, update /components/modules/interworx/apis/interworx_api.php and find: throw new Exception("soap_error2"); and change it to: throw new Exception("soap_error2 " . $e->getMessage() . "\n" . $e->getTraceAsString()); Then try it again. When it fails, look at the log output as you did in the first post.

looks like PDO is having trouble connecting (are you using localhost instead of 127.0.0.1 in server network configs?). (or did you not install PDO yet?) Also, before you do anything...did you restart apache after installing PDO? Sometimes just restarting apache can fix PDO errors (at least in my experience)

I'm not a fan of the client ID position: I think it would be better like this: Or what I use now which is like the admin area (I think 2.5 did this too not sure have to get my demo site back up to see). <h3 class="panel-title">Client #<?php echo $this->Html->_($client->id_code, true);?><!--<?php $this->_("ClientMain.myinfo.boxtitle_client");?>--></h3>

i prefer the third markup that mke has posted . still in love of v2.5

I agree that the positioning of the client id could be improved. I think adding hr's around it will make it take up more space than is necessary though. Having it in the panel heading seems a little better, but I prefer to keep that saying "My Information". Adding it after "My Information" may take up too much space, we don't want that to wrap. I'm torn, not sure the best placement. Anyone have any other suggestions?

If you are using PHP 5.6 on the Blesta box, install a proper SSL certificate on https://server3.yatosha.com:2443/

Have you enabled the graceful restart on my tutorial?

No update. This is still on our todo list.

Hi PauloV, We are testing this and saw a problem while changing the dns for a domain. If the domain is locked then OpenSRS will deny any DNS changes. You require to unlock the domain to change the dns settings. But, if you update the dns through the Blesta module it does not return an error while updating the dns if the domain is locked, in the client and admin areas. You need to go to the logs, to see this error : :"Registry error, domain's nameservers not updated [Object status prohibits operation Reason:clientUpdateProhibited]" I suggest to add a message saying something like "This domain must be unlocked to perform dns operations" on the tabClientNameservers if the domain is locked + to return the API error to the customer and the admin. Thank you, Carl

To clarify, the spinning icon denotes the task is currently running. If it runs for too long than seems practical it may be stalled due to error or timeout. In that case, the task doesn't formally end, and is forced to end after the 6 hour wait period. If you continue to encounter this, you will need to try to debug the issue with the cron task or what it is running to determine why it is unable to complete successfully.

Zero quantity config options are removed in CORE-1676. However, removing $0 line items would remove all free items you have as well.

also create a php info file at root of your Blesta install and load it in your Internet Browser, to check if that load fine: http://www.inmotionhosting.com/support/website/php/create-phpinfo-page-to-see-php-settings

restart your mysql service, I even suspect it was stopped

That would be pointless and probably best to put the description on it ResellerClub, NetEarthOne & ResellBiz. PS: the way I found out is by logging into an account it goes via a logicboxes.com/foundataion something before being re-directed back to the company website.

There were no configurable options. The spinning icon was the issue. I searched the forums and seen that I needed to wait six hours. I did that and all is working ok now. Thanks for you help

There is alredy a resell.biz module for blesta The "Logicbox" module works with resell.biz or any outher logicbox registrar ( @Paul/Tyson/Cody Maybe it wold be a god idea duplicate the module Logicboxes and rename it on every registrar existent that uses the same platform I know that the best way is to not rename but more than 90% of hosting companies dont know that Logicboxes is used on several registrrars (yes i also know that you have on your website here http://docs.blesta.com/display/user/Logicboxes)

This is my last reply in this thread , we are here not to fight or to demonstrate that our ideas are more important than other ideas, but we are here to give the blesta staff a road how to win more and POTENTIAL clients , and what is the locking features and the best improuvement just blesta need to add SPECIALLY for the HOSTING market . blesta accept it or reject it , that is thier decession and not our choice . blesta is the only billing software that has a poor solutions for HOSTING market (at this moment) , regaring other competitor like WHM** , Client****, Boxb*** , AWS* ..... we have found this by experience and testing others solutions . excluding this point, and some minor feature , blesta is the solid, secure and the best ... the most users using blesta , thier are a big probability to have new plugins/modules/gateways.... either free or paid , that way the blesat can have a large base of addons for defferent use .

Hey guys, Thought others might find this useful. I needed to have old configurable option values available in my POST requests from the universal module so after a bit of digging a pretty simple edit to app/models/services.php takes care of this nicely. Unfortunately it's a core edit, though hopefully this can make it into core officially *hint hint* // KNOWNHOST MOD RETURN OLD CONFIG OPTS foreach($service->options as $config_option){ if(isset($config_option->option_type) && $config_option->option_type == 'quantity'){ $vars['oldconfigoptions'][$config_option->option_name] = $config_option->qty; }else{ $vars['oldconfigoptions'][$config_option->option_name] = $config_option->option_value; } } // END KH MOD RETURN OLD CONFIG OPTS Insert this code around line ~1064 (right above $service_info = null;) of app/models/services.php I've only tested this a few times with different scenarios but it works perfectly in my environment. Enjoy

I am just worried that I might be incorrect and offend a real customer. I guess better safe then sorry.