I am having the same issue, but after upgradingd to free 4.3.9. I was able to repeat the bug on two separate instances by simply upgrading. The duplicated fields were not savable.
I did found the duplicated groups under Field Groups admin, and deleting the latter seemingly solved the issue.
Works just perfectly now. Thanks for the help.
(btw – I don’t remember if I marked my own answer as the solution, I just used the checkbox above the submit. How can I undo this?)
Just one more thing, I noticed an odd behaviour when I updated the previous posts manually. Sometimes the content totally disappeared from the page (while still there in the admin). When trying to restore it from the revisions, it seemed like a few minutes after my manual update there was one more, totally blank save. Strange enough…
Edit: I had to take out the apostrophes… Everything works fine now.
$new_content .= 'blah'. $fields[field_51bde56567f28] . 'blah';
Many thanks!
Thanks, almost there, the blahs appeared in the_content. I am not sure what I have to replace in the code, when using my real ACF field names, they do not show.
$new_content .= 'blah'. $fields['what'] . 'blah';
I use several smaller texts surrounded with formatted code – it’s like using forms in the admin. The original text input area remains empty, I changed the content-post.php, which looks good, but breaks some wp functionality, like excerpt generation, rss texts, etc. I guess the proper way should be using a function or filter to replace the_content or post_content.
I made something like this – still not the right code.
function new_filter_content($content) {
if( is_single() && is_main_query() ) {
if(get_field('what')) {$new_content .= 'blah' . get_field('what') . 'blah';}
if(get_field('where')) {$new_content .= 'blah' . get_field('where') . 'blah';}
$content = $new_content;}
return $content;}
add_filter('the_content', 'new_filter_content');
I guess I have a similar issue, Jetpack shortcodes (http://jetpack.me/support/shortcode-embeds/) do not render in ACF fields, wysiwyg or text. Is there any workaround?
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.