WebhostingNZ.com

Hi @od-ana
On the 'orders' widget on the 'Billing' -> 'overview' page, click the cog, set your email preferences.

So if you upgrade your ram from DDR3 to DDR4 it's the motherboards fault for not taking the ram?  They should make it fit and work?    Because we aren't talking about a minor build update here we are talking about a major version/release change.
If you don't want to pay to upgrade, just run PHP 5.6.  If you want to update your PHP,  you need to update your Blesta as well it's as simple as that.
Get a cheap VPS, put PHP5.6 on it, install blesta, or go to a webhost that provides mulit PHP.  cPanel, Cloudlinux and I'm sure other panel software also provides the user with the choice on PHP version.
 

Please let me know how they made changes that broke it?  The software was released for PHP version 5.6.  It still works on the PHP version it was produced for they didn't break anything.  Your choice of PHP install is what is causing the problem.
FYI: Blesta 3.6.1 was released one month before PHP7 was even released, and a long time before control panel software added support for PHP7.
https://www.blesta.com/tags/3.6.1/
https://en.wikipedia.org/wiki/PHP
Side note but I wish Wingcommander/Privateer still worked on my current PC (without an emulator), wonder if I should message them and tell them to update for me?

Right here, this is the answer....
You do NOT need to update - you do however, need to also NOT update your PHP version.  You can't update one without updating the other.  As I have already said just run PHP5.6 and you will have no problem.
 
I won't be replying to this thread anymore as I feel it will go nowhere everything that can be has been answered already.  Good luck.

Best answer: renew with OpenSRS, then transfer to NameCheap, you don't "lose" the 12 months of domain registration, it gets tacked onto your NameCheap registration.
 

Why don't you find out what it will take to update to latest & greatest? Blesta pricing is very reasonable.

Hi @bjacksparow,
Why not just run PHP 5.6?  If your host doesn't support it, find one that does.  The better option as @katycomputer has pointed out would be to upgrade your blesta license and install the 'latest & greatest' aka current version.

Thanks. This is fixed in CORE-2813 for v4.4.0.
In the interim, you can patch this yourself by updating /components/reports/tax_liability/tax_liability.php
Find the following line:
'invoices.subtotal', 'invoices.currency', 'invoices.date_closed', Replace it with:
'invoices.id', 'invoices.subtotal', 'invoices.currency', 'invoices.date_closed',  

Hi @od-ana
On the 'orders' widget on the 'Billing' -> 'overview' page, click the cog, set your email preferences.

@Mariano  I see no reason that wouldn't work.  It's actually a great idea and I don't think would be too hard to implement.

@Blesta Addons sub is well worth it.  He has many useful plugins/modules and if he wants to keep getting paid he will keep them updated, that's the bonus to the sub opposed to a one-off payment.
It really is great value for what you have access to.

@Blesta Addons sub is well worth it.  He has many useful plugins/modules and if he wants to keep getting paid he will keep them updated, that's the bonus to the sub opposed to a one-off payment.
It really is great value for what you have access to.

@Blesta Addons sub is well worth it.  He has many useful plugins/modules and if he wants to keep getting paid he will keep them updated, that's the bonus to the sub opposed to a one-off payment.
It really is great value for what you have access to.

I can confirm that this is a bug. We're looking into it for 4.3.2.

Version 4.3.1 is now available, please see the release announcement.
Patching Blesta

See Patching Blesta in the User Manual for instructions.

Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Migrating to Blesta

See Migrating to Blesta in the User Manual for instructions.
Release Notes

See Blesta Core - Version 4.3.1.

For older releases see all Change Logs.

For what it's worth, I think @Blesta Addons subscription model is a good one. It supports future development and you get access to many great extensions.  

Yes, there's plenty for us to do, but I wouldn't give whimps that much credit. They changed their entire business model to maximize profits with their license pricing, scheme, and particularly market connect. They are turning their customers into resellers of theirs. Maybe it's evil genius, or maybe cPanel finally needs a return on their money.
Either way, we have been adding a lot of things, particularly integrations. We have more work to do, but Blesta is used by more and more people every day. Not a day goes by that I don't personally help someone move away from our competitor. President Trump talks about trade deficits.. if we are looking at deficits, it's that far more people are migrating to Blesta than away from it.

This is the "better way" if editing structure.pdt
<?php if($system_company->id == "1") { ?> .. your code here .. <?php } ?> Just change the ID "1" to your company ID. Then you don't have to do the hostname validation yourself, it'll be done based on the company.

You could create a template for each company, then edit each template.  Or add some PHP similar to the following:
<?PHP $host = $_SERVER['HTTP_HOST']; if ($host == "YOURCOMPANYBLESTAURL"){ echo 'YOUR CODE'; } elseif  ($host == "YOURCOMPANYBLESTAURL"){ echo 'YOUR CODE'; } ?> I'm sure there is a better way than the above but it works for us with our live chat.

all the world are agreed in this subject. Domains are services and should remain as services. how it should displayed and how the order form should treated is another story.
 

Hi,
You could use it for selling software, Blesta use their own software to sell their software   I haven't tested it for anything else but anything you need to invoice for it could be used for.  A plumber, for example, could set up a client every time he does a job, create an invoice, print and hand them, or email it to them.

If you are upgrading you should NOT delete your blesta.php     You only rename blesta-new.php to blesta.php IF and only if you are doing a new install, if it's an upgrade you can just ignore the blesta-new.php or delete it if you don't like it hanging around.
Also as a suggestion, you should never delete a file if you are not 200% sure of what you are doing, best thing to do would be to rename it to something else so you can move/rename it back if it was not the right thing to do.
If you have your blesta.php from before your upgrade I would suggest restoring it, if not restore your whole account if you have a full backup.
 

Hi @Chris van der Westhuizen,
it would be {contact.id_code} for a paid invoice, please see the below
https://docs.blesta.com/pages/viewpage.action?pageId=4161645
You can see the other email templates at the link below:
https://docs.blesta.com/display/user/Email+Templates

@Blesta Addons I 100% agree with you it would be great if there was a setting to force either or.  I would personally use it and force email only.  I have a few times told customers their client area login is their email address only to find out after I've sent the email it's not.
@breeze  You could also ask for a developer to make the quick change for you for a small price, one of the massive benefits to Blesta is the ability to change things to suit your own needs without needing to wait forever for an update and a setting.  I know there is a list of people who make modules / plugins for blesta on request (and payment) I've seen Paul link it a few times, maybe someone who knows the link could post it below for breeze.  (I think Blesta Addons is one?)

Hi @breeze
I've only had a quick look into it but you could just edit the orderform signup.pdt so it's not an option, maybe make a hidden field to pass the pram back to blesta
 
<div class="radio"> <label> <?php $this->Form->fieldRadio('username_type', 'email', ($this->Html->ifSet($vars->username_type, 'email') == 'email'), ['id'=>'username_type_email']); $this->_('Signup.index.field_username_type_email'); ?> </label> </div> <div class="radio"> <label> <?php $this->Form->fieldRadio('username_type', 'username', ($this->Html->ifSet($vars->username_type) == 'username'), ['id'=>'username_type_username']); $this->_('Signup.index.field_username_type_username'); ?> </label> </div> Change that to a hidden field with a name and ID as 'username_type' and the value of 'email' i think would work, or you could just remove the username option both may or may not work and would require testing.