Paul

It's not slated for 3.4 Mike, but the Affiliate system is in the process of being fully spec'd out. 3.4 will have a Knowledge Base, Contact logins with ACL permissions, and 2FA for clients and contacts. There will be more, but an Affiliate system is a big task and is unlikely to make it.

There is no direct association between a download from the download manager, and the universal module. The association is that a Package is assigned to the download. Having a service that uses that package gives the client access to the download. The module is irrelevant.

When you add your download under Settings > Plugins > Download Manager, select "Must be logged in", and check "Available to Packages". Then, using the multi-select, move only the packages you want to have access to this download from the right to the left.

Looks really nice!

What about clients that have no services, that you say, invoice manually periodically, or have a recurring invoice set up for? You would still consider these active clients.

If you invoice them for the credit, and then invoice them again when the credit is used you are invoicing the client for $6000 but they are only paying you $3000. Your accountant (or worse, the IRS) might wonder about the discrepancy between billables and revenue. It is better if they just make payment for the credit, and the credit remains on their account until you invoice it. You can subscribe to BCC notices on virtual any client email. Edit your staff group under Settings > System > Staff > Groups, and check under "Email BCC Notices". Whichever ones are enabled here you can then subscribe to under "My Info".

True, but changing SSH ports to something other than 22 cuts down on brute force attacks. Same could be true of changing the admin URL. You should always assume people know what it is, but it's not a bad idea to change it.

Your right. An inactive accounts cannot log in. Only staff can mark an account inactive, or active, or fraud, and a client cannot order new services under an account that is not active unless it is first made active. To be clear, are you asking for the ability for inactive accounts to be made active again by clients who order new services?

We are planning to support drop-in HTML invoice designs that get converted to PDF. These are simpler to make than the 2 PDF invoices we ship with Blesta as those are not simple HTML. Is that what you mean, or do you want to completely replace TCPDF with another engine?

Blesta doesn't allow you to create credits out of thin air. Record Payment > In House Credit is a good way to issue a credit though.

Comments seem like a good idea, do you mean staff and clients can both comment? So, a quote has a threaded reply/conversation with the client? If a quote is accepted, and an invoice results and pro forma is enabled, what is the appropriate action? If a quote is accepted, is that considered a contract and an invoice should be generated, or should a pro forma be generated? In past discussions, there was concert by some that a pro forma invoice doesn't need to be paid. Would it be appropriate to issue a pro forma invoice for an accepted quote?

CORE-1277 exists for Credit Notes. I don't have an ETA on this one yet, but it is planned. CORE-1148 will display payments / credits on invoices, if enabled, and if a payment has been applied toward the invoice whether partial or in full. Tyson was working on this so it is likely to be in 3.4. Also -- while only dates are shown on invoices, Blesta stores all dates/times in the database. So, it would be possible to display times on the invoice with some code modifications.

No need to re-install, just contact the reseller and ask them to "re-issue" the license. It's a box they check in our system that allows the license to be installed/activated in a new location. PM me your license key if you want me to look it up, I *might* be able to do it for you.

You are welcome to make a feature request - http://www.blesta.com/forums/index.php?/forum/11-feature-requests/

Ah, glad I was able to help! Good luck with your live import! We spent a ton of time on the importer and there's more we can do. We want it to be as smooth as possible, but it's really tough trying to convert lemon juice into orange juice. (or is it apples and oranges?)

Blesta doesn't prevent you from doing anything. You can edit the database directly, or write a plugin that adds that functionality, or edit the core, it's open. There's an infinite number of things Blesta *could* do that it doesn't, some good, some bad, some indifferent. We have to be careful about what we implement. This is one of those issues that we feel pretty strongly about, but if demand were high enough we would consider a change in course -- there just isn't the demand.

It's our job to make an effort to do things right. If you are running a lot of tests, they should probably be done in a dev environment, not your live environment. If this is part of your set up process, it doesn't need to be a feature.

Sounds like a good idea for a plugin *If* you could delete transactions, you probably wouldn't want all your staff to be able to do the same. Making money disappear in one area, sometimes mean it is re-appearing in someone's pocket, off the books. That's money laundering. If you can tell your auditor that Blesta doesn't allow you to delete transactions, then it makes you look a whole lot better and raises fewer questions. I'd rather explain why there's a voided test transaction than be under the heat lamp. In the grand scheme of things, it doesn't take up much space in your database, and space is cheap.

Any luck?

You could use the private notes field for internal tracking of things.

Anyone else having trouble with this also? I would suggest reaching out to Softaculous if you're having trouble, the more people they hear from the more likely they are to fix it quickly.

Do you have a config/blesta.php config file? You shouldn't until you've made it most of the way through installation. You should have a config/blesta-new.php config file, which is renamed, so this file, and the config directory should have write permissions during installation. The error seems to indicate that the config file was renamed, but the {database_host} tag wasn't replaced with the actual database host entered during installation (usually "localhost").

Any suggestions in terms of features to round this off?

I wonder if it makes sense to implement a simple quote system to start with. It would be similar to draft except: Clients can receive the quote via email, paper, etc just like invoices The quote email would contain a link to Blesta where they can accept to the quote Accepting the quote will turn around an invoice. Depending on the work involved, some other terms could be accepted. For example, half to start, final half due upon completion. etc. Really it needs to be fleshed out more, but I think if we stick to the basics in an initial release, it will work for most people and not take a ton of dev time to implement.

Never experience that issue, or remember anyone else mentioning it. The font is actually included with the PDF (Hence the 700KB-ish size). Have you made any changes, or are you using a non-default font?