Leaderboard

Here's a mockup.

Ah, yes, the pricing had been refactored into the pricings table a while after those source doc comments were written. Sorry for the confusion.

I suppose you would need to select a different Type to set a default value. Maybe another improvement could be to allow default values to be set/selected for each type. I like the idea of adding in more improvements to custom fields, like making a field read only only after it has been added once, but that is beyond the scope of the current "Read Only for Clients" option. I wouldn't want to tie this feature into that setting because it would add unnecessary complexity. A setting should only handle a single, specific, use case. I wouldn't want users to be confused because "Read Only for Clients" would then be conditional on whether a client is being created or edited. Of course, you could update the Order registration form to update this behavior--and by all means, feel free to do that--but we have to consider how this would affect everyone that uses custom client fields, and provide the best simple and general solution for all. I believe the simplest solution here would be to create a new setting to handle that case.

I think this falls into 4º- Setting configurations that can contradict each other in some contexts (i.e. misconfiguration) But there are two main kinds of bugs: Functionality that does not work as intended A program that causes an unexpected error or flaw (basically #1) Both of those would be determined from the perspective of the software developers. I would say this is not a bug because "Read Only for Clients" is clear that the field is read only. If it should also be a required field, then you should set a default value, because read only fields cannot be written by clients. It sounds like you want an option for clients to set a value once, but never again (i.e. add but never edit). And I think that might be a good feature request.

Currently we have Services.add and Services.edit. It would be great to have Services.terminate (cancel?) and Services.suspend to greatly increase what can be done using events Personally I need to use these to trigger some licensing functions.

This are all the ideas related to domains I have, not all of them are for the domain manager. I'll expand on the list later and say how I think they should actually be implemented. Allow clients to set default nameservers Easy way to set nameservers back to hosting company's default Select whois contacts from client's contacts - will fill in all fields possible leaving extended fields to be populated manually. Easy way to set contacts "same as registrant" or "same as tech" Possible linking of whois contacts and client contacts Allow customers to set auto renew and term Expiration reminders set per extension to comply with registries Group extensions by allowing multiple package groups on domain and other form List all extensions with prices and module/account Set pricing for registration, renewal and transfer Automatic import of existing domains from registrar Periodic price import from registrar Sync expiry dates with registrar After renewal update expiry dates as renewal term may start from payment date not expiry date Log domain history Allow pre-registrations Check transfers completed Set if registration/transfer allowed New "universal module" for domains with whois check Add new statuses like pre-registered, transfer in progress

I was just wondering why the configurable options and addon packages don't have descriptions to explain what they are for. So I would like to open a feature request to have a ? next to or a line underneath the title with the description set.

Custom fields are specific to client groups, but every client must be in a group. If a field should exist in all groups, it will necessarily have to be added to each group. This task simply allows for a default option to be pre-selected.

Maintenance mode in v3.4 will allow for Markdown, and be displayed on its own page. CORE-1395

the sammple and logical solution for Read-Only + Required is : That was my point of view .

Agree! Need to be able to sell domins like Godaddy and have it so that people can manage their DNS but, not have a hosting account. Managing the cPanel DNS is easy from their PHP API. A full module for this would be great so that we can use our eNom reseller account to sell only domains+dns and have it all managed via Blesta.

This would be great for clients that want to purchase domain names and manage their DNS from our company vs having to have a fully cPanel account in order to manage their DNS. A module would fit that bill perfectly since cPanel DNS can be fully managed via their API.

What part is misleading from the docs? Glad you were able to figure it out. You should be using POST rather than GET for that request, though. But as you're probably aware of now, the third parameter to each of the API SDK methods (get/post/put/delete) is $args: an array containing each of the methods' arguments, as described in the docs.

I see, if you can add anything with a timezone and assign to staff that would be good but probably for the project manager? anyway +1 now cause of your post

correct, emails that you could read and then forget about, mean to do later, accidentally delete, etc. This way...it adds everything to a single spot. Could even expand a bit to add custom tasks (follow up with new clients in x days). A to-do list system would be awesome.

I think he explained it pretty well, he's requesting a to-do list plugin that creates a to-do list based on things that happen in Blesta. If an error happens, it automatically adds a review task to the to-do list. If someone places and order that requires review, automatically add that to the to-do list, etc.

Still for sale, please feel free to send offers.

in my opinion if we check required + read only . if the field is read only & required and is empty (no value) , the input should be editable , that mean that the user can fill the field in registration or in the client area ( a notice that the data can't be changed after by the client himself) , if the field is filled then the input should be disabled . that sceanarion is the best approuch .

Yes, I know, but dosent make sence The "read only" only has to work on Client Area and not wen a client is registering How the hell we can make a field "read only" + "required" lol How it is done right now we cannot ever, never, enable the "read only" + "required" or the client cannot finish the process There is 3 kinds of "bugs" in my view 1º- Bugs that cause errors 2º- Bugs that dosent work the way it should work 3º- Bugs that dosent make sense the way it works This "Bug" goes into the 2º and 3º category "Sugesttions", is for me, new functionality that isnt alredy implementd, in this case dosent fit here because the functionality alredy exists P.S- Only my opinion

Manually linking? But first make sure you have setup your Module well, thus you can successfully create accounts to the servers, Then, just go to client profile > add service > Remove the tick from "Provision using the cPanel module" . And fill in the domain name and username same as from the server. Thats It's. Blesta will automatically check for an existing account in the server with the same information. Hope that helps, By the way I think the post is in the wrong category. Should be in support

+1 nice idea, so for instance we could explain what a configuration option is for, what it does, and/or how to configure for that option.

I want private link only special customer can see but it will not listed on group WHM** has hidden option like this.

The plugin Has been update to v2.0.0 , compatible with v3.3.X . + added option to select between two css style, screenshoot has ben added to the first post . enjoy the free content

nice! what id really like to see is support for the email reselling side of things. once you get past 50 domains hosted, it gets a bit fun to keep it all straight. i do think a email module will be my focus after migration from HostBill.