They don’t in either case. That was actually my first troubleshooting try followed by attempting to move it to the Side. I’ll get a support ticket out.
I am using the core block editor/gutenberg in WP 5.2 (I’d have to be with using ACF Blocks, but I’m not using the bleeding edge Gutenberg plugin).
These are the WordPress theming concept of a Page Template.
This doesn’t happen with all Field Groups applied to a certain Page (for instance I have a field group applied to the Home page and it works as expected). Furthermore, this Field Group displayed in the editor as expected up until the full 5.8 release (or it might’ve been the last RC).
You could do this without ACF using the Description field that’s built in.
BUT, if you really want to use ACF I think the issue is your if ($icon) — it should be if ($menu_navbar_sottotitolo) because that’s the variable you set in the line above.
Well, deleted the page and created a new one, it works. I don’t get it.
I’ve been getting responses between 12 and 24 hours via the email support. I wonder if your ticket got lost in the shuffle?
It seems to be a problem with a specific page (maybe?) because other repeaters are saving fine.
Did anyone submit a pull request or issue on the Git repo? Not even sure that’s how Elliot’s handling these things anymore.
Elliot – just wanted to say thanks for the fix in 4.3.6, works perfectly for me now.
Confirmed in 3.9 RC 1 with WYSIWYG in flexible content fields. Getting errors from the new version of TinyMCE, it looks like.
I know it’s been a while for the rest of the commenters on this thread, but I found a way (maybe a little hacky) to do this. In my theme functions.php file I added:
add_filter( 'tiny_mce_before_init', 'override_mp6_tinymce_styles' );
function override_mp6_tinymce_styles( $mce_init ) {
// make sure we don't override other custom <code>content_css</code> files
$content_css = get_stylesheet_directory_uri() . '/bd-editor.css';
if ( isset( $mce_init[ 'content_css' ] ) )
$content_css .= ',' . $mce_init[ 'content_css' ];
$mce_init[ 'content_css' ] = $content_css;
return $mce_init;
}
mp6 styling was getting in the way, so I hooked into the tiny_mce_before_init filter to force my editor styles to load anyway. Hope this helps someone.
Would also love to see this — clients often ask for editor styles to match their display styles.
I haven’t had a chance to test it yet (noisy clients). But Ciceron seems like a pretty smart guy. I’d go with his assessment. 🙂
@ciceron Hah, I did the same thing trying to fix it 🙂
I have this same issue on a client site. Completely broke a feature I built for them months ago that relied on the relationship field returning a post object.
Just rolled back to 4.2.0 and everything works fine again.
