Cody

Blesta doesn't make that easy, like it does for all other invoices. I think to prevent a staff member from accidentally sending a draft invoice to a client. Maybe it would make sense to add a setting to allow draft invoices to be emailed/faxed from the client profile just like all other invoices.

Here's a mockup.

HSTS has to be configured domain wide, so should only be done via server config, not application specific. I'm not sure many people install only Blesta on their domain.

I meant, what explicitly do you think we should consider? safe mode added in 5.4? What's else? Blesta already uses HTTPOnly. Secure cookies isn't feasible because not everyone forces SSL. That's why I'm asking, specifically, what options you think Blesta should support.

Stats on existing users don't necessarily correlate to potential customers, which is obviously the biggest concern when operating a business. To take an extreme look at it, we could make PHP 5.6 the minimum, and yes some people would be fine, others could upgrade, but we would receive almost 0 new business.

Regarding dropping support for PHP < 5.3. I have been for this since 3.0.0-a1 back in November 2012. The problem was at that time, more than 60% of all servers were still running 5.2 or lower. Today, sadly, there are still 25% of servers running PHP 5.2 or lower. Why have people been so slow to adopt PHP 5.3? Well, I suspect it has something to do with the fact that RHEL and CentOS are so incredibly slow to adopt new packages, coupled with the fact that most hosts don't keep servers up to date. In an ideal world, everyone would be running the latest version of PHP (5.6 today), but that's just not reality, and for us to shut off support for 5.2 and lower prematurely would hurt a lot of people. We always recommend installing Blesta using separation of concerns (1 server/VPS per role = minimum 3 servers/VPS [1 DB, 1 web, 1 mail]), but reality is there are tons of people that have Blesta installed in a shared environment. As Paul said, we'll be making 5.3 the minimum soon, as we now feel comfortable with the statistical usage of 5.3+.

What exactly are you referring to?

Thanks for the report. CORE-1437.

I guess if we're going to be creating plugins for other applications we should create one for drupal, modx, textpattern, refinery, concrete, expression engine, and every other CMS too? You know, to make Blesta usable?

Version 3.3.0 is now available. You can download it in the Client Area. If you have an owned branded or owned unbranded license purchased more than one year ago, be sure you have Support and Updates for your license before attempting to upgrade. To purchase support and updates: Log into the client area and click the "Manage" link next to your license, then click "Addons", and select Support and Updates from the drop down menu, and continue to purchase. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Migrating to Blesta See Migrating to Blesta in the User Manual for instructions. Overview Pro forma invoices Pro rata Price overrides Modules:Added Multicraft Plugins:Update Order plugin to include new order forms templates Tons more... PHP 5.5+ Users Included in this release is a /hotfix-php5.5/ directory. Please use this directory to overwrite the default /blesta/app/app_controller.php, /blesta/app/app_model.php, and /blesta/app/models/license.php files. Release Notes See Blesta Core - Version 3.3.0-b1. See Blesta Core - Version 3.3.0-b2. See Blesta Core - Version 3.3.0. For older releases see all Change Logs.

Wrong URL in emails is most likely due to the wrong path set in [settings] > [system] > [General] > Root Web Directory. This should be "The full server path to the web directory where Blesta is installed."

Where did you get 0.5.1? Latest looks like 0.5.0.

It's easy to spoof from addresses. You should never trust emails like this, regardless of who they look like they're from. We will never send patches via email.

It is the same, but you don't notice any issues because a regular invoice can not be converted like pro forma and draft are converted to real invoices.

The start value doesn't reset each year. Rather, if you're using the {year} tag in the numbering, a new set of numbers will be generated beginning at the start value given each year. The start value is just that, a start value. It's not intended to be incremented as that's the opposite of how it was designed.

Read only wouldn't work since users may want to change it to a larger value. I also don't think bugs in WHMCS are something we should implement in Blesta.

That would break as soon as someone changed the proforma start value to something less than the next value. For example, you open settings to make some changes, before you save your changes the inv_proforma_start gets increment because invoices were created, then you save your settings and overwrite the inv_proforma_start value with an older value.

Version 3.3.0-b2 is now available. You can download it in the Client Area. This is a BETA feature release. This release is not considered stable enough for production use. Please report any bugs in the 3.3 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 3.3.0-b2. For older releases see all Change Logs.

You could do it, if you wanted to so you could manage these values across your various plugins, but there is no requirement to define values that way.

You wouldn't be able to overwrite any variables with a function. With this event you can set other variables in structure, but again, only in structure and you can't overwrite variables that are set in structure after the event is called. You can set whatever variables you like, however. You are not limited to header, body_start, and body_end. Not sure what you're trying to do for seo analysis, but it's trivial to set javascript in body_end, for example google analytics.

Why would you need that? You can just call your function inside of your plugin.

Please note that the AppController.structure event has been updated to use arrays instead of strings for head, body_start, body_end in 3.3.0-b2. This is a backwards incompatible change (with 3.3.0-b1). Please be prepared to update your plugins if your plugins use the AppController.structure event. See CORE-1421 for more info.

This is trivial to implement with a plugin using the AppController.structure event.

Paulo, I think you misunderstand how it works. Consider the following example: Invoice created for Client A: PROFORMA-1 Invoice created for Client B: PROFORMA-2 Client A pays PROFORMA-1 becomes INVOICE-100 Invoice created for Client A: PROFORMA-3 PROFORMA-1 not reused! --- The only case where you will have the a pro forma invoice number reissued is if, and only if, Client A receives the latest invoice, pays that invoice, then generates a new (latest) invoice: Invoice created for Client A: PROFORMA-1 Client A pays PROFORMA-1 becomes INVOICE-100 Invoice created for Client A: PROFORMA-1 Client A pays PROFORMA-1 becomes INVOICE-101

Fixed in 3.3.0-b2. CORE-1406.