@NabeelMolham@wp_acf@wpml As a walk-around I've limited my custom css to be generated only for default language, but still, the options page with empty fields for secondary languages seems a bit awkward.
Hey @wp_acf folks, another question. Is there a way to disable certain ACF Option Pages to be untranslatable with @wpml? I've got theme setting in the options page (color, fonts, etc.) and want to keep it the same across all languages. I'm googling for last 2h without success :-/
Hey @wpml how can I completely disable translation editors? I want to use #gutenberg and translate each page and post independently. Can't see any option to disable classic and advanced editor in the same time :-/
@jmslbam@wp_acf@BeaverBuilder Well, with ACF you could set your own layout for each block, ie placing the textarea field in a separate tab. But yes, ability to resize the modal would be amazing.
@wp_acf@BeaverBuilder I'm really happy you like the idea. IMO modal + preview in Gutenberg would be a perfect mix for every type of custom block β€οΈβ€οΈ
@uniondesign@wp_acf Well, I had the same issue, and finally went for filtering blocks via js function. IMO removing reusables while filtering block is unwanted and unpractical Gutenberg behavior, and should be reported as an software error.
@wpcrafter Thanks for that video. I'm considering Brizy for my low-budget projects and it seems to fit just fine. I'll test it a little more, but right now I'm considering a lifetime option.
Today I discovered an awesome add-on for ACF, called Component Field. It's incredibly easy to use, and saves a lot of time.
Until now I've been using clone field for reusable fields, but with Component Field it's just so much more convinient
Check it out https://t.co/0hB2s4ljt9
@MaximeCulea I think think that with ACF blocks it should not be an issue, as each block is loaded separately in the editor. And actually after applying component field my total queries to DB went down. But it might be just me shit-codding ;-)