Leaderboard

Configurable options are definitely what you want for charging extra for RAM, Disk, IP's etc. All customers will be eligible to download the beta when it's released. The beta will be available in the download area, to authenticated customers only (You have to login to see it). We're getting close.

ioncube was indeed the issue, thanks Paul

Try this: Update /components/gateways/nonmerchant/_2checkout/_2checkout.php (line # 290) from $order_number = ($this->ifSet($post['demo']) == "Y") ? "1" : $this->ifSet($this->meta['transaction_id']); to $order_number = ($this->ifSet($post['demo']) == "Y") ? "1" : $this->ifSet($post['order_number']);

PHP version is fine, but it's a pretty old version of ionCube. Try updating ionCube to version 4.4 from http://www.ioncube.com/loaders.php. You can download a zip file for a loader wizard that will tell you exactly how to update ionCube. All our stuff is running version 4+ of ionCube without issues, being that 3.3 is a major release lower it could very well be the problem.

Thanks for testing I'll check the web server's restrictions regarding symlinks. I think there is a nofollow somewhere...

I just tested the symlink and it works but it depends on where the file is stored. For example if I put it in something like /root/geo/GeoCityLite.dat and give it proper permissions it doesn't work. If I put it in /geo/GeoCityLite.dat it works. So whatever directory you have it in Blesta isn't being allowed permission to access it through symlink.

But!... But!... drag and drop!

The idea, and it works for PayPal, is that customers who want to pay with PayPal are familiar with the branding of those images and know what to do. This might be less obvious for something else that customers may not have an account with and instead will pay with a credit card on their website. I'm sure something can be done to improve the usability here -- just not sure what the best option is.

I wasn't thinking of a specific environment, as anybody can install the libs in a centralised location for all apps to use, but FreeBSD, via ports, does put the main database in /usr/local and updates it via cron.

Perhaps. The point I am making is that having a public roadmap that shows what features will be added (in what order) will be beneficial to potential Blesta customers such as myself who are evaluating and comparing the software against various other alternatives. For example, I have a list of basic features I need to support my business. When I research the various software possibilities, I have ruled out Blesta because it does not have some of those features. If I can see that those features are on the list to be added... then I will be much more likely to re-consider Blesta as a possible match for my needs. Without the roadmap, I am limited to spending a lot of time digging through old posts in the forums to see what Blesta management might have posted in response to someone else asking about that feature... and it's likely that info is outdated, irrelevant and possibly misleading at best.

In all honesty, a roadmap would be a great "feature" for Blesta to have when prospecting for new license sales. It would certainly allow people like me to make a more informed decision on whether we want to use Blesta or some other billing system. If I know that needed "feature x" and "feature y" are in the queue (and what order in the queue), then I'm much more likely to consider Blesta. Furthermore, I would argue there are few features so secret they can't be added to a public roadmap. Of course, if there's some radical new feature that no other billing system has, then it could be left out. However, I see no reason why any feature that exists in other billing systems shouldn't be included in a public roadmap. It would only serve to show Blesta management is serious and knowledgeable about the direction of their software, in order to make it fully competitive with the others available. Thanks.

That looks pretty cool. Cody and I were actually discussing the possibility of supporting file based HTML email templates in the future. This would add a drop down on the email template page that would let you select a pre-made email template. The template would contain the header and footer, and then anything you enter into the WYSIWYG editor would appear in the content section. While HTML can be used in the templates now, through the editor, this would simplify things dramatically when supporting rich designs, give people that flexibility, and allow a market to open up for email template designs.