Paul

We will be doing an affiliate system plugin, however it's pretty low priority at the moment.

The license is valid, support and updates good through Aug 14, 2014

The license is valid and eligible to transfer. Support & updates good through Aug 14, 2014.

You can purchase addon companies during checkout for a new license, but cannot order them for an existing license yet. To get an addon company for an existing license just open a ticket and let us how many you need. We'll add them and invoice you. Pricing is $95/each or $350 for 5. It's one time, and can be applied to an owned license only (no monthly options yet). There is no additional yearly maintenance for addon companies.

CORE-639 % discounts for client groups tentatively scheduled for 3.1. It's not completed yet.

CORE-763 is tentatively scheduled for 3.2, yes.

The trial is super easy to get rolling with and nobody besides you can screw it up.

While we don't have any docs for importing from whmcs up yet, it may be helpful for you to review the import from Blesta 2.5 here http://docs.blesta.com/display/user/Migrating+to+Blesta You should install a fresh copy of v3. Then, take a backup of the database, so you can roll it back to a fresh install after doing a test import. You should do a test import and then verify everything works correctly. If there are any issues, let us know. We are still working on the importer and are happy to work with you through any issues. Also, we don't recommend turning on the cron in v3 until you're ready to go live. Until you turn the cron on, you can always go back. Nobody will be charged, nothing will be sent, etc unless performed manually. Also note that admin accounts in whmcs use MD5 passwords. You can enable support for these by editing config/blesta.php and enabling legacy password support. Once the staff member logs in, their password will be updated automatically to a bcrypted HMAC-SHA-256 password. We suggest disabling the legacy support after enough time has passed.

Understood. Just to clarify, Cody and I discussed the issue offline and I insisted that it was possibly a bug because of what you said in your original post: It was my understanding by your description of the issue that Restricted packages that were Addons may still appear on the order form. It was a reasonable assumption based on what you said. Since CORE-715 was suppose to resolve this and we confirmed that it was solved for standard packages (non-addons), I thought we may have overlooked restricted addons. What we learned was that you meant it's the Group that appears, not the Restricted Addon Packages. I think what you consider pervasiveness, is actually us not understanding at first what you meant. It wasn't worded correctly, and it was reasonable for us to think we may have missed a particular case. Back to this issue. I see 2 ways forward. 1. Add a setting in the admin area that will force empty package groups not to display on the order form. 2. Never display empty package groups on the order form. You see #2 as being the solution, and view it as a bug. We think some people may want empty package groups to display and are leaning toward #1. We are building for a wide audience. Differences in opinion are welcome, but we're not pervasive just because we disagree. And you make good points, worth considering. Whichever way we go forward on this issue, it will end up working like you want. The only reason we have to become less open minded and ignore or avoid requests and ideas is if things start to become hostile. We aren't interested in drama. Like I said before, if we can move forward on the basis that people understand and trust that we aren't being shady then discussion on all topics can be productive. If you had this assumption to begin with and tried to understand why we did what we did I think you would have been less critical. I think we all want most of the same things, but there will occasionally be contention.. that's to be expected. I just ask, please don't assume the worst of us because we're not in agreement on everything.

We appreciate your feedback, and think that it furthers the discussion. What you have to say is often very thoughtful and very useful. However, let's not operate on the assumption that we're trying to pull one over on anyone. That might be how other people operate, but we don't work that way. We're very honest about what we do, why we do it, and how we do it. The label feature was planned before this discussion. We don't try to hide bugs.. we'll be releasing a patch today that fixes about 30 of them. If we wanted to hide, we would encode the entire application. Let's move forward with the understanding that we operate ethically and aren't trying to hide anything from anyone, or save face by pretending bugs aren't bugs. We may not be right 100% of the time, but that's what this forum is all about.

Please note, this forum is not a marketplace for WHMCS licenses.

Are you using any particular control panel? Try piping to index.php instead, as described here - http://docs.blesta.com/display/user/Support+Manager#SupportManager-EmailPiping

We have a task to make the label "Default" configurable. Someone may have other options available offline, for quote and custom set up. In this case, they could use a label that says "Call for special options" or something. They want to indicate during checkout that there are options available, but they must be ordered separately, are special order, or custom/unique in some way. We always ask ourselves whether a change will exclude a use case. Sometimes we can come up with an example and then it becomes obvious. Sometimes we can't come up with an example, but believe that there may be a case to be made that we haven't considered, in which case, the decision becomes less obvious.

If a group contains no addons that can be ordered due to their status, the alternative may be to not display the group at all.

Yes it would. This file won't change often, but you'll want to merge the changes if there are any in a future release. If there are no changes, you can simply forget to upload it.

Reopened

config/session.php Change to the value you want. It's for the entire system, and applies to both clients and admins.

Could we create a .php file, that contains a configurable option for the company ID in the file? We'll default this to "1" for the primary company. If users want to pipe email into multiple companies, they could copy the file, change the company ID, and pipe their mail into the cloned file. We'll continue to support the other option by passing as parameters, but anyone that has trouble with that can use the alternative method.

There is probably a server issue, have you checked the error logs?

It also doesn't help that quite a few people purchased licenses with the intent to flip them because they knew the price was going up.

Hi Barry, Sorry about that, I'm not sure what happened. We do want to do something with Voip billing, and we have some customers that have implemented their own solutions. I'm not sure exactly what they did to make it all work though, and they haven't shared much of it with us. A feature request that goes into detail would be a good starting point for this. Cheers Paul

Perhaps mailparse is not loading via the web server? Didn't you have a similar issue with IonCube?

Yup!

This is a good question for Cody or Tyson, I'll ask them to take a look.

That's the most common reason IMAP/POP may be preferable, but there is a way around it. You can have email forwarded to another address at a different domain, whos MX points to the server running Blesta and pipe it in. I've not personally tested this, but I don't see any reason it wouldn't work.