serge

the portal plugin was not enabled for this company.
 
SOLVED

the portal plugin was not enabled for this company.
 
SOLVED

thanks serge , but this is not what i want or this methode is impossible with my request . the invoice template system didn't accept the base_uri var , also note that the upload directory is out side the public html .
but anyway i have found tip that is working for me , i convert the image to the base_64 code and i use it in the img tag . so if anyone want the same thing this is the working solution

$type = pathinfo($this->meta['logo'] , PATHINFO_EXTENSION); $data = file_get_contents($this->meta['logo']); $base64 = 'data:image/' . $type . ';base64,' . base64_encode($data); $buffer = '<h1><img src="'. $base64 .'"></h1>';

This word should be changed to "Next Invoice" , you can do it via language file .

I think the problem is related to this: http://www.blesta.com/forums/index.php?/topic/2143-service-should-renew-when-paid-not-when-invoiced/?hl=invoice%20date
 
The "Confusing" name problem
 
This has to be changed

a
yes, i have see your remark , the payment detaill show the transaction_id but this ID is not the gateway transaction number , like you have write in your remark , it show "8" (transaction internal id instead of "5ND0132358817940D" gateway transaction number .

+1 for what Tyson said.

The proforma number is sequential, with no duplicates. The associated invoice, however, when paid, is no longer a proforma invoice. Voided invoices are still proforma, and still sequential. Once a proforma invoice number has been paid, it becomes a normal invoice, and the proforma number is 'released', whereby it can be used again elsewhere (sequentially, like your example). Are you saying there is a requirement that proforma invoice numbers cannot be used if they were used before, even when the proforma number is still unique? If so, could you reference the source for that requirement?

"Client ID" are unique number so in what it's differ with "client account ID", as it's ever what it is or mean by now.
 
What's your need behind the word "account", may you develop more?

oh my bad it's a feature request from 2014, I was thinking it's was from Today!

Thxs, I missed that also.

Looks Nice, I just noticed a little issue on the Order form. I switched to USD and all It didn't give out the conversion.

Your support tickets links are wrong:
http://dev-blesta.netpublica.com/plugin/support_manager/client_tickets/departments/plugin/support_manager/client_tickets/add/1/plugin/support_manager/client_tickets/add/1/plugin/support_manager/client_tickets/add/1/
instead of :
http://dev-blesta.netpublica.com/plugin/support_manager/client_tickets/add/1

That's pretty good. You did all that with the CMS plugin?
 
I see the Support Departments don't work yet, but I guess that's apart of the remaining 10%.

Looks nice mate.

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

This is a patch release that corrects issues with 3.4.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.4.1.

See all Change Logs.

@ModulesBakery , i have reported your tread as BUG .
 
i have found a solution . for those who want patch thier system , open app/controllers/client_services.php
 
 
change at line 943
// Get tabs $client_tabs = $module->getClientTabs($package); with
// Get tabs if (!empty($service->date_suspended))    $client_tabs = array() ; else     $client_tabs = $module->getClientTabs($package); EDIT :
and to prevent client from access to tabs with direct url 
 
change the line 123
$tab_view = $module->{$method}($package, $service, $this->get, $this->post, $this->files); to
if (empty($service->date_suspended))     $tab_view = $module->{$method}($package, $service, $this->get, $this->post, $this->files); i can sleep now

I have created CORE-1570 that suggests we disable client access to module management tabs for suspended services. While an argument exists that modules may wish to provide management features for suspended services, no such example exists. In all known cases, displaying the tabs can have negative consequences. The evidence is, at this time, overwhelmingly in favor of not displaying module tabs to clients for suspended services.
 
If at such time a case can be made for modules rendering management features for suspended services, then it would make sense to address that at that time.
 
Thanks for the feedback! 

good, thanks
 
In some countries having a lot of unbankable people, more than 80% of payment are not received same day of order,
customers have a order Ref number from the payment gateway and do over-the-counter cash payment.

I believe the company ID may be available, and a conditional could be created to display different content for different companies. I'll have to look into it, unless someone else knows?

here mate: https://licensecart.com/plugin/support_manager/knowledgebase/view/189/company-id/12/

I don't think that there will be any case where showing them would be useful (it might not be an issue to non-hosting businesses like me and LicenseCart) but for hosting providers i think it is critical, when the service status is not active, the only thing i would want a client to be able to access is the service information page, but other tabs should not be there in the first place.

CORE-912 addresses this. Most orders are paid and activated same day for most people, but this is an important distinction for services that either are awaiting payment for an extended period of time or for services (such as colo or dedicated servers) that may need to be manually provisioned over the course of days.

This has been assigned to CORE-1569, thanks for following up.

The Universal Module uses the package name as the service name before the service is created when one is not otherwise set from service fields set on the product. This would be why you see the "Package Name - Service Name" displaying the same value on order forms. In most areas of Blesta, a service name (label) is expected, and it is probably best for you to create one for the service so admins and clients know what the service is for.
 
That said, I'll remove the package name being used as the service name for services that have yet be created, as shown on the order form.