Questions, weird behavior, cool things

Hey David!

As my project continues, we’re encountering things! Some problems/questions:

• The autoresponder isn’t always working. It works most of the time for Office-based emails, but a gmail account is never receiving responses. We’ve tried to figure out what the cause is, but it’s been hard to pinpoint.
• Is there some way to declare that a checkbox is checked, or which element of a dropdown is currently selected, from the field object passed by render_get_field_slug-{slug}? I couldn’t find a way to do it, so I ended up adding “selected” keys to $field[‘config’][‘options’] and editing the core field.php files for dropdowns and checkboxes to trigger “selected” if the key exists. It’s not a great fix because the changes will be removed whenever you update – am I missing something?
• Along the same lines, it seems like auto-populated fields don’t have their [‘options’] set until after render_get_form is done. I’ve edited pods-caldera-forms to pre-load a lot of fields for user updating, but haven’t been able to pre-select auto-populated fields from inside render_get_form. I did try calling Caldera_Forms::auto_populate_options(), which returned the correct $field object, but my changes were overwritten. I’m assuming this is because the core calls auto_populate_options() later. render_get_field_slug does what I need, but since I’m calling pods to get data, I’d rather not make a bunch of get_field_slug filters and make the runtime suffer more. Is this intentional?
• As per the other support post about Pods WHERE, I did make a Filterable Pods field. I looked around for a way make it switchable behavior like Auto-Populate, but from the look of it, it’s deeply embedded in the core, and not easily extended. Or is there a filter I missed that might accomplish this?
• For two of the fields we made for our project, we’re depending on .change() handlers to watch bound fields and set outputs. But when “show if {field} is {value}” conditionals are applied to these fields, not all of the .change() handlers are applied when the fields render. Any ideas or debugging advice?

And as for the cool things, we made a bunch of fields/processors that you might be able to use! Filterable Pods is one, but we also have a FullCalendar.io field and 4-5 processors for working with the Google Calendar PHP API. I’ve also added field pre-loading and pod editing on submit to the Pods-CF plugin. Most of these are still in-progress and some are project-specific, but we’re hoping to generalize them after the semester’s over. ??

https://github.com/thely/wtsscheduling/tree/master/wp-content/plugins

https://www.ads-software.com/plugins/caldera-forms/