Front-end edit form - Publish down date disabled

Hi,

May be i'm missing something in configuration but :

When i create a content in frent-end the publish up and publish down dates fields are disabled.
When i edit the new created content, fields are enabled.

I have try lots of things but i'm unable to define the publish down date in the creation form.

Regards

Hello

you probably allowed
edit.state (publish privilege) only in specific categories

and during initial creationthe code see no edit.state (publish privilege) thus the fields are disabled

probably the above behaviour is not best

- instead we should treat publish up / down fields like the state field
(i mean its behaviour when not using publish override and it is visible)

that is

1. we can allow the fields to be edited
2.and after submit, if no edit.state (publish privilege) in the selected category then clear them if needed

Hi Georgios,

Yes you are right, user as only rigth to publish in some category.

It would be great if he can choose the end publication date in item creation...

Do i need to create an issue on github?

The behavior you describe here :

1. we can allow the fields to be edited
2.and after submit, if no edit.state (publish privilege) in the selected category then clear them if needed

seems to be relevant.

Regards

Hello

yes, please open a new issue in github

we need to force disabling / unfiltering these
- only when using instantiating JForm (via model's getForm()) for item saving
- but not when instatiatiating JForm (via model's getForm()) for displaying item edit form
or better just check and clear them inside the save task of the controller, like we check there the state and category changes

Hello

please ask about fix tomorrow evening, if you do not here from me sooner
probably it is small fix

Hello

this new version (you may use install via URL)
github.com/FLEXIcontent/flexicontent-cck...e/3.2.1.x-stable.zip

The fields publish_up , publish_down will be enabled during intial form submit

please note
- submit menu item override of these will take priority over user values
- during item creation if user has no privilege to set them , then they are not cleared, just the reviewer / approver should check these field too