Brandon Kraft

Are there any error messages on the screen, in your browser’s console, or in your site’s error log that occurs when the crash happens? I don’t have a copy of Divi at the moment to attempt to test it, but curious if there are any errors that can direct me to where things may be amiss.

Thanks!

Could you share some more details about what you’re seeing?

I tried setting up a new field group associated with the Posts post type with those three fields. On a new post in the block editor, using the meta fields at the bottom of the page, I’m able to use all three fields. Saving the post and reloading the editor retains the values.

I’m curious if you’re setup in a different way that would help me figure out what’s happening for you. While I don’t immediately recall anything in beta 7 that would be impacting this, can you try after updating to today’s beta 7?

I’m having trouble duplicating this.

Here’s what I’m doing:

• New field group that is set to display with the Post post type.
• Image field with image field output, setting field name to image_field
• On a post, adding an image via the media selector.
• Via PHP, set to output var_dump(get_field('image_field')); within the loop on a post.
• View the page.

Doing that, I’m seeing the image field’s array dumped to the browser.

Is there something different that you’re doing that might help me figure out what’s happening for you and/or could you share how you’re setting things up?

While I don’t think anything that’s changed in beta 7 since beta 6 would impact it, please update to beta 7 just to be sure.

Thank you!

Thanks for the report. I’m investigating.

This should not be resolved in beta7 released today! Thank you!

Howdy!

This requires custom code at this time. If you’re not familiar with adding custom code, you can use a plugin like https://www.ads-software.com/plugins/code-snippets/ to add it.

You’d want to add this as a snippet that would be something like this. The default—and what you are running into–is it’ll allow years to be picked 100 years before or after the current year. The script below would change it to 1000 years before or after. You can change it to be more suitable to your needs.

/**
 * Modifies the ACF date picker year range.
 *
 * @return void
 */
function scf_orgsupport_modify_acf_date_picker_year_range() {
    // Only load if plugin is active.
    if ( ! class_exists( 'ACF' ) ) {
        return;
    }

    // Register and enqueue our custom script.
    wp_register_script(
        'scf_orgsupport_modify_acf_date_picker_year_range',
        null,
        array( 'acf-input' ),
        null,
        true
    );

    // Add inline script.
    wp_add_inline_script(
        'scf_orgsupport_modify_acf_date_picker_year_range',
        '
        acf.addFilter( "date_picker_args", function( args ) {
            args.yearRange = "c-1000:c+1000";
            return args;
        });
        '
    );

    // Enqueue the script.
    wp_enqueue_script( 'scf_orgsupport_modify_acf_date_picker_year_range' );
}
add_action( 'wp_enqueue_scripts', 'scf_orgsupport_modify_acf_date_picker_year_range' );
add_action( 'admin_enqueue_scripts', 'scf_orgsupport_modify_acf_date_picker_year_range' );

Beta 6 should resolve the issue; thanks for flagging it and apologies for the trouble!

Thanks for flagging. Can you check out beta 6 to confirm it resolves what you’re seeing?

Thanks for the information. I believe this should now be fixed, notably with Russian being translated enough for www.ads-software.com to generate language packs. Can you upgrade to beta 5 and ensure your translation packs are up to date (on the same WordPress updates page) and let me know if you’re still having trouble?

I’m sending up beta 5 – can you check that out and see if it resolves it? If not, can you copy/paste the incorrect line and what it should be?

Can you give the development version a spin ( https://downloads.www.ads-software.com/plugin/secure-custom-fields.zip , also available from https://www.ads-software.com/plugins/secure-custom-fields/advanced/ ).

This works for me on Chrome and Firefox now. I’d like to confirm it fixes it up for you before pushing out a new beta version.

I see the issue. I’ll have it fixed up soon.

Are you still seeing the issue in latest Firefox @alx359 ?

Thanks for letting us know. Is this with any particular fields or other data types (e.g. taxonomies or post types, etc)?

There isn’t any, yet. It’ll be something I’m looking at getting rolling after the holidays.