Front end user posting options?
- This topic has 5 replies, 2 voices, and was last updated 9 years, 4 months ago by .
Viewing 5 reply threads
Viewing 5 reply threads
- You must be logged in to reply to this topic.
Home › Forums › GovIntranetters › Front end user posting options?
I would rather not have to have my staff learn two interfaces to use our intranet. I would very much like them to be able to post their own events, need to knows, how do I?s etc without having access to the admin dashboard.
Would anyone be able to point me in a direction why I may be able to find an easy solution or if I’ve missed something in the options maybe?
thanks in advance 🙂
If you have Gravity Forms, you can use the Custom Post Type plugin
Create your form and add it to a page – see example form
Is there anything different I need to do in order to make this work for Events?
When using Gravity Forms + Custom Fields, the only field populated is the End Time.
All the others following the same set up stay blank.
Is there something I’m missing off Luke?
You need to add fields to the form using the Post Fields panel and match up each of the custom fields. Also, set the post type in the Title field – see attached.
Every field is working except for the start date and end date fields.
The calendar looks different in yours to mine (I have no idea if that could do with anything). I’ve tried using a custom field text box to put in a date but that also comes back blank when posting the form.
My calendar on the front end looks like this:
I have them set up the same as my other custom fields:
I’m wondering if you are able to replicate and can offer advice?
EDIT: The start date is being picked up by the form and recorded as an entry with a value.
Cookie | Duration | Description |
---|---|---|
comment_author_email_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_url_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
wordpress_logged_in_[hash] | Indicates when you’re logged in, and who you are, for most interface use. | |
wp-settings-{time}-[UID] | This is used to customize your view of admin interface, and possibly also the main site interface. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | Used to distinguish users. |
_gat | 1 minute | Used to throttle request rate. |
_gid | 24 hours | Used to distinguish users. |