Leaderboard

No alpha, you will have access to the beta though. As usual, beta's are open to all customers.

I just wanted to point this out in the road map for Vesta (http://vestacp.com/roadmap/) they have Blesta integration planned for the next version 0.9.8-8.

Hello Blestars Just for curiosity, did you recently post anything on www.webhostingtalk.com ? Was your post moderated? Do you see any push to a specific Hosting Panel on moderation, or topics lately? Regards, PV

Most people are running older versions of the Ioncube loaders, and PHP 5.5 supported builds of Blesta are not backwards compatible with these legacy loaders. Additionally, Blesta must be encoded for PHP 5.3 or 5.4 support in order to work with PHP 5.5, per this thread on Ioncube's forums, quoted below -- But, the minimum requirement for Blesta is PHP 5.1.3, so we have been releasing builds that are compatible for the majority (PHP 5.1.3 through 5.4.x), but not compatible with PHP 5.5. Adoption rates for PHP 5.5 are increasing, and we recognize the need to support it. At this time, due to Ioncube's limitations, we would be required to have 2 separate builds in order to support PHP 5.1.3-5.4.x and PHP 5.5. We are releasing this hotfix to allow PHP 5.5 support for Blesta 3.1.2. The zip contains only the 3 files we encode, to protect licensing. If you are not running Blesta 3.1.2 DO NOT apply the hotfix. blesta-3.1.2-php5.5-hotfix.zip If you are doing a fresh install, first download blesta-3.1.2.zip and overwrite the files in 3.1.2 from the hotfix above before attempting the installation. If you are planning to upgrade your existing server to PHP 5.5 and have Blesta 3.1.2 installed, overwrite the files in the hotfix above after you upgrade your PHP.

Dear support , it would be great if you are able to create a contact form on our blesta. A lot of users wants to send an email using contact form without open a ticket in order to ask something. Thanks

Cody is working on finishing up the conversion of the order form to bootstrap. Then he is going to implement the new ajax order template that I created, which looks great btw. Then beta will start. The new order form has comparison boxes or a slider for package selection. I think most people will use the new one.

Dennis is a great guy, had the pleasure of meeting him in person last year. Very down to earth, always a pleasure to read the WHT newsletters he sends out.

No you cannot. As the name suggests, it is a patch for v3.1.0 or v3.1.1 to v3.1.2. It does not contain new files from v3.0.x to v3.1.0. You should download the full v3.1.2 zip.

They think you're a shill? Our only association is that you're a customer, and we did not and never will ask you or anyone to post on WHT on our behalf. If our customers aren't allowed to post on WHT on their own accord, then we're being unfairly targeted. I don't know what you originally posted, but I suggest asking for the ticket to be escalated and reviewed by SoftwareReview. Sounds like you omitted some information that you should have included, but I don't believe it's shilling because you had nothing to gain, and you posted it on your own. A mistake? Probably. A clear shilling violation? I don't think so. EDIT: I feel like promoting the chat plugin you wrote now.

You can upgrade/downgrade services for a client from the Manage link for their service on their client profile page. As soon as proration is added, clients will be able to upgrade/downgrade from the client area. The upgrade/downgrade packages available are those packages that are in the same package group as the package they originally ordered.

I would tend to disagree with your statement. I would expect someone with common sense would think, "Ok, it looks like someone else here must have renewed it". Particularly when the renewal date may be up to 10 years in the future (for a .com domain, for example). But I guess the point is that it shouldn't be ambiguous -- it should be quite clear that the service terminates on the date indicated unless payment is received... at which point it renews. I don't see this as a feature request, I believe it is definitely a bug.

If you haven't, I'd suggest opening a ticket in their helpdesk to contest it. If the banning moderator responds, ask for it to be escalated to SoftwareReview. A permanent ban for that post seems ridiculous, especially since you have nothing to gain monetarily. (It's a free plugin!!) Maybe you should have mentioned that you wrote the plugin for full disclosure, but a perma ban for that seems absurd.. unless there were other reasons involved in their decision. Here's my suggestion to everyone who participates on WHT: 1. Follow their rules. 2. If you feel you've been unjustly targeted or given an infraction because of a post, open a ticket in their helpdesk and contest it. (I have opened a ticket every time I received an infraction, and have had one reversed) 3. If you see other people self promoting or not following the rules, report those posts. (I have reported posts made by our competitors for self-promotion, and their posts have been removed) The moderators at WHT believe they are enforcing the rules fairly. In most cases, they probably are, but because of our competitions long history and position in the market they are favored. WHT even promoted a thread for one of our competitors beta release announcements. They have never given us the courtesy. Things are changing, but it takes time. We're going to do all we can do, and continue to make Blesta better. Don't be intimidated, if you have something to say, say it! Just make sure you follow the rules.