Advanced Custom Fields

Admin pages with a lot of WYSIWYG fields can be significantly slow to load. That's why there is the option "Delay Initialization", that waits for the editor to be initialized as soon as the user clicks it. The related JS is from the days before IntersectionObserver was born – but it could now definitely be improved so that TinyMCE will be initialized as soon as the field enters the viewport. Here's a little function I wrote that does exactly that: /** * Attaches an intersection observer to delayed WYSIWYG fields * to enable them automatically if scrolled into view * * Uses the `ready_field` and field.addAction('load') actions * @see https://www.advancedcustomfields.com/resources/javascript-api/#actions-ready_field * @see https://www.advancedcustomfields.com/resources/javascript-api/#actions-load_field */ handleACFWysiwygField = () => { /** * Is the field delayed? */ const isDelayed = (field) => { return field.$control().hasClass("delay"); }; /** * This function will be injected into the ACF field object. * So `this` will be the field */ function observe() { if (!isDelayed(this)) { return; } const field = this; const $wrap = field.$control(); const observer = new IntersectionObserver( (entries) => { if (entries[0].isIntersecting) { $wrap.trigger("mousedown"); observer.disconnect(); } }, { rootMargin: "300px 0px", } ); observer.observe($wrap[0]); } /** * As soon as the field is ready, prepare it * for observation */ function onReady(field) { if (!isDelayed(field)) { return; } field .$control() .find(".acf-editor-toolbar") .text("Initializing Editor ..."); field.observe = observe.bind(field); field.addAction("load", field.observe); } acf?.addAction("ready_field/type=wysiwyg", onReady); }; The function does the following things: wait for any wysiwyg field to be ready if the field is delayed wait for the field to be fully loaded ( field.addAction('load') ) patches the field with an "observe" function, that observes it and initializes the editor as soon as the field becomes within 400px of the viewport As this all can already be done using the JS API, I thought it would be worth sharing it publicly. But if the ACF support is reading this, maybe they'd consider adding the functionality to the core?

I can' t write in ACF label field (like text) when i creating field group . It's just stucked while i click that particular label field. None of the action could be done. when i dublicate field once the text arrow automatically go to ACF label field . Kindly cross-check and rectify please.

It would be better if ACF had a feature to allow users to upload their own posts via the frontend.

We need an extra 'add field' button. It would sit on all fields and would add a new field just below the field it was created from. This would help eliminate the annoying drag and drop that we need to do when adding new fields up top. Please see example screenshot.

Add a new field type of Phone Number - pairs well with the email field. When you're asking for one, you're probably asking for both. Give options to choose how that phone number is validated (allow countries, default country, preferred countries) And allow various return formats (full number, country, number without country code, etc) JS validation: https://intl-tel-input.com/

Please consider adding support for object caching. This will speed up the admin editing experience.

Currently listed in known issues is the limitation that fields inside groups dont support bidirectional relationships. We use groups sometimes and would be glad if this is supported. https://www.advancedcustomfields.com/resources/bidirectional-relationships/#known-issues Thanks

Currently there is a hook that is invoked when a new group settings tab is added to the meta boxes at the bottom of the ACF Field Group Editor. I'd like to propose that this hook be invoked for not just new tabs, but existing tabs as well including location_rules , presentation , and group_settings . This should be a simple enough change by duplicating this line ( https://github.com/AdvancedCustomFields/acf/blob/master/includes/admin/views/acf-field-group/options.php#L275 ) to each case or adding two new pre/post hooks such as acf/field_group/pre_render_group_settings_tab/<tab_key> and acf/field_group/post_render_group_settings_tab/<tab_key> . Why? I would like to extend the Presentation settings tab to include custom presentation fields/info rather than creating another presentation section using the existing acf/field_group/render_group_settings_tab/<tab_key> hook which can lead to confusion when navigating the admin field editor. Thanks!

Allow users to toggle enable/disable markdown formatting in the Text Area fields.

1] Show a field using conditional logic from a taxonomy field term text. So for example Show an image field if the taxonomy field has the term/text value of "photos". 2] Set a default term(s) to show terms automatically, to save from picking them in some cases where they might be regularly shown.