Paul

Blesta version 4.0.0-b5 (BETA 5) is now available. You can download it from right here (Client Area Login Required). If you haven't seen the blog post announcement for 4.0.0 BETA 1, you can read it here. This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.0.0-b1-b5. SEE BETA 5 ONLY For older releases see all Change Logs. What to Test! 1. TEST EVERYTHING, IN PARTICULAR ANYTHING TO DO WITH PRICING AS WELL AS PHP 7 FUNCTIONALITY. SEE CHANGELOG FOR SPECIFIC ITEMS. Known issues 1. Upgrading/Downgrading a service as a client does not work because the "Review" button is missing.

You could create a plugin to handle the events. See https://docs.blesta.com/display/dev/Plugin+Events

There is a services add event (hook), see https://docs.blesta.com/display/dev/Event+Handlers but modifying the cPanel module to perform the action may be better.

One of three problems: The username is not correct (double check that it is) Email does not work at all (Do other emails go out, or is it just password reset ones that don't?) If no email, check email settings. Clients reset at /client/login/reset/, not /admin/login/reset/

Hasn't slowed down, v4 is just too big. Post 4.0, will be quicker smaller releases.

That's the worst!

Welcome! What module are you using? I imagine you'd likely need to make a modification to the module to assign port numbers in that way.

I can't say for sure it's resolved in 4.0, but I would strongly suggest giving it a try in 4.0 beta 5 (soon to be released) and report back if it is still an issue. We refactored a lot in terms of how pricing is handled with the new pricing presenter. If it's still an issue, it'll be easier to resolve moving forward.

We use cash basis accounting, so we don't need invoices for tax purposes. Makes sense though!

I've heard of people wanting a copy of all invoices over a specific period of time before. Is this specific to your region/country? Might be a good feature request. I imagine this could be an option under Billing > Print Queue to "Export Invoices" for a given date range (and possibly other filter options), that would generate a single PDF without having to queue the invoices up for print.

Just slammed with v4 stuff. As soon as things lighten up, I'll be doing more blog posts.

Not my.cyberhour.com where Blesta is installed though, at least it's not forced. If you put in https:// then it works. I'd suggest forcing HTTPS, easy to do in your Blesta .htaccess file if you're on Apache @CyberHour https://www.cyberhour.com get's an A- on SSL Labs, nice looking good! https://www.ssllabs.com/ssltest/analyze.html?d=www.cyberhour.com&hideResults=on EDIT: Oh, and I like your Bitcoin specials, nice VPS plans!

Anybody try it out yet? Seems to work great in Blesta 4 beta 4 in my own testing.

We're planning some UX improvements to Packages, but you should still be able to change a Package from "Active" to "Inactive". If the DA server doesn't exist, you could create a new fake DA server in the module, and change it to that and make inactive. I realize this creates a sort of catch-22, which we'll be addressing.

There's no option no, because the service and invoice must necessarily be created to wait for payment to be made. Services are "in-review" or "pending", untill payment is made, so they are not activated. It's also helpful if you find some orders that were never paid, you can follow up with the customer. Do you have a customer who keeps placing orders without making payment? You might want to use this 3rd party plugin that auto cancels unpaid orders - http://blesta-addons.com/client/plugin/store/main/item/7/

If you want invoices to be queued for print so they appear under Billing > Print Queue to be printed and marked as printed, you need to add 1 record for each invoice to the invoice_delivery table. id invoice_id method date_sent 80 63 paper NULL In this case, 80 is an auto incrementing ID, invoice_id is the invoices.id for the invoice you want to print, paper is the method (alternatively email), and date_sent should be NULL. Test it with a few and you'll see them appear under Billing > Print Queue. A bit of a warning on this though, it may be troublesome to generate a PDF of thousands of invoices at once.

Looks like Tyson rejected your pull requests, needs some simple changes.

A new Virtualmin module (alpha) is available. To install, download the attached virtualmin.zip, unzip and upload the "virtualmin" directory to ~/components/modules/ and visit Settings > Company > Modules to install and configure. Any comments or suggestions, please post in this thread! virtualmin.zip

We are planning to maintain it for v4 forward. Keeping that in mind, feel free to submit pull requests on Github, the extension is open source. TheSSLStore Module https://github.com/blesta/module-thesslstore TheSSLStore Plugin https://github.com/blesta/plugin-thesslstore

Oh, that's cool. We're working on it.

Never had a chargeback with BitPay. Not sure what their TOS says, but if you accept payouts via BTC, they couldn't physically do a chargeback. Best they could do is hold future funds.

Doesn't Stripe ask for EIN/SSN? Maybe BitPay treats in differently depending if you accept Bitcoin payouts or USD payouts.. not sure.. but, sounds like they want your SSN and company name.. and for company name you could just use CubeData I'd think.. maybe your Name, DBA CubeData.

You are a business, just a sole proprietorship. I don't think you'll have trouble. I don't recall it being a hassle at all for us to sign up. Did they give you trouble? I asked to have our limit increased once and they did so with no questions and no hassle.

Why not just install the BitPay gateway and use it for Bitcoins? We've been accepting Bitcoin through BitPay for quite a while now without issue.

I don't have an ETA as development on an affiliate system has not started yet. We have more work to do in terms of spec'ing it out before we can start development. As a result, April would be very ambitious. I'd suggest going with a 3rd party affiliate system for now, they all should be pretty easy to integrate.