Leaderboard

I would like a coupon tier please in the future, where we can make a coupon just for a month or a year. Or even valid for a month or a year. Maybe a tick box feature with the day, month, year, one time. Or even a auto generator so it pulls what values they are. So maybe one package has this: [ ] 2 day [ ] 4 month [ ] 12 month [ ] 1 year [ ] one time Because at the moment if a user say wants to buy hosting from you. They find a coupon for 60% off your package. But accidentally clicks on the yearly price. They enter the coupon and BAM they now get 60% off your yearly price. Even though it's not valid for it. Just a little inside of my feature request

I added this method to Packages, so you can look for a package based on meta fields. It even includes some hackery to look up values in serialized data. /** * Searches packages that contain the given meta field * * @param string $key They service field key to search * @param string $value The service field value to search * @param string $subkey The key to look for in serialised meta * @return array An array of stdClass objects, each containing a service */ public function searchPackageMeta($key, $value, $subkey=null) { $module_id=1; $this->Record = $this->getPackages(); $qry = $this->Record->innerJoin("package_meta", "package_meta.package_id", "=", "packages.id", false)-> group("packages.id")-> where("package_meta.key", "=", $key)-> where("package_meta.value", "=", $value); if($subkey) { return $qry->orLike("package_meta.value", sprintf('%%s:%d:"%s";s:%d:"%s";%%', strlen($subkey), $subkey, strlen($value), $value))->fetchAll(); } else { return $qry->orLike("package_meta.value", sprintf('%%:%%:%%;s:%d:"%s";%%', strlen($value), $value))->fetchAll(); } } Example usage: find packages that include .com NameCheap domains. blesta.api('packages/searchPackageMeta', {'key': 'tlds', 'value': '.com'}) Find all SSL certificates blesta.api('packages/searchPackageMeta', {'key': 'type', 'value': 'ssl'}) Get all 33" washing machines blesta.api('packages/searchPackageMeta', {'key': 'dimensions', 'value': '33', 'subkey': 'diameter'})

Hello there, I have an unbranded blesta license for sale .I've bought it during beta time to see where it goes . As of now i didn't find it productive . In the future i'm sure that blesta will be a top notch billing system . So i am selling only one of my licenses . We are having one if you are . It's verified on the same forums by Blesta Team . WHMCS branded swap is also accepted Asking price : 175$ OBO ( Now priced 210$) What else is included ? *. I'll take you through all the features of blesta live on teamviewer *. Hassle Free Installation *. I'll help you setup your blesta one-time ! You can reach me here or on my mail . I'll be happy to assist you

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.

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

What you're probably reading is refugees who are waiting on modules. The reason the guys are selling their licenses is that Blesta offered a promo price (which I think was a mistake) of $99 for v2.5 while v3 was in Beta which included a free upgrade when v3 was released. So now they're trying to flip them at a higher cost.

Error validation was only happening immediately before provisioning the service. We've updated the Universal module to do this validation when the form is initially submitted as well. CORE-765 fixed for 3.0.3.

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

If you only have one row, it will not be removed.

Until we've investigated and determined steps required to implement this feature, I won't be able to tell you what to change.

Yeah, Blesta license sales are popping up in several of the forums I read. It seems a lot of people don't want to wait for it to mature. If Blesta wasn't multi-company I might consider snatching up a few of these myself, but I have no real need.

As I've told Paul I'd do and just got round to it, here is the video.. please excuse the dashboard it's because I'm developing a theme for boostrap so broken on here. It also shows the error for the yearly issue. Register it from 2013 - 2014 and it shows 2014 - 2015. http://screencast.com/t/7x4Y8EIsbG60

Is there a customer viewable "road map" so we can see where items such as the Enom and the Quantum Vault Gateway are on the timeline.

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

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.

Contact logins with ACL permissions is actually on our list, CORE-627 and is tentatively schedule for 3.2. We will considered sponsored development for core features, however we will only do those if we already agree that we want to include it. Same really goes for extensions too. We try to prioritize development based on demand, and in all honesty someone willing to part with some cash says a lot about how serious they are about throwing their support behind something. It's possible to have 100 votes for a feature that nobody will really even use but sounds cool. We would rather build the feature that 10 people would actually use than the one 100 people voted for but wont use.

CCAvenue is assigned to CORE-736.