Blesta Addons

@font-face { font-family: "Glyphicons Halflings"; src: url("../fonts/bootstrap/glyphicons-halflings-regular.eot"); src: url("../fonts/bootstrap/glyphicons-halflings-regular.eot?#iefix") format("embedded-opentype"), url("../fonts/bootstrap/glyphicons-halflings-regular.woff2") format("woff2"), url("../fonts/bootstrap/glyphicons-halflings-regular.woff") format("woff"), url("../fonts/bootstrap/glyphicons-halflings-regular.ttf") format("truetype"), url("../fonts/bootstrap/glyphicons-halflings-regular.svg#glyphicons_halflingsregular") format("svg"); } the font location hsould be "../fonts/" instead of "../fonts/bootstrap/" .
 

What is the Obstacle Now in Domains? in reality the obstacles are now :
- Multi Price System, This can be fixed with more price fields like Renewal Price, we add more fields , Transfer Price, Restore Price.
- Better Domain Management, this also can be fixed by adding the functions to the actual modules .
- Unification Commands, this also can be done by actualizing the actual modules.
- Privacy, Forwarding & other addons prices, this can be implemented with the actual  system by addons, we need just to tweak the actual modules to support this addons
- if we want to distinct with domains modules and other modules we can add a new entry in modules to define is a domain module or not (true/false) or something like the order type definition.
For me what Blesta need is enhancing the actual system  and not reinventing a whole system for domains.  now we have waited years to only hear a something from blesta, creating another system will take other 2 or 3 years, and the quick solution and the simple is to extend the actual exist mechanism to support new features .

What is the Obstacle Now in Domains? in reality the obstacles are now :
- Multi Price System, This can be fixed with more price fields like Renewal Price, we add more fields , Transfer Price, Restore Price.
- Better Domain Management, this also can be fixed by adding the functions to the actual modules .
- Unification Commands, this also can be done by actualizing the actual modules.
- Privacy, Forwarding & other addons prices, this can be implemented with the actual  system by addons, we need just to tweak the actual modules to support this addons
- if we want to distinct with domains modules and other modules we can add a new entry in modules to define is a domain module or not (true/false) or something like the order type definition.
For me what Blesta need is enhancing the actual system  and not reinventing a whole system for domains.  now we have waited years to only hear a something from blesta, creating another system will take other 2 or 3 years, and the quick solution and the simple is to extend the actual exist mechanism to support new features .

What is the Obstacle Now in Domains? in reality the obstacles are now :
- Multi Price System, This can be fixed with more price fields like Renewal Price, we add more fields , Transfer Price, Restore Price.
- Better Domain Management, this also can be fixed by adding the functions to the actual modules .
- Unification Commands, this also can be done by actualizing the actual modules.
- Privacy, Forwarding & other addons prices, this can be implemented with the actual  system by addons, we need just to tweak the actual modules to support this addons
- if we want to distinct with domains modules and other modules we can add a new entry in modules to define is a domain module or not (true/false) or something like the order type definition.
For me what Blesta need is enhancing the actual system  and not reinventing a whole system for domains.  now we have waited years to only hear a something from blesta, creating another system will take other 2 or 3 years, and the quick solution and the simple is to extend the actual exist mechanism to support new features .

we can't do anything, this need a modification in the core files, and we didn't encourage  the core files modification or hacking .
after the renewal price option, the next step i think is the unification of command in all domains modules, like getNameservers() , setNameservers(array $vars = null), getWhoisContact($type = 'all') ,  getEppCode(), setEppCode($epp) .... something like that .... or the second option that i can think about is to create a new module called for example domain manager, inside the module the option to add registrars and then extend the module command from the registrar class, the same login as modules with their functions, but finally Blesta who decide what is the best .

Hello All ,
 
Today i want to suggest/talk about the navigation links , for my poor point of view , it need a full re-factor not just a improvement . why ?
 
1 - Normally the navigation links should be totally controlled by the admin/staff , as now some of the navigation are not stored in database and is added directly to the navigation.php , it's a -1 point for blesta .
2 - the admin/staff should be able to add/edit/delete links as it want .
3 - the navigation link should support access levels , like (all, guests, clients, staff, or based staff based permissions ) , for example i want to make navigation link only showed to the guests , like a registration link , or make a link showed only to clients like payment account .
4 - the link should also support orders , as i can move order (up/down) of them as  want .
5 - links should be multi-language of course . (i think that it was the main goal to make them n navigation php class by blesta ).
7 - the navigation links should support external urls .
8 - the navigation link should be out of the show_header var .
 
at the moment , getPrimaryClient is the most wanted .
 
if blesta accept the deal , they jst add the structure database tables and the class . i can provide a free plug-in to the community to ad/edit/delete/order the links
 
 
 
 
 
 
 
 

i have found the issue is not the null, it was a char before null that caused the error
        Loader::loadHelpers($this, ['Date' => [ null, 'UTC', Configure::get('Blesta.company_timezone')]]);
        Loader::loadHelpers($this, ['Date' => [null, 'UTC', Configure::get('Blesta.company_timezone')]]);

In your screenshot for the package option "Script", I notice that the "Name" is capitalized as "Script" rather than "script" as mentioned in the documentation. I believe that is case-sensitive, so it may be why WP does not get installed. I would update that and retest first.
The package has 1 and 3 month terms, but the package options are only setup for 1 month, so it would only be installed if the 1 month package was ordered, not the 3 month package.

Hi, thank you for your help.
I was testing the Pay Now (No login required) link... it actually take me to "Make Payment", but after selecting the payment gateway and clicking "Review and Confirm", I'm redirected to login page. This is normal behaviour?
My gateway is Paypal Payments Standard
 
Edit: Tried this solution posted by Tyson and it worked 
 

you can open a ticket with blesta, give him more info about your reseller and license key, i'm sure they can move the license to your account or give you another license key with the matched expiration date .
 

we also waiting this feature, it will solve one of our issues.

it would be nice to add orders to searchable items . like tickets ect ...

Created as CORE-3111.

Hello, this is not the first time i talk/claim about this, but this is causing us a lot of problems and claims and money lose . we talked in
and here
 
but until now no fix is provided .
a sample case from us
Service Created in 10-4-2018 14:00 .
Renew date are 10-4-2019 14:00
Invoice Due Date 10-4-2019 00:00
Suspend Services Days After Due  1 Day
this service will be suspended in 12-4-2019 when cronjob run .
as you see we have here 2 days of latency in suspension system, we need the service to be suspended the same day if invoice is not paid (in our example should be 10-4-2019 14:01) , i wouldn't talk about times in blesta as we have talked a lot and we have arrived to no solution, my ask if blesta staff can make a new setting or anything to achieve this simple request?
we need the service to be suspended after their expiration date immediately, in some services letting services for two days active (and this is the minimum in blesta) before suspending them will consume a lot of resources and licenses fees.
 
 
 
 

Stripe Will change their payment System for New Europe law sales, i think this will infect the API also,
https://stripe.com/en-US/guides/strong-customer-authentication
 
https://stripe.com/en-US/payments/strong-customer-authentication

not applying to invoice , i'm talking about printed invoice to client. the clients need to see if there are a credit left or solde left  after the payment applied to invoice.
the remaining amount to pay is shown in the invoice as balance (positive), and normally he should be negative because we own money to client . if client owe money to us then the balance should be shown with positive value . this is what we do in our accounting system in our country, not sure if this is the same as USA .
 

we are almost finished the integration of coreui template with admin dashboard .

 the original free theme are available here https://coreui.io/demo/
what do you think ?

after some look at blesta code, i find that the GatewayPayments->getBuildProcess() is not setting the errors, it only return the html returned data, in this case is a empty value . we have made a simple fix, in two files .
components/gateway_payments/gateway_payments.php  line 162
change from
return $html; to
if (($errors = $gateway_obj->errors())) { // If no response given and errors set, pass those errors along $this->Input->setErrors($errors); return; } return $html;  
file controllers/client_pay.php line 868
change from
$this->set( 'gateway_buttons', $this->Payments->getBuildProcess( $contact_info, $total, $payment['currency'], $apply_amounts, $options, $payment['method']['pay_with'] ) ); to
$gateway_buttons = $this->Payments->getBuildProcess( $contact_info, $total, $payment['currency'], $apply_amounts, $options, $payment['method']['pay_with'] ); if ($errors = $this->Payments->errors()) { $this->setMessage('error', $errors); } $this->set('gateway_buttons', $gateway_buttons);  
with this way, any error returned the the buildproccess will shown to the client . like invalid zip code,  empty state ...ect

we have a gateway that set a error if returned from the gateway and set it to the returned data, but blesta is not showing the returned error .
i have made a simple test and made the buildprocess return a error, but blesta client side is not showing it when the client want to pay with that gateway.
$this->Input->setErrors($this->getCommonError('invalid')); return; is blesta not showing the returned errors in process view, or we have missed something ?

Thanks, I think that would be a useful addition. We'll look into it for CORE-3066.

Great Work .

After a long and great time building the CMS we wanted to change our way we do business to help others get the best out of Blesta and we can grow a bigger community with Blesta.
The BlestaCMS is now open-code and the "base" is free to everyone. That's currently 1.2.7. We will fix bugs and patch the version when needed for free but to upgrade to a new version let's say 1.3.0, you will need a license. We're still working on this to make sure the updates are safe and secure. You'll also need a license if you wish to get support from us with active support and updates.
If you do need support you can go to our support ticket page, click on BlestaCMS Support and then enter your license key. This will allow you to submit a ticket.
You can download the latest version of the BlestaCMS Base here: https://blesta.store/client/plugin/download_manager/client_main/download/26/CMS-1.2.7.zip
Support:

Valid:

Suspended:

PS: We've fixed the spelling on complimentary, sorry for the error on the screenshot.
Cancelled:

 
---
BlestaCMS previews: https://blesta.store/cms
Share / View the code / Modify / fork freedom on Github: https://github.com/atlanical/BlestaCMS-Community-Edition

Nice!
Looks like you may have another typo in the success message.  It says 'you can how submit a support ticket'.

Thanks mate wouldn't be possible without your help making the tickets  and I'll fix that haha how is now in the future haha. Fixed.

Screenshot