activa

When client click in verification email link, the client redirected to checkout page 3 step.
I think is better to redirect to dashboard and show a message that email is verified.

when we use a nonmarchent gateway, the callback/return page redirect to received page, if a error is set by the gateways, blesta show the error message with a non well design panel box above.
also the panel box is not 100% width. we are testing in blesta 5.0.4
 

with the new domain manager , it would be better to unify the functions actions like getExpirationDate(), is the only unified function in domain registrar modules, something like getContacts(), updateContact(), getNameservers(), updateNameservers() .... ect
this way we can create more plugins/addons that interact with registrar modules with a unified function without care about the registrar module type. other competitors has this.
 
 

Hello all,
I have finally finished the module you can use to resell SSL Certificate through SSLTrust:
https://gitlab.com/ssltrust/besta/-/wikis/Installation
https://www.ssltrust.com.au/

Presently there's no way to access the suspension reason within the suspendService() method in modules.  Looking at the source in app/models/services.php this is because the updated suspension_reason isn't set until after suspendService() runs, thus the suspension_reason field in the $service object is incorrect (ie it's the old/previous reason, if any).
It would be great to be able to pass this value along to modules which may have their own methods of notifying customers, taking actions, etc.

Sure, upgrade to Blesta v4.7.0+ and ensure the Order plugin is using v2.20.0+. The domain module should then make the service's domain field available via ::getServiceName or the configuration value service.name_key.

Is there a reason it has to be a dropdown and not an input tagged as numeric and validated?  If there aren't technical limitations to arbitrary lengths why limit it?  Just default the number to something reasonable (30 days maybe).

Thought i'd add this on the news forum incase you're not aware the release of 4.7 Beta
 
https://www.blesta.com/2019/09/05/blesta-4.7-beta-released/

You shouldn't have any problem removing mcrypt and still have your data encrypted/decrypted the same as before so long as your Blesta system key remains the same.

Hello Sir
we are working on a hetzner dedicated server module (robots) not the cloud one.

We have Pushover, Hipchat and Discord integrated; if you need a mobile notification i think Pushover you will love it.
for Onesignal we will integrate it after the next release .

Blesta always needs to check you have a valid license. If you decide to sell it to someone else later, why should your copy of it continue working?
I don't play the lottery, but if I did, it wouldn't change anything. There may be more money to spend making it better though.

if @Paul wins lottery, i am sure blesta will become more robust, and may be even free...

Customers may pay with a payment method that takes the client away from Blesta, which posts back to Blesta when the payment is completed. Provisioning services through certain modules may take a significant amount of time to complete, such that making the user wait in the browser may result in a timeout. We are considering an enterprise level feature that adds a daemon to your server that runs continuously and processes certain jobs like order provisioning in near real-time.

The whole 5 minute cron thing is bizzare, why do orders submitted via the order form even need to wait for a cron job to fire...
Perhaps also look into implementing something similiar to hostbillapp.
https://hostbill.atlassian.net/wiki/spaces/DOCS/pages/491527/HostBill+Queue+Performance

The module really should make several attempts at generating a username if one is already taken before it fails in Blesta. I've created CORE-3225 to look into adding that behavior.

The issue is a bug with TCPDF. See here. They have not yet included a fix in TCPDF.
You could fix this in your installation by updating /vendors/tecnickcom/tcpdf/tcpdf.php:6849 by commenting out the "return false":
if (!@TCPDF_STATIC::file_exists($file)) { return false; } to
if (!@TCPDF_STATIC::file_exists($file)) { //return false; } Note: I did not investigate what, if any, issues may arise because of this work-around.
I would consider updating Blesta to include a downgraded version (v6.2.19) of TCPDF for the last known working copy except that a security vulnerability was fixed in the same patch release as this issue.

I was able to confirm https://dev.blesta.com/browse/CORE-3228

let me vote for it

+1 to Portugal/Europe
 

+1

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
 
 
 
 

it would be better to allow contacts  also to have custom fields like clients account.
now the custom fields is apply to clients account only .

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. 

For a dev, all actions have to be able to run pre eventes and after events, thas common sence
For me this is a priority one inclusion and its very easy for Paul/Tyson/etc to include in next release