Leaderboard

I re-read it and understand but it's not how the order form works because if you have the correct order form as DOMAIN AND OTHER, and not having the domain group as the "package groups" then it won't show anything like that. You'll see the search and then the configuration page. then: Configure:

selling blesta theme with whmcs demo... moreover opening a dispute to get support reply...

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

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 .

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

+1

+1 to Portugal/Europe

let me vote for it

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

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.

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.