use custom fields filters for notifications

This support ticket is created 7 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	-
-	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	-

Supporter timezone: Europe/London (GMT+00:00)

Tagged: Content-submission forms, Toolset Forms

This topic contains 17 replies, has 2 voices.

Last updated by Nicholas 6 years, 12 months ago.

Assisted by: Nigel.

← 1 2

Author

Posts

November 28, 2017 at 12:52 pm #593977

Nicholas

Screen Shot 2017-11-28 at 1.46.49 PM.png

Hello Nigel.
Thank you.

Acutally in this case I have to avoid that the user can actually publish the post.
Right now it's possible to set the option to "--not set--". In case the user accidentally selects this option the post will be published. I need to avoid that by all means.

Do you know how I can get rid of the --- not set --- option? (see screenshot)

November 28, 2017 at 2:44 pm #594013

Nigel

Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Nicholas

The only way to get rid of no option is to specify a default option, e.g. to pre-select draft.

You can do that by editing the draft option of the generic field like so:

"default":["draft"],

Alternatively, for the post status set by the form when it submits, instead of publish you could try private, for example.

The final alternative would involve adding custom form validation to make sure an option was set without remove the nothing-selected option, but that obviously implies more work...

December 1, 2017 at 9:42 am #595017

Nicholas

Thank you very much for your help Nigel. This ticket is resolved.

← 1 2