Virtovo

Will this cause any database issues going forwards with Blesta if they decide to implement something similar?

Thanks. I didnt realise that is what they did. This can be moved/closed as you see fit.

I'm hoping I've understood this functionality correctly. If the BCC notices in the staff group are meant to BCC members of that group when any of the ticked emails are sent then these are not working. Version affected : 3.1.x Steps to reproduce: Tick some BCC notices in staff groups and wait for any of the ticket emails to be sent. Email is working fine for other things to admins (password resets, ticket notifications etc)

This is great stuff. Really boosts the support manager functionality.

How would I manage the below situation in Blesta: Client purchased a $20 package at a special discount of $10 off Customer is enjoying the service and wishes to upgrade. We'd like to offer the customer the same price/performance ratio and to do this we'd have to offer him our $40 package. We'd like to still offer the same discount to the client so to discount the package to $20 ($40 - $20). Is there a way to do this?

Just had Eric working on something for us. He's been outstanding and worked hard to deliver what we wanted. Would definitely recommend.

Please close this thread. I'll deal with the matter in the support ticket. Four days with no response on an issue that is losing us clients is not great. The Blesta team seem like really nice guys; however, the level of support I've received on issues from Blesta has paled in comparison to that offered by WHMCS or Hostbill and that really is saying something.

Any ideas?

Indeed it was, although as I got no followup from Blesta I've decided to pursue this elsewhere.

I didn't receive a PM regarding a testing environment so have looked to a solution elsewhere.

It was held for review by maxmind. It needed to be activated out of review, the cron would not pick it up. I am 99.9% sure the tick box was checked. For instance the service has 'use module' ticked under solusVM options on the service page. I've included some extracts from the Module log which might help inform this further. Although I can appreciate where you are coming from on this point, the alternative you are telling me is to run SQL queries directly on the database. Which is the lesser of the two evils? That is awesome news.

This is a pretty serious bug. It makes a ToS worthless and as pointed out is illegal in many jurisdictions.

Hello there, Thanks for the reply. I did include some additional info in the ticket which explained things a little better; however it's unanswered for nearly 48 hours. I included extracts from the module log in the ticket. To clarify some points: 1) It was provisioned from on hold using the solusVM module. 2) The client received an email with username and password password contained within (for an account which did not exist) 3) Repeated attempts of provisioning an order for this client all resulted in the same outcome 4) I'm not really liking the idea of editing the database directly to work around problems like this. It was needed for the ticket cron import issue I faced and also now this. Not all staff can be given access to the MySQL database directly so this is a massive inconvenience. Is there a reason why these linking fields are not available within Blesta itself? 5) Have you considered having some way to search or filter the module log? The solusVM log fills up pretty quickly as it adds an entry everytime the template list is retrieved. You then have to click on every single entry to see what that entry is. It's a cumbersome task. I'd like to re-iterate that I really like Blesta; however many things feel like I am seriously swimming against the current.

I've got an issue with the SousVM module for a specific client whereby Blesta will not provision a service no matter what. As usual with Blesta there are no error messages or otherwise that could be used to debug the issue. The only steps I know which led to the issue (although not confirmed as the cause) are: Client signed up but met reject score on Maxmind so was not allowed to sign up Client then met review score on Maxmind and order was set to 'for review' Service was activated out of 'for review' Client was sent an email which thought they had an existing solusVM login as it matched on if service.solusvm_password and sent a username (which didn't exist in SolusVM). I've got a ticket open with Blesta, they took the time to move it down to medium priority but did not fashion it with a reply. As a quick solution in case this problem occurs again (I've already lost a high profile client as a direct result of this), does anyone know how to provision a service after it has been created. There is no 'create' option in the service actions. Failing this, is there a way to manually link a VPS to a service in Blesta. This can be achieved in every other billing system I've used by simply assigning the vserverID to the service. I really want to like Blesta; however it's currently issue after issue at the moment and pretty much 0 useful info/errors are given when things do not work.

This page instructs to 'upgrade' http://www.blesta.com/2014/02/12/security-advisory-staff-permission-escalation/ Whereas the post on the forums instructs to 'patch' I am assuming patch is the correct method; however would like to clarify.

Do you have any restrictions on location? Did you need self managed or fully managed?

We've got an intermittent issue with ticket piping ourselves. The fact that Blesta doesn't really give a great deal of insight on what is happening during the pop3 retrieval makes the ability for end users to debug this impossible. The best suggestion I've had so far is to try IMAP instead. Since switching to IMAP I haven't encountered the problem again but I'd much prefer to help the Blesta team fix the issue with Pop3!

Thanks. Seems to have even more problems than I am having with the SolusVM/KVM module.

Can anyone using the proxmox module list the features available client side? Screenshots would be an added bonus! Thanks in advance!

After having some issues with the SolusVM module for Blesta I'm going to try and fix the parts which are half broken for KVM. Does anyone have any suggestions for any features they would like to see added?

This looks great

Sounds great!

Is it possible to pass a coupon code on the order form URL?

If you wish to send a PM of your requirements I'm happy to oblige.

The error reported on the password reset is: <status>error</status><statusmsg>Not supported for this virtualization type</statusmsg> This is not true any longer and SolusVM does indeed offer password resets from the admin side and has most recently included them also from the client side in the latest beta. Regardless if the password reset is not supported for KVM via the API/Module then this should not be exposed to the client and definitely should report success as it is very confusing to clients and causes undue frustration. The same issues pertains to RAM/CPU metrics. It would be far better to not show these metrics when the virtualisation type is KVM as reporting nothing leads people to believe that functionality is broken. Is it possible to add checks to the module for the virtualisation type and enable/disable those features that do not work with that type?