swerlo

@Paul Interesting that I have to interpret only to you in other words, everyone else seems to understand. Yes, it's the 'read-only' request. Personally I do not like the dynamic around the Blesta, my fault is that I needed more than a month to realize this. In many ways it lacks features, which wouldn't be a problem if this is the first year of the development. It actually looks to me like it's in the first year of development, but as I understand it's there from the 2007. While this is tentatively coming from the frustration it is also a friendly feedback. The lack of this feature isn't the only reason I will probably be forced to look for the alternative software. Wish you all the best.

Thanks CubicWebs. The activity I'm seeing from you, it would be great if there's a half of it from the developers. I'm getting disappointed a little bit here, not much about the software, but about the support on the forum. I do understand there's some procedure, but I think it's not the thing I should care about. From my point of view they are free to organize their business as they think it's the best. My intention isn't to sound rough, but it's more than 20 days since I submitted this request and now I really need to know will it be implemented and in which time frame. Once more time, I politely ask, can someone of the development crew answer this?

Could this request get some kind of priority? I submitted as a feature request, but I also see it as a security option.

CubicWebs is right, I meant on the page title.

As I know you should be able to search and find clients by their name. Also you can just click on their name from the support ticket, if that's the way you are receiving the request, and you'll be redirected to their profile.

I've already have had few suggestions and this is probably the last thing I have to suggest after taking the Blesta. While it's pretty normal for the admin to see the id of the clients, I do not think it's a good practice that this information is available from the client area. I think it doesn't look professional and human. When clients are logged in the client area they should not see the id number (#1501, #1502, 1503, etc).

Hi, I'm forced to use Namecheap at the moment, but I would like if there is a better domain registrar option available through the Blesta. Logicbox interface is terrible in my opinion and somehow I cannot handle their pricing structure, I need to have sub-resellers then to offer domain to the end user... it's too complicated. Also I understand that Enom will be available soon, which basic domain price isn't too high, but whois privacy is ridiculously over priced. Now, I want to recommend implementation of www.internetbs.net/‎ They offer really good pricing (https://internetbs.net/en/domain-name-registrations/price.html). But really it's not only about that though when you do the math, if you have a lot of domains it isn't negligible. They also have easy to use system and free whois privacy. I've been with them for 3 years now and never had a problem. They do have Reseller API, which should easy the process of implementation for developers - https://internetbs.net/ResellerRegistrarDomainNameAPI/. I'll appreciate if this can be supported by the community and if developers can give some feedback would be this possible in the near future. Thanks.

I'll try that. Thank you very much.

Thanks CubiWebs. I suppose it will work, but will this be overwritten when the Blesta gets an update?

Hi, as the title says, I would like to completely remove the billing information (Tax ID/VATIN) from the registration step. I cannot control this from the settings. From the Settings >> Taxes >> Basic Tax Settings, I have unchecked all options and the Tax ID/VATIN still appears.

Hi, I find it can be confusing when the customer comes to the payment step, because there's no clear payment button. Instead there is an image of the payment processor. At least it's the case with the 2checkout. Eventually I have clicked on the image and was redirected to pay the invoice. Still I'm more familiar with 2checkout than the customers and this can lead to unnecessary tickets opening. The point is that it wasn't clear to me how to proceed. I was searching for the button and after a bit of frustration I've clicked on the image without knowing what would happen. Maybe I'm wrong, but I suppose simple button in front of the image would be a better solution. Would like to hear is there a chance to correct this.

After submitting the feature request, what time is necessary to be promoted into the system? And how do we know if something is going to be accepted? It would be much better if we have the appraisal from the developers when the feature would be implemented, especially when those are just small tweaks.

After submitting the feature request, what time is necessary to be promoted into the system? And how do we know if something is going to be accepted? It would be much better if we have the appraisal from the developers when the feature would be implemented, especially when those are just small tweaks.

yes I think so. I saw this at WHMCS.

Hi, Sorry if this is somewhere able but I do not see it. I do not like that clients are able to edit all the fields. We should be able to set fields like 'first name' 'last name' 'email' as not editable for clients from the client area). I would like this to be as the option for admins to configure which fields aren't editable. Eventually if the client really have to change one of these fields they would need to open a ticket and the admin can do this for them. Thanks.