Blesta Addons

the blesta has a limit for the service key field, it would better to made a check before sending the fields to the service controller to add add/edit service. i found this in my blesta logs PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'key' at row 1 in /home/***********/public_html/vendors/minphp/db/src/PdoConnection.php:196 Stack trace: #0 /home/***********/public_html/vendors/minphp/db/src/PdoConnection.php(196): PDOStatement->execute(Array) #1 /home/***********/public_html/vendors/minphp/record/src/Record.php(275): Minphp\Db\PdoConnection->query('INSERT INTO `se...', Array) #2 /home/***********/public_html/app/models/services.php(3654): Minphp\Record\Record->insert('service_fields', Array, Array) #3 /home/***********/public_html/app/models/services.php(3604): Services->addField('16241', Array) #4 /home/***********/public_html/app/models/services.php(1266): Services->setFields('16241', Array) #5 /home/***********/public_html/app/controllers/admin_clients.php(6053): Services->add(Array, Array, true) #6 /home/***********/public_html/app/controllers/admin_clients.php(5941): AdminClients->createService(Array, Array) #7 /home/***********/public_html/app/controllers/admin_clients.php(4688): AdminClients->processServiceStep('confirm', Object(stdClass), Object(stdClass), Object(stdClass)) #8 /home/***********/public_html/vendors/minphp/bridge/src/Lib/Dispatcher.php(142): AdminClients->addService() #9 /home/***********/public_html/index.php(21): Dispatcher::dispatch('/admin/clients/...') #10 {main} i don't have info about this action, but maybe one of the staff are wanting to add service with long key in the service field .

we can add a small text to indicate the limits under the input field. in side side i found that more pro and more simple to work, the slider in some browser and some mobile stuck and freeze . but if you want to add a option when we select the quantity text to select between slider and input well be nice also .

when we want to upgrade/downgrade service we get the fallowing error . Undefined index: client_prorate_credits on line 5107 in /home/xxxxxxxx/public_html/blesta/app/controllers/admin_clients.php NOTE : error reporting enabled

a quick view in the code in editservice() , if the client want to reinstall the vps with the same used template, the action is not token, if he reinstall with a template different from what is in use, the vps is well reinstalled . any one can confirm this ?

not sur, but if the staff suspend a service and they put in the reason fields 'Suspended for security reason', the client should receive the suspension email with the suspended cause, if the suspension was for non payment the reason should be no payment, maybe we should be more precis in the email template to avoid those ticket/emails/phones that ask why my account was suspended . this feature it should be addressed to client not to staff. also suspension for non payment is not the same as suspension for violation of TOS . Finally this is not a big deal, it was just enhancement to the email template to be more accurate about the suspension reason . also adding suspend by 'Staff id XXX' or by system it would be nice in the service view in admin side .

jQuery is our friend here . if you look at the snippet code sample in my post, it include a min/max value, maybe it need some tweak to be more conditional.

so you consider this isn't necessary . it was just request to enhance the user experience . maybe in the future it become necessary.

it would be more professional and simple if Blesta change how the quantity field is rendered now . a more simple quantity filed should be more elegant and all device compatible . something like this sample sample code https://bootsnipp.com/snippets/dGWP

re-uploaded the files again and is working now .

as Blesta now has option to set service suspension reason, it would be nice to update the email suspension service template to include the service.suspension_reason, a simple condition to check if the service.suspension_reason is set and then include it .

i have already requested this feature, the competitor do this from years now, they have pre-events and after-events (hooks) and they look to response to complete the action or return the returned errors. i think this behavior a great way to extend the software and give the developers the ability to do more features and staff . the events now in Blesta is just like a notification system about completed actions, and also i think is no sense for look for after-events return as the action is already completed.

the fix for blesta 4.6 beta is not working, no error returned by gateway . https://dev.blesta.com/browse/CORE-3122

What is the Obstacle Now in Domains? in reality the obstacles are now : - Multi Price System, This can be fixed with more price fields like Renewal Price, we add more fields , Transfer Price, Restore Price. - Better Domain Management, this also can be fixed by adding the functions to the actual modules . - Unification Commands, this also can be done by actualizing the actual modules. - Privacy, Forwarding & other addons prices, this can be implemented with the actual system by addons, we need just to tweak the actual modules to support this addons - if we want to distinct with domains modules and other modules we can add a new entry in modules to define is a domain module or not (true/false) or something like the order type definition. For me what Blesta need is enhancing the actual system and not reinventing a whole system for domains. now we have waited years to only hear a something from blesta, creating another system will take other 2 or 3 years, and the quick solution and the simple is to extend the actual exist mechanism to support new features .

we can't do anything, this need a modification in the core files, and we didn't encourage the core files modification or hacking . after the renewal price option, the next step i think is the unification of command in all domains modules, like getNameservers() , setNameservers(array $vars = null), getWhoisContact($type = 'all') , getEppCode(), setEppCode($epp) .... something like that .... or the second option that i can think about is to create a new module called for example domain manager, inside the module the option to add registrars and then extend the module command from the registrar class, the same login as modules with their functions, but finally Blesta who decide what is the best .

if you search you will find this subject the most wanted and talked. but it seem that the hosting/domain industry is not their priority list . yes, this feature is step forward in the domains logic model.

thank tyson, this only for the upcoming blesta 4.6 ? i will test it later, this will allow us to override it globally in blesta. so anywhere to call $this->base_uri will get the overridden value and not the default one ? so from the preAction event we can dot it without changing or modifying any blesta files ?

Hello Sir, it need a fully license reissue to work .

is not a space, is a strange char before null that is not visible and only can be detected by selection .

we have some seo practice in our website, nd we need this to do it in our multilanguage plugin that add instance for every language in blesta like /fr/ or /ar/ ...ect how we can override only WEBDIR by extending the container?

in this particular case we need to override . as we need to set a new value of WEBDIR .

i have found the issue is not the null, it was a char before null that caused the error Loader::loadHelpers($this, ['Date' => [ null, 'UTC', Configure::get('Blesta.company_timezone')]]); Loader::loadHelpers($this, ['Date' => [null, 'UTC', Configure::get('Blesta.company_timezone')]]);

Use of undefined constant null - assumed 'null' (this will throw an Error in a future version of PHP) on line 78

yes, after we set the timezone the dates not appear correctly . just a note the null return error, i have fixed by empty array Loader::loadHelpers($this, ['Date' => [[], 'UTC', Configure::get('Blesta.company_timezone')]]);

Yes , i have checked, it exist, but i have found that we didn't add it in a custom plugin that override some container functions.

we are using Date in a custom module . so we need here to set From and To to make them work . we have tough that the Date class do this when it loaded .