Jcomments select field

Hi,

A good thing would be to make a select input to allow frontend users to enable or not comments for an item.

Through basic parameters, they can modify "create pathway automatically" and select a comment system.


Thank you

You mean it is wrong to allow user to select the comment SYSTEM, they should just select :
enable or disable comments, right?

if, you mean this, then yes it is wrong to expose such detail to the frontend user.

Yes.

Normal user (with author access to submit content) must have only the choice between On and Off.

I tried to make a select input and integrate jcomment tag but no success.

I am thinking that some other parameter should not be shown to frontend,

so maybe, selecting individual parameters to show would be more preferable than selecting groups of parameters to show in the frontend (this is a new feature)

e.g. the create pathway automatically is a parameter that should not be shown in the frontend

and yes, the parameter allow/disallow comments, is an important one and we must not allow to select commenting system ... (in 95% of the cases).

Any other parameters you would think should simplified in the frontend?

maybe remove the sliders too? I am thinking of this because we are to release final version, and easy of use in frontend is important.

ggppdk wrote: so maybe, selecting individual parameters to show would be more preferable than selecting groups of parameters to show in the frontend (this is a new feature)

Yes, it should be better. Another field should be voting.

edit :
after that, I don't see something else that should be added.

For voting you could do this yourself

Create a FLEXIcontent radio field
- with name allow_votes,
- with Label "Allow Voting"
- with values "No" "Yes"

then add this field into the "render only position" of your template

and do something like this in your customized item.php template file:

Also another approach would be what blog template does ...
It has parameters for showing fields.

Instead of adding to a template position with drag and drop, the xml (item/category layout) of the template have parameters for choosing which fields to show ...

So you could duplicate blog template,
and a few more parameters for fields of your choose and then allow template configuration to the frontend form.

This way the frontend user will be able to select what he wants to be show.

REMEMBER to remove template parameters for obligatory fields, e.g item title, since these will always be shown.

Regards

ggppdk wrote: I am thinking that some other parameter should not be shown to frontend,

so maybe, selecting individual parameters to show would be more preferable than selecting groups of parameters to show in the frontend (this is a new feature)

e.g. the create pathway automatically is a parameter that should not be shown in the frontend

and yes, the parameter allow/disallow comments, is an important one and we must not allow to select commenting system ... (in 95% of the cases).

Any other parameters you would think should simplified in the frontend?

maybe remove the sliders too? I am thinking of this because we are to release final version, and easy of use in frontend is important.

I come back with my request about comments system.
Just to allow author to choose Yes / No for comments.

This has been added in latest version for frontend content edit form