Jonathan

But there's no reason a 5-minute task that causes so much grief can't get into 4.0.  I don't understand the point of delaying something so simple as an image replacement that would curb so many complaints.

This sounds like a great start.  I agree with the due date reflecting what the actual due date would normally be for that invoice cycle.

Yeah having a client side button for this too would be nifty.

For one reason or another, we do get a lot of requests to go ahead and generate the next renewal invoice for a service early.  The ability to forcibly generate these from an admin standpoint would be excellent!

For one reason or another, we do get a lot of requests to go ahead and generate the next renewal invoice for a service early.  The ability to forcibly generate these from an admin standpoint would be excellent!

Knowing quite a bit about the internals and history of cPanel and their very early beginnings this statement is quite correct.  A lot of these changes are because Nick is finally letting go of some power to an extent whereas in the past he's pretty much single-handedly reviewed each piece of code, rewritten lots of it, etc.  In recent years cPanel finally started getting structured like you'd expect a software development company to be.
 
I can't say I'm perfectly happy with it.  While yes changes are coming much quicker these days, so are bugs.  Some of that is due to how inherently large cPanel has become as a software package but some is because they're pumping out features like crazy and can't do as much QA.  The "stable" tier of these days is like the "release" tier of 5 years ago stability-wise, and what was the stable tier then no longer exists due to the rate at which they're pumping stuff out.

I have bumped this up in the backlog.

This is why I never rely on third-party plugins, mods and themes -- especially anything paid (and ESPECIALLY anything obfuscated).
 
I learned that lesson a decade ago.
 
The whole "not releasing it, hmpf" attitude is a major reason why. It reminds me of a child: "If I can't have it, nobody can!" So it's nice to see a developer realize that open-sourcing it is needed. Otherwise the dev is really just screwing over existing clients.

+1

Having an event for services.schedulecancel would be immensely helpful.  It'd be triggered upon a service being scheduled for cancellation.  We'd also need the inverse event upon unscheduling the cancellation.

Having an event for services.schedulecancel would be immensely helpful.  It'd be triggered upon a service being scheduled for cancellation.  We'd also need the inverse event upon unscheduling the cancellation.

Can we get a CORE task created for this?

I second this.  Such functionality is quite nice in other systems.

For both refund and void commands in auth.net CIM, the API command "profileTransVoid" is sent when for refunds "profileTransRefund" should be sent.
 
This results in refunds failing 100% of the time unless it's an unsettled transaction.
 
To recreate, try to refund an auth.net CIM transaction.

For both refund and void commands in auth.net CIM, the API command "profileTransVoid" is sent when for refunds "profileTransRefund" should be sent.
 
This results in refunds failing 100% of the time unless it's an unsettled transaction.
 
To recreate, try to refund an auth.net CIM transaction.

I think it would be alright, but perhaps consider putting the gateway name in the text so it's very clear.  "Check out now with PayPal/Skrill/<gateway name>" type thing.

I think I found the issue.  Will update this post with more info once confirmed.

I think I found the issue.  Will update this post with more info once confirmed.

After receiving numerous complaints about the current buttons not being clear, we've found folks really like this one:
 

 
This should definitely be updated to be more clear to folks trying to make payments via PayPal.

Glad to see this has gotten use (had just gotten a thumbs up on WHT regarding it).
 
I didn't realise at the time but vQmod 2.4.1 has a 'semi broken' cache engine in that it takes more time for cached renders then it should.  If there is demand I'm happy to update to 2.5.x release.

You got it - CORE-1725

Looks great guys!

Looks great guys!

Looks great guys!

Looks like there's no checking here for a valid hostname.
 
"google.com" is not a valid hostname for the purposes of a Linux server's hostname.
 
"host.google.com" is.
 
This causes some issues with many things inside of a VPS such as cPanel being a big one.  cPanel will not recognize a raw domain name as a hostname.