This is really exciting!
![:cheer: :cheer:](/media/kunena/emoticons/cheerful.png)
Pardon the delay, had to renew my subscription and had some holiday distractions.
A few things I should highlight:
1. When saving a custom field without a title, it does not save and dumps all the data. I understand that a title is a required field, so what I'm suggesting is for the validator in the backend to check this before attempting to save. This will prevent users from doing a bunch of work only to have it removed. After putting in a title, saving worked of course but had to re-fill out the data.
2. Near the bottom of custom field options it says "When it's not checked the field validation is enabled and the user will not be able to submit a
hotspot unless he fills this field."
It should say "comment" instead of "hotspot". Also I suggest changing the "he" to "he/she", but that's up to you.
3. Will checkboxes be added? They are mentioned in text twice, but there is no field type for them.
4. Not sure we need to have it say "Custom fields" after posting the comment. The viewer should be able to figure out what the data means based on how the administrator constructs it. The reason I'm proposing the removal of the text is because it's a little more clutter to the nicely fashioned Ccomment form.
5. When viewing the list of custom fields in the backend, the titles should link to the edit page of the custom form. I know you can edit the custom field by clicking the checkbox and then clicking the edit button, but this isn't as friendly. Joomla articles in the backend for example allow you to click the title to edit the article.
I should send you an email soon regarding styling the custom forms. Overall I'm really excited about the direction of CComments.