Forum Replies Created
-
Posts
-
Having the same problem. I was thinking about integrating Gutenberg (at least to give it a shot) but it’s not working in combination with piklist.
Hello there (again),
besides the fact, that the values were not updated, there was another problem with the encoding. I’m from austria and we use umlauts. So i started investigating why the umlauts were not displayed correctly (only for the metabox shown above, not for other metaboxes that are in use which are showing umlauts correctly).
It turned out that the others used UTF-8 without BOM while this one was using UTF-8.
After i changed it to UTF-8 without BOM the umlauts were displayed correctly and also the changes were saved.
A bit of a surprise for me, but ok – it’s working now.
Ticket can be closed (@piklist team: the ability to close a ticket (at least for the creator) via a checkbox would make sense so you don’t have to read through and close it manually.)
best regards, Harald
Wordpres URL of plugin
https://wordpress.org/plugins/events-manager/
Plugin Website:
I now use
em_event_save_preinstead ofem_event_save_meta_pre(this one is executed much earlier).Everything now works as expected. Thx a lot Steve for your insight and sorry, should have tested it with a normal post first. The idea came to my mind a bit late.
Ok, i found a workaround.
There’s a hook that is called before the metadata is stored by events-manager: em_event_save_meta_pre
I just unset the recurrence_dates there.
– The problem occurs only for multiple entries (add_more)
– The solution is dirty: adding another repeating field will require adapting this method. As I’m not planning to do add a lot of fields, the solution is ok for me.add_action('em_event_save_meta_pre', 'agram_em_event_save_meta_pre'); function agram_em_event_save_meta_pre($event) { unset( $event->event_attributes['recurrence_dates'] ); }Entries in the db look now like this
'270242', '19633', 'recurrence_dates', 'Aug 16, 2015' '270243', '19633', 'recurrence_dates', 'Aug 17, 2015'I think i found the cause of the problem. Just tested with a plain text field – same problem.
As i’m pretty sure this would cause a lot of support tickets and be probably fixed already there must be another problem.
I’m using events-manager, so i’m pretty sure it’s events manager in combination with piklist that causes the problems.
I’m investigating further and will a short answer if i find a solution.
Seeing it form piklist point of view: ticket can be closed.
thx for your effort. great framework, thumbs up!
Hello Steve,
thx for the quick reply.
I saw already that the data is actually correctly stored (but also duplicated n times where n entries exists)
But the admin area is not usable like this.
See the file: before_saving.jpg (This is how i enter the data, in this case dates from 1st to 3rd of august.
See the file: after_saving.jpg (This is how it looks after i store the article)
The data stored in the db looks like this
270131 19610 recurrence_dates a:3:{i:0;s:11:"Aug 1, 2015";i:1;s:11:"Aug 2, 2015";i:2;s:11:"Aug 3, 2015";}
270132 19610 recurrence_dates a:3:{i:0;s:11:"Aug 1, 2015";i:1;s:11:"Aug 2, 2015";i:2;s:11:"Aug 3, 2015";}
270133 19610 recurrence_dates a:3:{i:0;s:11:"Aug 1, 2015";i:1;s:11:"Aug 2, 2015";i:2;s:11:"Aug 3, 2015";}
It seems it always shows the last entry.
So it’s not really usable this way. Am i doing something wrong?
