Forum Replies Created
-
Posts
-
I’m also experiencing this error.
WP 3.8.2 or 3.9
TEC 3.5.1Theme: Roots (http://roots.io/) specifically on the single-event view
That does work if I directly link to that URL / format. But once there, if I use the View As drop-down on menu bar to switch between views, it does not maintain the &tribe_event_display=past parameter.
Re-phrasing that as a question:
If I start out at http://yoursite.com/events/photo/?action=tribe_photo&tribe_paged=1&tribe_event_display=past how can I ensure that use of the view as menu bar options keeps the user viewing past events?Thank you so much for the sample. It did resolve my issue and (thankfully) my form is one that doesn’t require a datepicker on the front-end so including the action in default-template.php prior to the acf_form_head call keeps the scope down to where the error was. I’ll note this ticket back to the cross-post thread on their forum.
Unfortunately this one is both still only in dev on VM and when launched will be behind a VPN. However, I can give a set of simple instructions that will allow you to replicate in your own test environment along with the templates above. FYI – The field group snippet below was generated via the export feature of ACF. The issue appears to apply to all ACF front-end forms that attempt to display within an event screen.
1) Download and activate ACF: http://wordpress.org/plugins/advanced-custom-fields/
2) Add the following to your theme functions.php file which will generate a new ACF meta form on your posts.
if(function_exists("register_field_group")) { register_field_group(array ( 'id' => 'acf_gallery-details', 'title' => 'Gallery Details', 'fields' => array ( array ( 'key' => 'field_52e306d127d7a', 'label' => 'Event', 'name' => 'galleryEvent', 'type' => 'text', 'required' => 1, 'default_value' => '', 'placeholder' => '', 'prepend' => '', 'append' => '', 'formatting' => 'html', 'maxlength' => '', ), array ( 'key' => 'field_52e93fe1b5329', 'label' => 'Photographer Name', 'name' => 'galleryName', 'type' => 'text', 'required' => 1, 'default_value' => '', 'placeholder' => '', 'prepend' => '', 'append' => '', 'formatting' => 'html', 'maxlength' => '', ), array ( 'key' => 'field_52e93ffcb532a', 'label' => 'Photographer Email', 'name' => 'galleryEmail', 'type' => 'email', 'required' => 1, 'default_value' => '', 'placeholder' => '', 'prepend' => '', 'append' => '', ), array ( 'key' => 'field_52ebde7123116', 'label' => 'Photos', 'name' => 'galleryPhotos', 'type' => 'image', 'required' => 1, 'save_format' => 'object', 'preview_size' => 'thumbnail', 'library' => 'all', ), ), 'location' => array ( array ( array ( 'param' => 'post_type', 'operator' => '==', 'value' => 'post', 'order_no' => 0, 'group_no' => 0, ), ), ), 'options' => array ( 'position' => 'normal', 'layout' => 'no_box', 'hide_on_screen' => array ( ), ), 'menu_order' => 0, )); }3) Go to Custom Fields window – /wp-admin/edit.php?post_type=acf – and note the ID for field group titled Gallery Details.
4) Replace the array value (252) in the two page template files of my previous update with the ID noted in step 3.
5) Create a new page that uses the template and note that the ACF front-end form loads successfully with no issues.
6) Create an event and view on front-end of site with the default-template.php from your theme. Note that ACF has JS conflict errors related to Tri.be.
7) Debug
8) ????
9) ProfitThanks
JamieFor anyone else trying to solve the first challenge – having hidden additional fields for Community Events – the following JS is all you need along with the ID of the field:
‘jQuery(‘#event-meta.eventtable input[name=”_ecp_custom_1″]’).parents(‘tr’).eq(0).hide();’
At least if being hidden visually is all you need.
Hi Casey,
I figured that would be the case for #1 and will follow-up with submission towards that.
For #2 – the issue isn’t specific to GF it’s a general WP development one. How would I add / update one of the additional field values?
If it were a standard post / custom field I would expect to be able to use the WP function add_post_meta with the meta key above.
The scenario I was intending it was that each event has a custom field identifying genre or topics that a particular presentation would cover, but it could just as easily apply for any of the following:
-Event would include / require projector or specific equipment: pick list
-Event is being recorded yes / no
-What software / version other meta is being discussed.In all of those cases, having a method to view all events that are particular to that data scenario would be useful. If I think about it in comparison to the WP 3.1+ implementation of custom post types, having the option within the /events/ template of creating an archive-[customfield] and single-[customfield] which returns the results of any events which have that custom field selected….The filter / sort around particular data for the field is quite manageable from there.
I’ve since found an alternate approach that my particular need for it in the short term isn’t required, but would be a good feature to consider in the “events calendar can scale displays as big as the meta data you can dream about” perspective.
I’d recommend a future enhancement to tribe_meta_event_cats so that passing null for the $label value (or another parameter option) that can specifically strip all the dt / dd wrappers. I’m using that function in a table returning all the results and already have column titles that do the same effect.
Christina: Was just putting out what info I could find in hopes it might help someone else figure a full solution.
I’m now at the same point you are – stores organizer info perfect, but venue only stores permalink with venue name, not the venue post title.
I did manage to setup dynamic drop-down lists for venues / organizers which you can select from previously created ones that works via the following:
-Create a standard dropdown field. In the advanced tab specify populate dynamically with field title VenueSelect (or OrganizerSelect for that)
-Paste the code from http://pastebin.com/t3W0ntgz into your functions.php making sure to replace the _6 in gform_pre_render_6 with whatever the ID for your form is.
-In the gform_pre_submission function where you do the format_event_date function, you’ll need to check that field to store venueID / organizerID or not as this example does: http://pastebin.com/Nyj08q1h
My temporary work-around is since events are posted to draft and GF stores the populated data, when an event is posted for a new venue I manually create the venue and associate to the event. Hoping either a solution for this or the community events comes out soon though.
Additional support would be helpful. tribe_is_event() confirms that I’m on an event single view, but not which event category is involved. Need to be able to pull that info to a variable or conditional like is_category(‘text’) and in_category(‘text’) allows on the post / post category view.
The recent updates to GF 1.6 and the Custom Post Type plugin for GF has made this integration quite easy for the first scenario.
Create a standard drop-down with dynamic population parameter name ‘EventVenueID’ and specify Populate with a Post Type of ‘Venues’. Setting the default entry to something like ‘–select venue–‘.
The first half of that might be a lot easier than that now….
The Gravity Forms + Custom Post Types add-on (http://themergency.com/plugins/gravity-forms-custom-post-types/) offers ability to put both taxonomy or post type entries into standard drop-down fields.Still can’t seem to make it quite work, but that might help the process for someone else.
Went looking into the DB to see what I could see.
-Venues are stored as a custom post type (tribe_venue)
-Venue details are stored as post meta (custom fields) on tribe_venue
-Venue ID is post meta (custom field) on event post type (tribe_events)
-Similar approach for Organizer (tribe_organizer)Seeing this approach makes me more inclined to wait for the community events add-on, but if I were to take a stab at implementing something specific to GF with TEC 2.0 I might:
-Use a standard drop-down field for Venue ID
-Populate it with hook on gform_validation that pulls all posts with type tribe_venue storing the ID as value and name (post title) in display
-Augment the save_tec_event_meta_from_gravity function Brian wrote to get it into $_POST format expected.My immediate use cases for GF / TEC integration don’t go farther than that, but if you wanted to add a drop-down option to ‘add new venue’ via the front-end:
-During save event with add new venue selected….
-Create a post (venue) with the venue info as post meta data and retrieve the post ID
-Store that as the venue ID in place of the drop-down value for ‘Add New Venue’ option before letting the function described above occur.I just finished doing a rideshare board plugin that used GF for front-end submission (http://wordpress.org/extend/plugins/idealien-rideshare/) with custom post type + taxonomies for the data storage which was comparable, but much easier by being able to just do wp_insert_term for any new elements.
Out of curiosity – did extending terms (something like http://wordpress.org/extend/plugins/taxonomy-metadata/) ever come up as a potential vector rather than venue / organizer being post types?
