Cody

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.

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.

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.

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

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

You make some good points and offer some good suggestions. We'll keep an eye on this one.

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.

Fixed in 3.3.0-b2.

Fixed in 3.3.0-b2. CORE-1406.

Re-opened because it may be possible to parse package email snippets when saving a package which could (in theory) resolve this type of issue.

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

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

CORE-1362 fixed in 3.3.0-b2.

CORE-1362 fixed in 3.3.0-b2.

CORE-1362 fixed in 3.3.0-b2.

CORE-1362 fixed in 3.3.0-b2.

Hi and welcome.
 
Blesta is already 30% off, no coupon neccessary. I'm not sure how much longer this discount will last though, it's a ridiculously good deal.

Good points, electric. You've highlighted exactly why we've designed Blesta to be so modular and customizable.
Of course, I'm always surprised when people say Blesta is basic or simple, or otherwise lacking in features when compared to some other systems. It makes me smile, knowing we did a good job with not overwhelming the user. But it also means we may not be conveying all of the features of Blesta to users that are used to systems that have cut corners.
Take for example service terms. Most systems support one time, monthly, bimonthly, annually, and biannually. Blesta supports hundreds of thousands of possible terms!
Other systems supporting only email delivery of invoices. Blesta supports email, fax, and postal mail (yes, invoices that actually fit into double-windowed envelopes and can be printed through Blesta or mailed directly from Blesta)
Other systems have a basic API that was added as an after thought. Blesta's API automatically grows with every release, and with every plugin installed.
Multi-company,... the list goes on.
While I can definitely see how someone used to another system might notice some things currently unavailable, the net result is Blesta is more featureful overall; and growing daily.

We don't have any immediate plans for a quote system.

Closing as not a bug. If the issue persists create another report.

CORE-1402. Fixed for 3.3.0-b2.

base_uri is defined in AppController, so it's only available to controllers that extend AppController. Plugin classes are not controllers, so they don't have this variable set.
 
Use WEBDIR constant to give you the installation path, and Configure::get("Route.admin") or Configure::get("Route.client") to give you the rest of the URI.

Looks like you're blocking POST requests from PayPal's IPN, given that the POST data is empty: "a:0:{}"
 
This could be one of two things:
 
You have PHPIDS plugin enabled and it thinks PayPal's IPNs are attacks -- check your PHPIDS log, adjust settings as necessary, OR Your server is misconfigured and is not allowing POST data from PayPal's IPN service.

Didn't I post how to use this event in another thread?
<?php class MyPluginPlugin extends Plugin { ... public function getEvents() { return array( array( 'event' => "Appcontroller.structure", 'callback' => array("this", "run") ) // Add multiple events here ); } public function run($event) { // Fetch current return val $result = $event->getReturnVal(); $params = $event->getParams(); // Set return val if not set if (!isset($result['body_start'])) $result['body_start'] = null; // Update return val -- ONLY set if client portal if ($params['portal'] == "client") $result['body_start'] .= "<p>your HTML goes here</p>"; // Update return val $event->setReturnVal($result); } } ?> See Plugin Events. Creating Events.