Paul

If he doesn't reply in the next day or so, then yeah probably email.

Cody may be able to provide some direction for getting this to work for you now, I'm not sure. We are aiming for an 8 week +/- 2 week release cycle, but this will vary and we expect our 3.1 release to take a little longer, since we've spent much of our time since release resolving bugs. Moving forward, we expect the number of bug reports to diminish. We expected to receive a higher number of bug reports after our initial 3.0 release, being that it's all new code. Give us a few releases to get in our groove.

Added the graph as CORE-743, it will be independent from the "Range" revenue graph. This will result in up to 2 revenue graphs being displayed at the same time, year to date and range (7 or 30 days).

It's assigned to CORE-741 and tentatively slated for v3.2. It will add a new authentication mode drop down, with plain, login, cram-md5, and null/none as options.

Not sure if this was answered, but yes the domain a license is associated with can be changed anytime. You would login to your client area, click "Manage" next to your license, then "Manage License", then check "reissue" and save. This is required anytime you move your installation.

It's not supported but there appears to be a transport for it for Swiftmailer, which we use. Cody doesn't think it would be terribly difficult to add. How widely used is CRAM-MD5? I honestly have never heard of it.

Enom is scheduled for v3.1, and we are now transitioning most of our resources to development for 3.1. Still, we will release an Enom module for testing as soon as it's available, and the idea is to include it officially with 3.1.

I think this would be a change to the cPanel module to allow a location to be specified on each cPanel server in the module configuration, and then a service field would be created to allow the user to select from it. It's a good idea, we'll need to look at in in more detail. If you have a recommendation of how it should be implemented, please let us know.

Go to edit each support email template and click to save them. If there are any syntax errors it should produce an error. A syntax error in an email template can prevent it from going out. We only recently started doing syntax validation on them.

CORE-732 exists for a "Revenue this Year" stat. I also want to do a yearly graph, however I'm trying to decide whether we change the graph date range and add a new option for this in the drop down (currently 7 days, 30 days), or add this as its own graph. What do you think?

CORE-737, tentatively assigned to 3.2

Normally I would say something like "We can't release information about any security practices.", but no, we are not using PHPIDS ourselves. Not right now anyway, that may change.

It has already been assigned to CORE-676, tentatively slated for 3.1.

Yes JIRA. We prefer not to have anonymous tasks posted though, end up with duplicate items or items not well spec'd out, or that we don't plan to add. Basically it comes down to me having the time to sit down and figure out all the permissions.

CCAvenue is assigned to CORE-736.

I believe that is correct

We are planning to add a setting to disable automatic application of credits, and a feature to apply credits to invoices manually. This task is assigned to CORE-468

That option is already there. When adding a service as an admin you can select "Do Not Invoice".

You may be affected by the same issue, we'll have to look into this. Do you see any packages at all, or none?

Create a new package that uses the same module that is free, then Manage the service on their client profile page as an admin, and you can change their package to the free one.

Cant you just update the package pricing for all terms to $0.00?

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.