activa

Really like the new fields on configurable options. Wanted to propose a few improvements.
First, the setup fee is only applied once.   For example, if I sell 10 option "seats" I'm only capturing one setup fee for all the seats instead of one setup fee for each seat.   Perhaps, a "Setup fee applies to 'all' or 'per'" option?
Second, in some cases I would like to make selecting an option required.  Perhaps a "is required" checkbox next to the option?
Finally, I would like the flexibility to tax options, but not the parent service.   Perhaps adding a "inherits product's tax status" with a "yes|no" dropdown to each option?

From 2019, we will release a new version of our widget plugin, this plugin will be required for any other upcoming addons to be installed, this plugin has been improved and rewritten to support our upcoming features, like auto update or manual update with 1 click, manage subscription ... ect.
activating the widget in dashboard is not necessary, but installing the plugin is necessary for other addons to be installed/upgraded.
 
 
 

mcrypt is not available by default for php7.3 so you have to use PECL to install it. I followed the tutorial here (Even though it says php7.2)
https://lukasmestan.com/install-mcrypt-extension-in-php7-2/

The "OrderPlugin.client.name" definition is used in a couple locations:
In the client navigation When listing available order forms on the /order/forms/ URI For #2, the language is loaded from the language file, so it will appear as whatever definition you have set.
For #1, the language is translated to the default language and saved in the database under the `plugins_actions` table. This navigation language does not change, or reload, unless the Order plugin is installed/upgraded, and remains static from there on. We intend to update plugins to support multi-language definitions that are pulled from the plugin's language file instead of the database, but this is not currently integrated into Blesta.

surprised? many people / companies give up because there are no basic/standard modules to sell services. Our license was bought when it was Blesta 2.5, today we have Blesta 4? How many years should I wait? Many elements are still missing. Just browse the forum to find questions about the missing modules! The list is very long so Blesta is a waste of time for many companies. Although we still use Blesta, three of our other brands are based on wh...s. Many developers create cool solutions / modules, etc. but they are not 100% stable in combination with continuous updates of Blesta. Hosting is a type of business that requires stable operation of elements used to sell services. Unfortunately, Blesta has a problem with that.

Yes, we left Blesta over the Summer and we left for many reasons but this one is the biggest:
https://www.blesta.com/forums/index.php?/topic/7197-domain-manager-we-need-your-feedback-on-domains/&tab=comments#comment-45629
Honestly, Paul's lack of any response to this just tells me that nothing is being done and we can't run our business with the answer 'we hope to have something available by the end of 2018'. We're there now and there's still no sign of this.
I don't want to create a list that makes it look like we're bad mouthing the software or anything but there are many other features we need and we discovered others after making the switch. I believed in Blesta and wanted to stick with it but it ultimately comes down to useability for our clients and Blesta isn't quite there yet for our business. We'll keep an eye on the progress and if it gets where we need it to be, we'll move back.
There are a lot of things to appreciate with Blesta too and depending on your company and needs, it's a great piece of software. I am in no way saying WHMCS is superior or anything like that. It just has the hosting features that we need for our clients. I feel we gave Blesta a fair shot by sticking with it for over 3 years.

All of these systems are made to be customized. With that in mind, I would probably be interested in buying your license.

This is great, I would expect it :D

Hello All,
Today we want to announce that we are almost finished the development of our new module for Hetzner Cloud. the module will handel, create, suspend, unsuspend, cancel, rebuild(r- install), reset password and change hostname from admin and client area.
in our upcoming release, we will add support for volumes, floating ips .
now with this module we will cover the two big companies in Europe (with OVH server module already done).

We've been WHMCS users for well over 8 years and today we took the leap to Blesta. We will be integrating it with our new platform and slowly moving clients over in 2019. We have grown so tired of the price increases and code refactors over at WHMCS with no real added value for us.

Hi @rebus9,
Blesta does not perform cross-domain AJAX requests without specifying the dataType option, so I don't see how the vulnerability mentioned (i.e. https://snyk.io/vuln/npm:jquery:20150627) could be exploited as it is described. Blesta, actually, does not perform any cross-domain AJAX requests at all except for one in the admin interface in order to load the "Follow @blesta" button in the Feed Reader plugin. Unless you have installed some other third-party extensions with Blesta that do perform cross-domain AJAX requests, I don't think you have anything to worry about regarding that jQuery XSS vulnerability.

Thanks Tyson.  That extra detail was enough to get an exception from TrustWave.  The exception is not permanent, but hopefully the Blesta software will have an updated jquery version before the it comes up for review/re-evaluation.
 

The issue with service options not allowing you to add an option for the Universal Module was an issue resolved in v4.4.1. You should upgrade to that version of Blesta and try again.

Is a jquery components, shipped with blesta but maintained by third party. Blesta use jquery series 2, it should upgraded to series 3 .

Searching cPanel reseller ACL on Google shows this thread and a few others.
Judging by other threads it looks like there's a number of the Blesta devs along with other forums members that simply don't understand (or don't want to understand) exactly how WHM/cPanel assign reseller limits and the capability of the API. The ACL's aren't assigned per package, but per account and therefore they have to be assigned in one of the following fashions;
1) Assigned by calling setresellerlimits in the API on account creation (Blesta doesn't do this). 
2) Manually through WHM post account creation. 
This is a pretty fundamental part of the reseller account creation process, and without this Blesta currently doesn't server those that sell reseller packages very well using the core cPanel module. Comparing the module to WHMCS, ClientExec and free alternatives like BoxBilling I can see that these other systems have nailed this. Why is Blesta missing some really very important functionality? Nothing seems to be happening with it at all.

ticket #4885952 i submitted a new one other day before posting here, and have included links to these forums
im happy to test the new files for you
   

Is the member verification code only available for Google? Google's verification code can't be used in China. China is blocking Google's website. Is there any other verification code? No verification code was swiped by 6000 members for an hour.
 

wish template you are using? i have faced the same issue but in the order page wizard list, and resolved by putting the blesta-client jquery file in the header look at this thread
 

we will redesign our website and pages totally after we complete the credit note plugin and observium module .

when i update price then  . com tld disappear

today we get the same issue , about 40 invoices generated for the same service with the same dates !!
Installed Version 4.2.2

All I know is what they told me. Once they release something, I may do a video and blog post to show how it works.

+1 for security measures
how can you #BlestaDevelopers think every thing from the begening
great work @Paul & Team

Thanks! I confirmed this is the setting, and I started a new page in our documentation for this. https://docs.blesta.com/display/user/Config+Files#ConfigFiles-Blesta.default_password_reset_value

Ok I probably found when coupons become bugged - it probably happens when new month is starting.