Alex Vojacek

I am sorry but WHY on earth would you want a system that penalize a customer if he doesn't pay in time?.  This feels like you want to put the customer into a school regime were the admin will yell at him if he misbehaves.
I dont see this working in any meaningful way, it will just harm the customer-service provider relationship and I'm sure it will provoke more users to leave your services for good.
 
You don't penalize a user for late fee, PERIOD.  You can add the "late-fee fee" but that's about it.  I've never seen any system that worked this way, why are you trying to reinvent the wheel. Concentrate on making something that will add value to the customer instead of trying penalize them.

I am sorry but WHY on earth would you want a system that penalize a customer if he doesn't pay in time?.  This feels like you want to put the customer into a school regime were the admin will yell at him if he misbehaves.
I dont see this working in any meaningful way, it will just harm the customer-service provider relationship and I'm sure it will provoke more users to leave your services for good.
 
You don't penalize a user for late fee, PERIOD.  You can add the "late-fee fee" but that's about it.  I've never seen any system that worked this way, why are you trying to reinvent the wheel. Concentrate on making something that will add value to the customer instead of trying penalize them.

I am sorry but WHY on earth would you want a system that penalize a customer if he doesn't pay in time?.  This feels like you want to put the customer into a school regime were the admin will yell at him if he misbehaves.
I dont see this working in any meaningful way, it will just harm the customer-service provider relationship and I'm sure it will provoke more users to leave your services for good.
 
You don't penalize a user for late fee, PERIOD.  You can add the "late-fee fee" but that's about it.  I've never seen any system that worked this way, why are you trying to reinvent the wheel. Concentrate on making something that will add value to the customer instead of trying penalize them.

I left blesta because I couldn't handle domain management, at all, and the current state it is now it's almost ilegal to manage domains through blesta since it wont comply with ICANN,  so... how is this feature that all the major billing systems already has, something like: 
 
"They can't make it any faster as 4.0 isn't out and they have over 30+ tasks to do on that before they can waste a whole version on modifying and changing the way domains work. "
 
I stopped reading that phrase..  and I will re-phrase it.  The developers CAN'T waste any more time on other features that are not as important as this one.
The sole fact that your clients are asking for this feature and you take it so lightly saying it's a WASTE doing such a task speaks volumes on what you'll get with the hosting market.
 
You definely made a billing system that is NOT hosting friendly at all and you don't recognize this.. no, it's even worse, you wont accept what your clients are asking for.
 
This attitude is not good.  Clients ask for important stuff and developers should follow through and this is not an non-important feature... this is something all the other major billing systems already have and this is a feature that,  as it is now it's not ICANN approved, turning all your hosting clients into an almost ilegal sellers of domains...  
 
Developers should VERY concerned about this situation.   When I left blesta, the only new feature I had was "Mass Cancelation" but I didn't have (and still isn't available)  MASS EMAIL,  a featured that is soo much more important than Mass Cancelation.
 
If I have downtime expected on the datacenter I won't be able to let my customers know about this, but, I would be able to Mass Cancel all of them if they complain !!
 
This is not the way you build a billing system.   If I come here and seems to be complaining is because I felt I was not taking into consideration when I had my tons of problems with Blesta and developers were always doing more important stuff than the things I was asking, hence.. I left for WHMCS,  when I customer goes, it should make you take notice of why it was,   this is a good way of improving your attitude and your product.
 
Nobody asked me why I left, they lost my opinions about it the same way you'll loose the next customer that complains by replying "they can't waste time...".

My point is simple, because there is no domain management, the product is defective for the majority of hosting providers.
 
Even the large domain resellers are now focusing on WHMCS and have given up on blesta, until we have some form of domain management this will only get worse.
 
Since you are a blesta reseller, you have an extreme bias towards it.
 
I have lifetime owned licenses for WHMCS/Blesta/Clientexec/AWBS. 
 
Besides the domain management, blesta is a fantastic product.
 
As of right now the best WHMCS alternative is clientexec, which is sad.
 
If blesta lacks the resources, they need to hire more developers and expand, and/or offer bounties.

I hope there is more to it than 'just pricing tables'.
 
On the admin side, when a domain is pending transfer from another registrar, Blesta is trying to provision the service every 5 minutes (or whatever the persons cron time interval is) and I hope this can be dealt with. There's also no place to enter an EPP code if an admin creates the order on the admin side for the customer.  I think the 'Basic Options' section of 'add a new service' needs to have the options 'Transfer or Register' and if Transfer is selected, a field for an EPP code (optional) should appear.
 
As far as the pricing tables, I think a simple setup of 3 tabs in the pricing section of packages -->> browse that say 'Register', 'Transfer' and 'Renew' would work just fine. I don't know if these 3 tabs would be triggered from the 'Account' and 'Type' under Module options. That way it only shows if the type is 'Domain Registration'.
 
The other features that would be nice to have are 'Privacy Protection' and 'DNS Management' built right in. This may be a Logicboxes specific request though. Right now, if someone orders Privacy Protection, we have to login separately and activate this features vs. the system automating it.
 
I forgot to add one thing. Domains should be separated in the admin and client area. Not grouped together with the other services. We (and I'm sure many other companies as well) have clients with 20+ domains and it's not so easy for them to sort out and manage them.
 
Yes, the domain system is useable right now but it requires a bit of manual work from the employee / admin side. For the companies with hundreds and thousands of domains to manage, this causes a lot of extra work and automation and productivity is lost.
 
There are other features such as 'Resend verification email', 'Child Name Servers', etc that I would imagine are going to be handled by developers creating an 'extended' version of each registrar module.
 
Just my 2 cents.

Domain management in Blesta works if your customers have one domain they've bought at the same time as their hosting or if they've transferred the few they own and don't care about maintaining them (leaving that ICANN responsibility to you). It fails when you have a dozen+, spread across different registrars and if you're selling more exotic domain names (with the registration restrictions).
The biggest problem though is the lack of self-service option on the client side. It should be as good as what Enom or Logicboxes has to offer. Customers should be in control of their domains (contacts, DNSSEC, EPP, privacy protection, trustee service, etc.). Blesta should just sit one level above registrars, offering the huge benefit for customers of having only one system to use to manage all their domains.

May I suggest the developers to take this problem seriously and include the "test for the session path"  onto the installer? It will save a lot of time to people who comes from a VPS trying to install blesta onto CentOS (which is the OS of choice for hosting).

Since CentOS clearly set this session path wrong, it should be mandatory to test for this to work properly before installing the software, this will avoid weird error messages (like the one I had) and the debugging should be much more easy then.

It's definitely not php-fpm settings as I'm only using nginx as a front end reverse proxy (apache in the back) and don't even use php-fpm but I came across this problem also.
Prior to adding the include path explicitly as stated above my php info already reported the include path as .:/usr/share/pear:/usr/share/php
So this error makes no sense to me at all nor does the fix.
 
Took me 4 days over the course of a month to diagnose so thank you Alex and Alex only.

I am having the same problem and it's on the same service the original poster had
 
Attempting to provision paid pending services.
 
I don't have the slightest idea as to how identify this service or remove this from cron.
 
I agree, looking into the mysql database is totally unaceptable, plus, there is not indication in the system as to what cron task is failing so, the user cannot do anything about it except to find this thread on google.

I did this on my portal and had time to customice it.
 
The portal is incredible powerful as it lets you use html,  something I shocked hostbill didn't allow.
 
You can pretty much put anything on the portal page.
 
take a look
https://clients.elysiumservers.com

I agree Ken,  thank you for your kind words.
 

I try not to take it personally. I'm just pointing out that a little cortesy is nice!, like your answer!

Bootstrap Conversion
*******************************************************************************
I have been and still am in the process of building a completely responsive theme for Blesta. It is not completely finished but is very close to being complete.
 
I plan on selling this theme for a low cost so that I can continue updating it.
 
 
 
 
Desktop Screenshots
*******************************************************************************

 
 
 

 
 
 

 
 
 
Tablet Screenshots
******************************************************************
 
Will post these in just a moment.
 
 
 
 
Mobile Screenshots
******************************************************************
 
Will post these in just a moment.
 
 
 
 
 
Try it yourself!
******************************************************************
We all know actions speak louder than words, so login and see what you think!
 
http://dev.memoryx2.com/members/client/login
 
Login: test
Password: tester

Hello wonderful community.
 
I just bought my first license of blesta, the owned unbranded.
 
I finished my portal here:   http://clients.elysiumservers.com
 
but as you can see, some parts reads in https and some in http.  I managed to create a rule in nginx for the server to load each part and jump to http each time but it is of no use since a new web browser will ask for authentication in the SLL as soon as the redirection tries to work.
 
I know all about SSL but as of right now, i can't change the http url on 2checkout without having to pay them for doing it and I really don't want to pay for a SLL certificate so my clients don't  look to that horrible red page of "unsecure, danger... better leave"  unsecured SSL.
 
 
Is there a way to completely disable SSL and force blesta into http only?,  probably in the future when I have more money I will change the 2checkout url and pay for a SSL authority certificate but right now, I spent all my money on the license.
 
If you point me in the right direction I think I can handle myself, I need to know at least the files that controls https and http.
 
Thank you guys.

I did this on my portal and had time to customice it.
 
The portal is incredible powerful as it lets you use html,  something I shocked hostbill didn't allow.
 
You can pretty much put anything on the portal page.
 
take a look
https://clients.elysiumservers.com

https://clients.elysiumservers.com/index.php/
 
Thanks so much guys!
 
Conclusion:  DO NOT disable https, ever.

As harsh as it may come accross, cloudrck is 100% right.  If you can't poney up for a decent SSL cert (or use StartSSL and get them for free, with awesome security still), or don't know how to get a simple SSL cert to work on your domain...then you need to be learning how to do that.
 
If I go to someone's cart, where I have to input my payment details...and there is not https in that address bar...the site gets closed and I move onto another place that cares about the security of my information.
 
Forcing http when you are offering any type of online service and intentionally not using https simply because you do not want to pay for a non-expensive certificate is definately not the way to start in this industry.
 
Not trying to be rude, just trying to keep you from falling into trouble.

Hello wonderful community.
 
I just bought my first license of blesta, the owned unbranded.
 
I finished my portal here:   http://clients.elysiumservers.com
 
but as you can see, some parts reads in https and some in http.  I managed to create a rule in nginx for the server to load each part and jump to http each time but it is of no use since a new web browser will ask for authentication in the SLL as soon as the redirection tries to work.
 
I know all about SSL but as of right now, i can't change the http url on 2checkout without having to pay them for doing it and I really don't want to pay for a SLL certificate so my clients don't  look to that horrible red page of "unsecure, danger... better leave"  unsecured SSL.
 
 
Is there a way to completely disable SSL and force blesta into http only?,  probably in the future when I have more money I will change the 2checkout url and pay for a SSL authority certificate but right now, I spent all my money on the license.
 
If you point me in the right direction I think I can handle myself, I need to know at least the files that controls https and http.
 
Thank you guys.

Hello wonderful community.
 
I just bought my first license of blesta, the owned unbranded.
 
I finished my portal here:   http://clients.elysiumservers.com
 
but as you can see, some parts reads in https and some in http.  I managed to create a rule in nginx for the server to load each part and jump to http each time but it is of no use since a new web browser will ask for authentication in the SLL as soon as the redirection tries to work.
 
I know all about SSL but as of right now, i can't change the http url on 2checkout without having to pay them for doing it and I really don't want to pay for a SLL certificate so my clients don't  look to that horrible red page of "unsecure, danger... better leave"  unsecured SSL.
 
 
Is there a way to completely disable SSL and force blesta into http only?,  probably in the future when I have more money I will change the 2checkout url and pay for a SSL authority certificate but right now, I spent all my money on the license.
 
If you point me in the right direction I think I can handle myself, I need to know at least the files that controls https and http.
 
Thank you guys.