Cody

You can also use the License Manager plugin in conjunction with the License Module.

I think this is related to CORE-1349. So should be fixed in 3.2.2, which should be out very soon.

I think we could probably add a client group column to any report that has a Client # column. Then you could do, as Mike said, and filter using excel.

A number of users have requested the ability to download invoice PDFs using the API. I've always said how easy it is to build a plugin to do this, so here it is.
 
Actually, I took it a few steps further and made it more abstract than that. This plugin allows you to invoke any component in Blesta using the API, so it's quite powerful. Invoices are offered for download and stream through the browser using the InvoiceDelivery component.
 
Documentation for this plugin can be found here..
component_api.zip

Yes, this is a known issue, CORE-861, that we're currently discussing in private on how to resolve.
 
I know this issue sounds simple on the surface, but is complicated by the fact that a coupon can be applied to multiple services at a time, some of which may be taxable and some that may not be. So the issue is with trying to resolve how best to calculate and represent the discount.
One such solution is to add multiple line items, one for each service that the coupon applies to. This, however, can't be done if the coupon is for a fixed amount discount.

A number of users have requested the ability to download invoice PDFs using the API. I've always said how easy it is to build a plugin to do this, so here it is.
 
Actually, I took it a few steps further and made it more abstract than that. This plugin allows you to invoke any component in Blesta using the API, so it's quite powerful. Invoices are offered for download and stream through the browser using the InvoiceDelivery component.
 
Documentation for this plugin can be found here..
component_api.zip

What currency is that? I've never heard of such a thing.

I like the consistency, but these might be a problem due to the simple fact that the buttons don't mention "PayPal" in any capacity.
 
Personally (and this is me speaking as an individual and not in any official capacity as a Blesta dev), I like the idea of not using graphical buttons at all. I think they should just be regular UI buttons that say either "Pay with PayPal" or "Pay with PayPal Subscription". And similarly for all other non-merchant gateways (i.e. "Pay with Stripe", "Pay with Skrill", etc.). That would be, by far, the most consistent implementation, and the most graphically pleasing.
 
On a side note, PayPal has some of the ugliest buttons ever imagined. They were ugly in 1998, and even more so today. This only fuels my desire to do away with graphical buttons altogether.

I think what this thread should be requesting is the ability to show currency equivalence.
For example, package is $100 USD, user uses GBP, so they could see on the order form:
$100 USD (approx. £78.73).

CORE-1323

Hmm... should only fail if there was an error upgrading one of your plugins. Maybe try CLI upgrade next time and see what it outputs.

Version 3.2.1 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.2.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.2.1.

See all Change Logs.

I think what this thread should be requesting is the ability to show currency equivalence.
For example, package is $100 USD, user uses GBP, so they could see on the order form:
$100 USD (approx. £78.73).

Version 3.2.1 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.2.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.2.1.

See all Change Logs.

Version 3.2.1 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.2.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.2.1.

See all Change Logs.

Version 3.2.1 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.2.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.2.1.

See all Change Logs.

I like the consistency, but these might be a problem due to the simple fact that the buttons don't mention "PayPal" in any capacity.
 
Personally (and this is me speaking as an individual and not in any official capacity as a Blesta dev), I like the idea of not using graphical buttons at all. I think they should just be regular UI buttons that say either "Pay with PayPal" or "Pay with PayPal Subscription". And similarly for all other non-merchant gateways (i.e. "Pay with Stripe", "Pay with Skrill", etc.). That would be, by far, the most consistent implementation, and the most graphically pleasing.
 
On a side note, PayPal has some of the ugliest buttons ever imagined. They were ugly in 1998, and even more so today. This only fuels my desire to do away with graphical buttons altogether.

Yeah, but I'm just trying to highlight that this doesn't really add any additional security to clarify for those that may be under the impression that Blesta will magically read their PGP key-ring or something. That said, using asymetric keys is preferable to passwords for requesting shell access so I guess CORE-1272 is a net positive.

You do realize this can't work using your PGP key-ring, right? You would have to give Blesta the full server path to the SSH private key that exists on your Blesta server. That means the private key can't be encrypted...
 
So... still want to +1 this?

He means you create two packages. One package with your publicly available terms, another that is restricted. Only staff can add restricted packages (thus restricted terms) as services for a client.

Such a feature would require a lot more verification than just a staff email from address, as that would be trivial to spoof, and my guess is you wouldn't want random viruses appearing in your client's documents section.
 
Something like this would require you to use signed email messages. This means you'd need to use PGP message signing for the email you send, which would then need to be verified by the web server when it's received to ensure the content of the message really did come from you, and that is hasn't been altered when in transit.

Why are we still talking about this? As I've already said, it's in the works. CORE-1085.
 
/thread.

Why are we still talking about this? As I've already said, it's in the works. CORE-1085.
 
/thread.