PauloV

Yeah, I wouldn't put the word bounty in it, many people assume there is a monetary award.
 
In theory the plugin sounds like a good idea, but don't forget that they first have to install it. Most people won't go through the effort.

I'm lazy, I only post here if I know it will help others, but I don't technically look for bugs.

I personally think this would be pointless, just because I don't see why you need it, if it was for Plugin / modules / gateway developers to submit a easy list of their bug change report, that might be interesting. 

We already have a policy for security related issues. See http://docs.blesta.com/display/support/Responsible+Disclosure+Policy
 
Emailing our security department automatically opens a ticket, and we review all reports right away. We do not currently have a bounty program though. We give credit but not monetary rewards for reporting security issues. We may offer bounties in the future but we have found that most people do not download and install Blesta and test it themselves.. they run automated penetration tests on our live systems and cause headaches for our infrastructure.

The post that I have posted on WebHostingTalk is on the #3 replay above as an image
 
http://www.blesta.com/forums/uploads/monthly_03_2014/post-9426-0-86538000-1395426767.png
 
Also you can see it on Google WebCache here: http://webcache.googleusercontent.com/search?q=cache:OYdfw2vqagIJ:www.webhostingtalk.com/showthread.php%3Ft%3D1347143%26perpage%3D2+&cd=1&hl=pt-PT&ct=clnk&gl=pt
 
I will try to escalate the ticket to Dennis Johnson , but after what I have posted here, and Im sure the Bear as read it, I dont think I will never be able to have my member qlpqlp back
 
A response to this forum from Bear would be great, to him defend imself and also to close this, because no one will win anything and only Bear can step foward.
 
 
 
Fell free to do what you (all Blesta staff and owners) whant with Blesta Live Chat you have our permission
 
Regards,
PV

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.

CORE-1074 fixed for 3.1.3.

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.

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
 
 

New Update released, please see first post.
 
Regards,
PV

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.

Confirmed, all Blesta posts on WebHostingatalk are being moderated and some removed.
An employee of us as registered at webhostingtalk and he as responded at this post http://www.webhostingtalk.com/showthread.php?t=1358015 telling only that Blesta has a License Plugin and the post was removed and the member account banned.
Well done WebHostingtalk!

Fair enough, each to their own I guess, I just personally find them to be quite an ugly way to create a sense of integration. But as you said, some big players will still use them to make it easy for those with less technical ability.

I'm not sure if this is in the pipeline, but it'd be great not to have to jump in to FTP every time there's an update. Many of us work directly on tablets, and this feature would make it possible to update on the go without booting up a PC. Think Wordpress.

We have plans to better automate the upgrade process. No ETA yet on when the feature will be available, though.

Bear's got a grudge over Blesta that's all it is on that note, we've been infracted / warned more times than anything. What I was talking about is this.. If people who are your customers can't understand between a invoice needs paying and the renew date is when the next invoice is due, well your not aiming at a market who can understand bills / payments / and webhosting.

Thanks. Added CORE-1076.

CORE-1049, not completed yet. You can track progress through that link though.

Any updates on this bug? Anyone accepting certain classes of orders (not limited to just subscriptions) from California (and soon to be almost all the states if they continue passing consumer rights laws) requires this to be functioning, and its currently holding up the launch of my company.

I have noticed that the service expiry date renews for another term when it is invoiced.  I expect this should actually occur when the invoice is paid.
 
We invoice 14 days before the renewal of the term and some customers will elect to notify us of their intention to cancel at the end of the term.  This then leads to a secondary bug -- if I try to reduce the term back to its original expiry date, I get an error message indicating I need to select a date greater then the last renew date.  If you look at the attached snapshot you will see I am trying to enter 27 March 2014 but it is giving me an error despite it wanting a value greater than 26 March. Perhaps there is a timezone calculation that is awry here as we are in UTC+11 (Sydney, AU).  In the end I just scheduled a cancellation date for 27 March 2014 instead.

We could build an Blesta CSF Unlock IP Plugin to unlock CSF IP's from DirectAdmin and cPanel. if no one has anything against, we will start this week  (We have build one for WHMCS and its easy to migrate to Blesta)

This seems simple and easy to do. We will study this plugin next week, and maye release it

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.
 

New update a few minutes ago
 
Standalone "Support Manager Pro" plugin, check first post how to download and install.
 
Regards,
PV

New update a few minutes ago
 
Standalone "Support Manager Pro" plugin, check first post how to download and install.
 
Regards,
PV