@mullibahr Hey! Could you check if custom fields are enabled in the screen options tab at the top of the page? It could just be they’ve been hidden by a user and aren’t visible. If the checkbox is there, could you drop us an email to our support address and we’ll look into this deeper. Thanks!
@webconnect This happens when due to a plugin loading a non-full version of select2 and overwriting ours – we’ve got a patch lined up to fix this in the next day or two.
@snook4tech Your error is likely a filter or hook being applied on post save. If you send us an email to support, we can take a quick look as see if we can help here.
@ivanremi We’ve got your support ticket and someone will get back to you shortly. You can find more information on the warning in your logs here: https://www.advancedcustomfields.com/resources/acf-field-functions/ – it’s not a fatal error, and shouldn’t be the cause of any memory issue; but it’s a heads up some code is executing incorrectly and should be fixed.
-
This reply was modified 2 years, 12 months ago by Liam Gladdy.