Using ACF Repeater to Access Event Calendar Serialized Meta

• Menzer69

• March 30, 2019 at 2:54 am

Hi guys, I want a bit more control over some custom fields used in Events Calendar, it’s for their Ticket fieldset, but I am finding it hard to access the data because it is serialized repeater, I was thinking about accessing the fields using acf repeater (if that is possible) but I am concerned how I would add more rows and save the data to the correct format below, I saw another post regarding repeater fields and tried it but I think this is a little different and I couldnt get it working,any idea would be grateful thanks

a:16:{i:0;a:5:{s:4:”type”;s:4:”text”;s:8:”required”;s:0:””;s:5:”label”;s:20:”Full Name of Guest 1″;s:4:”slug”;s:20:”full-name-of-guest-1″;s:5:”extra”;a:0:{}}i:1;a:5:{s:4:”type”;s:6:”select”;s:8:”required”;s:0:””;s:5:”label”;s:9:”T-Shirt 1″;s:4:”slug”;s:9:”t-shirt-1″;s:5:”extra”;a:1:{s:7:”options”;a:6:{i:0;s:5:”Small”;i:1;s:6:”Medium”;i:2;s:5:”Large”;i:3;s:2:”XL”;i:4;s:3:”XXL”;i:5;s:4:”XXXL”;}}}i:2;a:5:{s:4:”type”;s:4:”text”;s:8:”required”;s:0:””;s:5:”label”;s:16:”FLIGHT OUT No. 1″;s:4:”slug”;s:15:”flight-out-no-1″;s:5:”extra”;a:0:{}}i:3;a:5:{s:4:”type”;s:4:”date”;s:8:”required”;s:0:””;s:5:”label”;s:14:”Arrival Date 1″;s:4:”slug”;s:14:”arrival-date-1″;s:5:”extra”;a:0:{}}i:4;a:5:{s:4:”type”;s:4:”time”;s:8:”required”;s:0:””;s:5:”label”;s:14:”Arrival Time 1″;s:4:”slug”;s:14:”arrival-time-1″;s:5:”extra”;a:0:{}}i:5;a:5:{s:4:”type”;s:4:”text”;s:8:”required”;s:0:””;s:5:”label”;s:15:”FLIGHT IN No. 1″;s:4:”slug”;s:14:”flight-in-no-1″;s:5:”extra”;a:0:{}}i:6;a:5:{s:4:”type”;s:4:”date”;s:8:”required”;s:0:””;s:5:”label”;s:16:”Departure Date 1″;s:4:”slug”;s:16:”departure-date-1″;s:5:”extra”;a:0:{}}i:7;a:5:{s:4:”type”;s:4:”time”;s:8:”required”;s:0:””;s:5:”label”;s:16:”Departure Time 1″;s:4:”slug”;s:16:”departure-time-1″;s:5:”extra”;a:0:{}}i:8;a:5:{s:4:”type”;s:4:”text”;s:8:”required”;s:0:””;s:5:”label”;s:20:”Full Name of Guest 2″;s:4:”slug”;s:20:”full-name-of-guest-2″;s:5:”extra”;a:0:{}}i:9;a:5:{s:4:”type”;s:6:”select”;s:8:”required”;s:0:””;s:5:”label”;s:9:”T-Shirt 2″;s:4:”slug”;s:9:”t-shirt-2″;s:5:”extra”;a:1:{s:7:”options”;a:6:{i:0;s:5:”Small”;i:1;s:6:”Medium”;i:2;s:5:”Large”;i:3;s:2:”XL”;i:4;s:3:”XXL”;i:5;s:4:”XXXL”;}}}i:10;a:5:{s:4:”type”;s:4:”text”;s:8:”required”;s:0:””;s:5:”label”;s:17:”FLIGHT OUT No. 2 “;s:4:”slug”;s:15:”flight-out-no-2″;s:5:”extra”;a:0:{}}i:11;a:5:{s:4:”type”;s:4:”date”;s:8:”required”;s:0:””;s:5:”label”;s:14:”Arrival Date 2″;s:4:”slug”;s:14:”arrival-date-2″;s:5:”extra”;a:0:{}}i:12;a:5:{s:4:”type”;s:4:”time”;s:8:”required”;s:0:””;s:5:”label”;s:14:”Arrival Time 2″;s:4:”slug”;s:14:”arrival-time-2″;s:5:”extra”;a:0:{}}i:13;a:5:{s:4:”type”;s:4:”text”;s:8:”required”;s:0:””;s:5:”label”;s:15:”FLIGHT IN No. 2″;s:4:”slug”;s:14:”flight-in-no-2″;s:5:”extra”;a:0:{}}i:14;a:5:{s:4:”type”;s:4:”date”;s:8:”required”;s:0:””;s:5:”label”;s:16:”Departure Date 2″;s:4:”slug”;s:16:”departure-date-2″;s:5:”extra”;a:0:{}}i:15;a:5:{s:4:”type”;s:4:”time”;s:8:”required”;s:0:””;s:5:”label”;s:16:”Departure Time 2″;s:4:”slug”;s:16:”departure-time-2″;s:5:”extra”;a:0:{}}}

• John Huebner

• March 30, 2019 at 4:07 am

This does not appear to be an array of the data created but array that defines the fields that have been created. In many ways it looks just like a set of fields for an ACF field group.

Could you access the information stored by the other plugin with ACF fields? Possibly. But how would depend on how the data is stored and not the field definition you posted. More than likely, yes, but it probably would not be easy.

• Menzer69

• March 30, 2019 at 7:19 am

This reply has been marked as private.

• John Huebner

• April 2, 2019 at 11:08 pm

Basically, what you have to do is build an acf/load_value filter for every field that you create, and get the data from the other plugin data. On the reverse side you need to create an acf/save_post filter, get the values from the acf fields and then update the values used by the other plugin. Different types of ACF fields will require different approaches and I wouldn’t begin to understand how the events plugin stores information.