Forum Replies Created
-
Posts
-
It’s creating the notice fine, but since the Piklist admin styles load in the footer after the WP styles, it doesn’t pick up the green left border from the .updated class.
The main one I noticed was the different types of admin messages. I’ve attached a couple screenshots showing what’s happening.
Ah, I see that now. I hadn’t tried dragging the entire meta box. Here’s a quick fix that adds that condition in as well:
.on('sortstart', '.meta-box-sortables.ui-sortable, .piklist-field.ui-sortable', function(event, ui).on('sortstop sortreceive', '.meta-box-sortables.ui-sortable, .piklist-field.ui-sortable', function(event, ui)Looks like ZIPs don’t work either so I’ve posted the updated admin.js here: http://hereswhatidid.com/media/admin.js.zip
I’ve tracked it down to the admin.js file in Piklist. On lines 1052 and 1073 where you’re assigning the ‘sortstart’ and ‘sortstop sortreceive’ events, it’s not being specific enough and picks up the editors that are within ACF. A simple fix to make sure that those events are targeting the correct elements prevents the error from occurring and the sorting works as expected. I’ve attached my version of the admin.js file with this fix in place.
A little further investigation points to it being specifically related to any flexible content field layout that includes the WYSIWYG editor. Flexible content layouts that do not have any WYSIWYGs in them do not trigger the error.
Has there been any progress on this one? I’m using 0.9.9.7 and it’s doing the opposite for me. ACF flexible content fields drag and drop fine but the Piklist add_more items create the large amount of empty placeholders. It’s also throwing the following JS error:
“Uncaught TypeError: Cannot read property ‘onpageload’ of undefined”
