Leaderboard

Developers, note: Previously deprecated methods have been removed. Stop using these immediately: Controllers: AdminBilling::reports (/app/controllers/admin_billing.php) API/Models Companies::validateCompanyInUse (/app/models/companies.php) PackageOptions::getValueProratePrice (/app/models/package_options.php) Packages::getDaysToProrateBetween (/app/models/packages.php) Packages::getProrateAmount (/app/models/packages.php) Services::setOptions (/app/models/services.php) Components WidgetClient::renderSubHeader (/app/components/widget_client.php) Additional classes/methods have been deprecated. You should stop using these ASAP: API/Models Invoices::getItemTotals (/app/models/invoices.php) ServiceChanges::getItems (/app/models/service_changes.php) Services::getItemsFromData (/app/models/services.php) Components PricingPresenter (/app/components/pricing_presenter/*) Helpers Areyouahuman (/app/helpers/areyouahuman/*) Recaptcha (/app/components/recaptcha/*) More deprecations will likely follow.

Yes! v4 buttons. Looks nice and clean.

Blesta version 4.0.0-b5 (BETA 5) is now available. You can download it from right here (Client Area Login Required). If you haven't seen the blog post announcement for 4.0.0 BETA 1, you can read it here. This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4 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 4.0.0-b1-b5. SEE BETA 5 ONLY For older releases see all Change Logs. What to Test! 1. TEST EVERYTHING, IN PARTICULAR ANYTHING TO DO WITH PRICING AS WELL AS PHP 7 FUNCTIONALITY. SEE CHANGELOG FOR SPECIFIC ITEMS. Known issues 1. Upgrading/Downgrading a service as a client does not work because the "Review" button is missing.

You might get some responses (if no one PMd you already) if you include the layout you expect. Config options have a many-to-one relationship with a service/order, so you would either need to list the same order multiple times (once for each config option) or group them all into a single cell.

Few previews of what's to come for 1.2.0.