Leaderboard

See the updated CORE-1371. With this event, plugins are able to inject arbitrary markup into the head, top of the body, and bottom of the body, as well as set variables into the structure that could be used in conjunction with changes to the structure file. There's really no difference. A hook is simply a poor man's event. By the way, there's already an event that is triggered on every page load: Appcontroller.preAction. CORE-1371 improves on that event.

Thanks PauloV. Really sorry but I never updated this thread to say that I got to the bottom of my error; after a significant number of hours I found a bug, which I worked with the blesta team to resolve a few releases ago.

Hi guys, I've noticed that when a client pays via PayPal there is no Blesta email confirmation sent, it's completely left to PayPal to send a receipt which feels a bit unprofessional from the client's perspective. Could this be implemented?

I highlighted Blesta's rounding issues some months ago and have since switched to using the exclusive tax method in the hope that these problems would diminish. Sadly, I continue to battle this problem daily, with rounding errors on invoice lines, invoice totals and when reconciling payments to invoices. Please refer to the attached image an an example, where you can see I am reconciling one payment against five invoices. I have entered the payment amount at the top (which is the amount the client had deposited) and checked the invoices to which this payment is being applied. If you add up the totals of each invoice, they do add up to the amount deposited -- but Blesta refuses to accept it. After some trial and error, I was able to record the payment by changing the payment amount at the top to be $3,809.99 The problem, as far as I can tell, is that Blesta is constantly performing the calculation of taxes rather than accepting the rounded two-decimal total for each invoice. Rounding should be performed once only (and I would suggest this happens at the line total). Once that rounded figure is calculated, all future calculations should work with the rounded figure. I really do like Blesta, but there are these niggling issues that deeply impact the software's integrity that need to be resolved. I hope that one day I can return to inclusive tax calculations which is how we should rightly be operating for GST in Australia.

Hopefully now my interworx create the reseller plans. But.. When i create the reseller plan for the user its create.. so its okay. But if he click to the login button he got this link: https://s1.mydomain.eu:2443/siteworx/index?action=login Actually why not login to this link? https://s1.mydomain.eu:2443/nodeworx/index?action=login Theese are reseller plans , so why want to login to siteworx , and not nodeworx?

Do you have an htaccess in the root web directory that might be conflicting? If you changed the /client/ directory to be a subdomain, you'd need to update the company hostname in Blesta to include the subdomain.

can you provide me to the email that I will PM you in a few seconds an access to your blesta instalation and ftp to trie to figure and fix the problem?

you can fetch them by $response = $api->post("logs", "getEmailList", $page = 1, array $order_by = array('date_sent'=>"DESC")); to fecth one email $response = $api->post("logs", "getEmail", $email_log_id ); more function for logs here http://source-docs.blesta.com/class-Logs.html i hope that can work for you

the module has been tested and working as we want : ) we will make some more test to ensure if there are a bug or not .

pretty sure he's asking how to access that list of emails/information via the API, as it seems he's already aware how to get to it in the admin panel.

as per this thread Request EVEnts , we want to see implementation of hooks system , something like : admin_header() admin_on_body_start() admin_on_body_load() admin_footer() client_header() client_on_body_start() client_on_body_load() client_footer() best regards

as the title see , is better to add the name attribute to the widgets . and why not a specific icon for it instead for the plugin logo . we have created a plugin with two widget and we have found like a double widget in the manage widget , we can't distingue beetwen them unless we activate them .

bug.

Now i found the problem. You have to choose Server Group: ANY.. not an already group. See the picture , then the things could work like a charm.

Hello, First i recomend you to read this: http://docs.blesta.com/display/dev/API After that you can create your API key on yor Blesta going to: Settings->System->API Access Now click on "ADD API USER" and creat a user to be able to access to your Blesta API. You can see some API commands exemples here: http://docs.blesta.com/display/dev/API#API-Examples To update user details, you can check the calling methods here: http://source-docs.blesta.com/package-blesta.app.models.html For clients edit here it is: http://source-docs.blesta.com/class-Clients.html Hope that helps

i have back again . the final solution will be as we have doit in v2.5 , a custom gateway for paypal and the others . the only probleme we have here , is we can't show any message to the client that the curency/amount to pay has been changed to a new amount/currency . but is better than we can't use paspay , stripe , payza ..... ) tomorrow i will share the paypal gateway with the community . EDIT : we can pass a message in the proccess.pdt file

Thanks mike . i have re-assigned the ACl and re-saved the group staff and the support departement and support staff . worked now . i think the admin (full admin) should by default have access to all without permission

Allow the From Name in email templates to either parse tags, or be overridden by department specific settings. Right now the email can be overridden, but not the From Name. This can lead to things like From Sales: <support@email.com>, and there's no way to change that right now. Would be nice if we could just put {ticket.department_name} as an example.

Should really be posted on their thread as it's not Blesta managed. It looks like Blesta's module doesn't close tickets.

That's a feature request for more tags, but I believe you can do what you like using the current tags {invoices.______} the guys will be able to tell you. If you would like to know now, you can use {% debug %} and email yourself that template and you will get all the tags you can use.

If we implement this, it will apply to all non-merchant gateways. Any issues with it working for 2CO, and other non-merchant gateways?