Paul

Just to add, even though the documentation says we don't allow tickets from reseller customers, you can still open tickets and we will respond to them. We are just limited in what we can do.. for example, we can't re-issue your license or upgrade/downgrade, add support & updates etc.. as the reseller is responsible for that.

That's a really great deal for 12 Years!

Great! Thanks for the update. Cheers

@naja7host are there any specific events that you would find particularly useful that I can look into? Ones that you would use? We can't add a whole bunch of events, there isn't enough time for it, but it *might* be possible to add one or two, or at least get those prioritized.

This may be related, see CORE-1937 This happens if there is an error. In your ticket, you mentioned a module row error, correcting that error should correct the 404 redirect you are seeing. The fix described in this task will show the error rather than the 404 page. So, your solution for right now is to correct the module row error. The module row error is most likely a side-affect of having deleted the module row on the module (For example, the cPanel/WHM server under Settings > Modules > cPanel: Manage) The solution is to edit your Packages, and re-save them with the correct cPanel/WHM server selected.

This is undesirable but it's not technically a bug. Because the Customize tab is a different controller and because it's not registered into the nav under a new section (Like Billing > Customize Reports) or something, it doesn't know that it should be under Billing > Reports. This is how any other plugin would work as well, using a different controller, without registering its own subnav item. This makes a "fix" more difficult. Cody tells me that it may be able to be corrected using a route, but that's probably not ideal. It may require a more complex solution. Good catch though, I can't believe I didn't notice that myself.

I wonder if there is a .htaccess file in the parent directory to Blesta. If so, it may be interfering with Blesta. Can you tell what the URL is before it redirects to /404/?

Nice work, very different!

What do you sell through TCAdmin? Are you using TCAdmin v1 or v2? It's moving up in terms of internal priority, I think it would compliment our Multicraft module in a big way.

You got it

Nice work! I see the price is $7/mo on your order page. Do you want me to edit your original post to change it from $20?

Is this still an issue? Do you have mod_security or anything that may be getting in the way?

Nice work! I sent you a little donation. If you're reading this and you aren't @naja7host, consider buying the plugin or donating.

If the contact opens the ticket, you'll be able to see that it was them that opened the ticket. No current way to open a ticket for a specific contact at the moment though.

Nice work!

Allow clients to change their client area theme? Have you had any requests from customers for that?

Great, thanks for the update!

Is your cron set up? The cron activates the service. Also, if paying a specific invoice, payment should be immediately applied when the transaction is logged. If making a general payment on the account, it will be issued as a credit and applied to oldest invoices when cron runs unless you've disabled automatic application of credits.

Great, thanks for the information! I'm assuming it's a 3rd party cpanel module then?

Nice KB article Mike, I gave it a thumb!

Well that's a bummer. I posted instructions on how you can open a ticket in my response above on Jan 25th. http://www.blesta.com/forums/index.php?/topic/5786-importing-whmcs-bombed/?p=40973 If they reconsider, feel free to open a ticket. We'll help out as best as we can.

If you have an old server with cron running, yes, it will chug along like normal even if the license is invalid. You will want to kill that cron, and preferably delete the old installation.

Every make any progress on this? For cPanel, if it's unable to connect usually it's a firewall issue. Blesta needs to make an outgoing connection to your WHM server over TCP port 2086 or 2087. Make sure those ports are open for egress traffic.

Is it an internal server error on your Blesta installation? Does it take a while before you get the error or does it happen right away? It's possible you may not have enough memory in your php.ini, or the timeout could be too low. Internal server errors can also be unrelated, having to do with a bad PHP extension or any number of things. To find out more, it's best to check the server logs.

Does Blesta's mail log show 2 emails going out to the customer? See Tools > Logs > Email tab. The email address of the customer isn't the same email address for any staff is it?