Timothin

Please check your messages.

Everyone who requested a refund received it within 24 hours.
I'm really sorry about what happened and promise to reward the people involved as an apology. Everyone who received a refund, will still receive the license (perk) they originally purchased when the module gets released for free.
I don't want to make the same mistake again, so this time I'd rather not give a release date. I take responsibility for the mistake I made and I hope to be able to amend my mistake soon and make my best effort to never repeat it again. I don't want to use this as an excuse, I take full responsibility for the mistake I made, but I think I owe everyone an explanation. 
The development of the module started in the last week of November 2017, but because I had several projects and tasks to do for other clients, I had no more time available in my schedule to develop the module on my own. So I decided to hire a full-time PHP developer in the first week of December to take over the development of the module. However, for reasons unknown to me, the last week of December my developer quit, causing development to stop.  I personally like to make code that not only works, but is also visually beautiful, trying my best to follow the development standards and follow good coding practices. 
However, I couldn't find another developer that met my criteria, because very few developers are familiar with Blesta. Because of this I started working on the module on my own during the weekends to prevent development from stopping completely, but it still ended up being delayed considerably. Having already finished some of the biggest projects I had, last week I resumed the development of the module again, at half time. Also, last week I got a new developer who will be able to help me in the development.
During this time I decided to make some changes. The final release of the module will not be called cPanel Extended, as I try to avoid confusion with the ModulesGarden module. In addition, the module will not be released under the CyanDark brand, as I am working on a new site specifically dedicated to sell only Blesta related products. With a development team independent of the CyanDark's team to avoid problems.
This is one of the most popular modules that I have, and I promise you that I will not let the module die, soon I will publish more news about the progress of development, but I prefer not to give an ETA at the moment, to avoid problems.
Anyway, I give you my sincere apologies and I hope you can pardon me for my mistake.

Any update on this? 

The .htaccess file included with Blesta already contains a rule to force HTTPS, which is commented out by default. Simply remove the # symbol at the beginning of these lines
# Force HTTPS #RewriteCond %{HTTPS} !=on #RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=307,NE,L] i.e.
# Force HTTPS RewriteCond %{HTTPS} !=on RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=307,NE,L]

That worked, was able to find it and delete it. Thanks!

Thank you! Was able to get this going.

what is a db?
 
 
 
I kid, I was afraid that it was gonna end up in a db modification. Thanks for the suggestions. Seem to have worked.