Paul

Are you using a reseller username, and not root? Someone reported an issue where root plans were displayed, but not those for the reseller user.

Ah, ok sounds good. The patch is going through QA now.

I've assigned this additionally to CORE-727.

I was able to duplicate this, please change.. To.. In both the HTML and Text sections. Note it requires 2x "=" and not 1.

This has been corrected, and a fix was posted in the referenced thread. The patch will hopefully be out later today. Not sure the reason for the new thread though..?

So the issue here is just that coupons are applied after tax, rather than before tax?

Please post the content of both the HTML and text sections.

Blesta is very dynamic, and a lot of things shouldn't be cached. Blesta does some of its own caching, if your cache directory is writable. I'm not that familiar with Cloudflare (though they are great guys, and we've met some of them) but if there's an option to disable caching for Blesta I'd do it and see if that corrects many of these issues.

Looking good!

I think that some method by which to automatically sort clients into specific client groups would be good to have, so it's a good idea. Before we would consider such a feature, we would probably want to see some different use cases so that it could be designed in a way that is broad in scope.

It's working for you now, so that's good at least.. chalk it up ta some kind of glitch. If a particular widget has an issue, just that one widget won't load. So, I thought this was a pretty interesting case since none of them loaded.

Resellers are able to offer v3 licenses, however it's taking some time for some of them to get up and running. v3 is based on an entirely new licensing system. All resellers currently have the ability to add v3 licenses in our interface, but we are still working on the API so they can issue v3 licenses automatically in their systems.

Clients can already close tickets from the ticket overview at /client/plugin/support_manager/client_tickets/ I've assigned the auto ticket closure feature to CORE-725

We should have something preliminary to test for WHM** by the end of this week. We want to do a HB importer next, but we don't have a copy of the software running and the lack of trial or monthly license makes that difficult. Does anyone have a dev or non-production license they are willing to lend us?

Awesome, good to hear. It'll be in the patch tomorrow or Wednesday along with some other fixes.

We are aware of this issue, though it appeared to be more limited in scope. It's suppose to be fixed in 3.0.2, would you mind testing the attached file? 1. Backup everything 2. Overwrite /app/models/services.php with the one attached. Let me know if it solves it. services.php

SolusVM deserves some praise for taking security seriously. You could argue that they should have been more security conscious earlier, but this was a good move.

1. Haven't thought much about that, but it's something we can certainly do. 2. Yes, we are planning to offer a verification badge. It will not be free, because we will need to audit the code to make sure it's safe. Those that want to purchase the service, and who pass our verification process will get the badge. 3. Good idea

We are looking at ways to make it public, and may do so in the future. For now, we try to post the task # in the forums for bug reports and feature requests to indicate it's in our system. The same number is included in the changelog for releases as they are implemented.

That's really odd, I'm not able to duplicate. Is anyone else experiencing this issue?

Does anything appear in the module log under Tools?

Did you change any of the templates? All the widgets load via ajax, and it's pretty easy to break them if editing the templates directly.

When you add a custom field, do the client groups appear in the drop down for "Client Group" at the top when creating a custom field?

The image hasn't come through. Which widgets specifically are missing?

It registers itself and runs early on in the application, so it's not really possible to limit its scope in any significant way. Which, I think, is by design, otherwise an attacker might be able to figure a way around it.