Paul

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.

If your post is gone, it's because I moved the marketplace discussion to http://www.blesta.com/forums/index.php?/topic/1046-the-markeplace-discussion-split/. Please take any discussion on the markeplace there and let's keep this thread focused on the knowledge base.

Thanks for the suggestion, CORE-763 has been added for forcing staff to use two-factor authentication.

CORE-494 for clients resetting cPanel password in the client area. Will take a look at client access to email log.

This is something that we would either simply implement, which would be similar to v2.5, or we would add a list of "on action" items that are configurable. I'm leaning toward the latter.

Does it show up in your phpinfo?

That's what I was worried about, glad you got it working!

We have no plans for Blesta to become a full fledged accounting system. Quickbooks can be used in conjunction with Blesta to handle the accounting, we use it internally ourselves. The shorter term question would be about getting some type of integration between the two. You should write an accounting plugin.

Does in include the ioncube loaders in it?

I just wanted to chime in on the module / marketplace discussion. I'll admit that I only read about 75% of the responses, as they were quite lengthy but I think I have a good understanding. If there's anything you want me to clarify, or think I overlooked, please let me know. 1. We want to support 3rd party developers as best as we can. We can't build everything for every niche. We are also aware that these developers have a financial incentive to build modules that we won't turn around and build ourselves. We can't guarantee this will never happen, but if there is any question, we encourage developers to ask us. We'll be as honest as possible about our future plans. Using ModulesGarden as an example, it's highly unlikely we'll develop an extended cPanel module anytime soon with the functionality they have built in because a) it already exists at a reasonable price, it fills the demand, and c) there are other areas of demand we can focus our efforts to move forward. Us building a cPanel extended module now would be a lateral move, and take away from much needed forward momentum. 2. We have partially built "The Marketplace", which is intended to be a marketplace of extensions for Blesta by 3rd party developers, and, at times, ourselves. When this is ready, 3rd party developers will be able to list their free and paid extensions in the marketplace. 3. There are 3 types of extensions we will develop. a) free and included in the core, free and available through the marketplace, and c) paid. We will never take our free modules, and start charging for them on an a-la-cart basis. If they start out included, they will stay that way. (Unless for example the company or panel we've integrated with disappears and we simply remove it altogether.) 4. An example of a paid extension that we will be releasing is the Licensing Module / Licensing Manager Plugin combo. This is the same system we use to license Blesta, and we will be releasing it as a paid extension. The reason this will be a paid extension is because it serves a smaller market segment. Not many people need it. There will be other paid extensions like this down the road that either serve a particular niche, segment, or enterprise, but we will not be moving to an everything a-la-cart system. We will also not be moving to a limited feature module, pay more for extended feature model to upsell people. I hope this helps clarify our position.

Ioncube may not be running via CLI. Can you SSH in and run.. php -i | grep IonCube .. and see if there is any output? If there isn't, maybe it's running off a different php.ini file. Alternatively you can run it with GET or wget. for example: GET -t 15m https://www.yourdomain.com/blesta/install/path/cron/?cron_key=CRONKEY where CRONKEY is your cron key as displayed under "Update Cron Key" (From http://docs.blesta.com/display/user/Installing+Blesta)