Leaderboard

Cheers!

We've talked about a package clone ability, drop you into the create a new package form with all the details copied in. It's a good idea, any more +1's?!

Attached is the Proxmox module for Blesta. Special thanks to Alex at Full Ambit Networks for creating the module and giving us rights to it. We'll be officially including it in v3.1 of Blesta. For now, we'll be considering it a beta module, and would appreciate any feedback you can provide. You can upload the contents of the attached zip to your Blesta installation directory, and then head into Blesta's admin interface to install the module under [settings] -> [Modules] -> [Available]. proxmox.zip

It's possible yes, but probably not likely for your bootstrap conversion. We're planning to do this ourselves for 3.2 and it's likely we'll go a slightly different direction than you have.

CORE-494 - Add client ability to reset password for cPanel, DirectAdmin, Interworx services.

Hi Guys, We have successfully enabled CSF plugin to unblock IP with option to select servers (if we have configured multiple servers in Blesta). Screenshot attached.

Nope but you should make it after you've added a server.

The module supports both KVM and OpenVZ. You select the virtualization type when creating a package using the Proxmox module.

Now I can see how to activate KVM machines. So I'm fine. No, proxmox support KVM and OpenVZ.

Thank you mate, very kind of you

LOL, I love this. Your function that you hacked together to decrypt their data is faster than the one they use. That just proves how much better at this you are than them.

Or have a BlestaTracker plugin built into Blesta. and then maybe sold for $xxx.xx haha.

hmm...I guess in that case I'll stop working on my super sekrit bootstrapped Blesta > Joomla bridge...until 3.2

You can get the Proxmox module from my other thread.

I remember talking to Cody about SolusVM mapping and it sounded challenging due to the differences in how they do things so we skipped over it initially. We'll be taking another look at this

Why do you need to change a password from the manage module section? Isn't that what the Module::manageAddRow() and Module::manageEditRow() methods are for? Nonetheless, if you wanted to have custom tabs, you would need to use GET parameters, and handle them in your Module::manageModule() method. So: may link to: $link_buttons = array( array('name' => $this->_("Test.add_module_change_password", true), 'attributes' => array('href' => $this->base_uri . "settings/company/modules/manage/" . $module->id . "/changepassword/")) ); and then you would update your module: public function manageModule($module, array &$vars) { // Load the view into this object, so helpers can be automatically added to the view if (isset($_GET[1]) && $_GET[1] == "changepassword") { $this->view = new View("change_password", "default"); # # TODO: to whatever else you need to do # } else { $this->view = new View("manage", "default"); } $this->view->base_uri = $this->base_uri; $this->view->setDefaultView("components" . DS . "modules" . DS . "test" . DS); // Load the helpers required for this view Loader::loadHelpers($this, array("Form", "Html", "Widget")); $this->view->set("module", $module); return $this->view->fetch(); } I haven't tested this, but that should be pretty close to getting it to work.

I haven't used cpanel extended yet, but it's shocking that it can't do it...seems like a pretty basic/standard feature for an extended module +2

I'm about to try a test run with live data to remedy the credits discussion from the WHMCS beta importer thread. It occurred to me that an excellent failsafe would be to mass set all email addresses to my personal address. This would not only ensure that no clients get emails, but would also allow me to execute tests to see what happens (our payment and module gateways are disabled for testing). Is there a quick and dirty database hack to mass set all client email addresses? I'll be re-importing the client database before going live, so data corruption isn't a concern here.

What specific type of documentation are you looking for? What's missing? I've always considered their documentation to be quite detailed. You are using: http://docs.blesta.com/display/dev/Overview?

I don't have a WHMCS install at the moment so I'm not sure what the actual table/column is so you will need to change those to the correct name...but this should work: update tablename set clientemailcolumn = your@email.com of course test this on the test database, and not the live database and this isn't always an issue, but depending on your database/phpmyadmin settings...if it doesn't allow you to use that (some settings prevent using a query to change all records in a column), use the one below that will make it think it's not affecting everything even though it actually is update tablename set clientemailcolumn = your@email.com where 1 = 1

I'm not sure if it does or not, but we're deploying an InterWorx cluster on dedicated colo hardware so virtualization concerns aren't a big deal ... unless it's going to cause trouble with CloudLinux's LVE. That's one of the areas where InterWorx has room for improvement: brute force protection for client accounts (there is none). Other than that it's a swell panel.

Yes, We're checking this with Blesta team and are waiting for an update from them. Thank you Daniel

For me, I'm not sure how much I would use it. The thing to me is this, I might only use it 3 times a year but those few times I did use it I would be thinking "things like this is why I love blesta." I'm gonna say +1 not because I would use it often, but because it would make blesta a sleeker piece of software.

That's very strange, because I took a SQL backup immediately after installing Blesta. After my last trial run I restored that database. I'll delete the databases, reinstall, and try again. Hopefully that's all it is! EDIT: Sheesh. That was it. So much for my mad cPanel skills. Everything is fine, nothing to see here.

We have to make a lot of assumptions if we start voiding invoices and cancelling services. To start, cancelling a service would be immediate and permanent. If you accidentally mark the client as inactive, you've done something potentially disastrous. If we void an invoice that had a partial payment, that difference is then returned as a credit. If we do none of this, but simply stop billing people with active services whos accounts are marked inactive or fraud, and the account becomes active again later -- those services will be back billed from the time the account was made inactive. So, the simplest, most straight forward way to handle it is to manually void and cancel. Marking the client inactive or fraud prevents them from logging in, and designates the account as such in the system. We want to leave you with control over how to handle any open invoices and active services.

Doesn't APF/BFD have issues with virtual servers? We use to use it and switched to CSF/LFD because of it if I recall. Maybe we can nudge Interworx towards CSF/LFD.

Really appreciate the progress on this. I know some people think an importer is their entitlement; however, having used competing billing systems importers or got into dialogue with the devs regarding one Blesta has been the best experience so far.

Ticket status is fixed for the next rev. We're working on adding diagnostics, and looking at ways to improve runtime.

I've noticed one thing around here and that is that everyone seems to have the a module, plugin, importer, feature that they need. Sometimes there is this insinuation that the devs aren't doing enough or list of things which they 'should' be doing. They can't just drop everything on focus on just one client with their specific needs alone (show me one company that does?). Mind you that it's a client management and billing system. It has an open modules/plugin system which means you can develop or have someone develop your modules. You can also have your own importer build. But if you're going to wait around for the complimentary modules and importers that come at no cost to you then a little patience are in order. Especially if your going to critique them about their so-called 'behind-the-scenes problems' as someone described it. If it was so easy and you want get migrated so badly why wouldn't you just build it yourself? Nothing is stopping you. Blesta is build with quality in mind and this takes time. The community couldn't be more helpful. I don't mean help this topic run away but good grief! It had to be said.

I've just gone back over this topic a couple of times and some of the posts are shocking me with the lack of patience and damn right rudeness some are displaying here I would like to remind people the WHMCS Migrator is still in "BETA" also seen those asking the same stuff which has been address previously I feel strongly the Blesta guys need to add a basic F.A.Q for those moving from WHMCS to Blesta.

Haha mate, on WHT he's slated every single one. So not much for him to choose from.

The system isn't garbage. With a few hiccups, it works great. Far better than our experiences with WHMCS or PBA. Patches are being released rapid fire to nail down bugs and suggestions. You've got one of the lead devs personally helping you troubleshoot your issue, which may even ultimately turn out to be a problem on your end. And that's not good enough for you? Sorry that some brand new software had a few bugs, I guess. You may not be aware of this, but your posts are coming off as petulant and entitled. If you don't want to actually work through the issue, there are other billing systems to choose from.

I would like to suggest we have a banned status (We have a Active, Inactive, Fraud Status at the moment) but when a user is classed as Fraud, they can still make support tickets, and I'm not sure if they can make new orders. We don't have any other way of removing rude customers. Eg: False information on account, acted like a immature person opening a ticket in gibberish. Closed ticket, set customer as fraud... Few minutes later another support ticket from that client. In the end had to ban them in the firewall.