Forminator Editor Shows Blank White Page

  • fajarsusilowati83

    (@fajarsusilowati83)


    1 week, 2 days ago

    Hi Forminator Support,

    I am experiencing an issue where the Forminator form editor displays a completely blank white page whenever I try to edit a form.

    The forms themselves are still working on the front end and can also be previewed successfully. However, I cannot access the editor to make any changes.

    The issue affects all forms, including:

    • Existing published forms
    • Duplicated forms
    • A completely new Blank Form

    I have already carried out the following troubleshooting:

    • Tested in both Chrome and Safari
    • Cleared the browser cache
    • Tested using WordPress Health Check & Troubleshooting Mode
    • Enabled only Forminator while in Troubleshooting Mode
    • The blank editor issue still occurred even with the other plugins disabled
    • Created a completely new Blank Form, but its editor also opens as a blank white page
    • Checked the Network tab and form-scripts.js?ver=1.57.3 loads successfully with HTTP status 200

    The browser console shows the following JavaScript error:

    Uncaught TypeError: Cannot read properties of undefined (reading 'transition')

    The error appears to originate from form-scripts.js.

    My current environment is:

    • WordPress: 7.1.2
    • Forminator: 1.57.3 (Free)
    • PHP: 8.4.26
    • Web server: nginx
    • PHP memory limit: 512 MB
    • Hosting: WordPress.com Premium

    I had also recently used TranslatePress to translate some front-end form content. However, the problem persists in Troubleshooting Mode when TranslatePress and the other plugins are disabled. A newly created blank Forminator form is also affected.

    Since the forms continue to work and preview correctly on the front end, but the editor fails even for a newly created blank form, could you please advise whether this could be an issue with the Forminator builder/editor or a compatibility issue with the current WordPress/PHP environment?

    I would prefer not to downgrade Forminator or make changes to the live forms because they are currently being used for a research assessment.

    Please let me know if you need the full console log, system information, or any additional diagnostic information.

    Thank you for your help.

    The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter fajarsusilowati83

    (@fajarsusilowati83)

    1 week, 2 days ago

    Hi Forminator Support,

    I would like to add some further troubleshooting information that may help identify the cause of the blank editor issue.

    1. The issue affects all Forminator content types

    I carried out further tests and found that the problem is not limited to my existing assessment forms.

    I can successfully create:

    • A completely new Blank Form
    • A new Quiz
    • A new Poll
    • Duplicated forms

    However, when I click Edit on any of them, the editor opens as a completely blank white page.

    This suggests that the issue affects the Forminator builder/editor generally rather than a specific form or corrupted form data.

    2. Front-end functionality still works

    My existing forms continue to display and work correctly on the front end. Preview also works successfully.

    I tested a submission and received the email notification containing the submitted responses and calculated scores. Therefore, the front-end form processing appears to be functioning.

    Interestingly, the Forminator dashboard still shows “Last Submission: Never” despite the successful test submission.

    3. JavaScript error in the browser console

    When opening any Forminator editor, Chrome DevTools shows the following error:

    Uncaught TypeError: Cannot read properties of undefined (reading 'transition')

    The error originates from:

    form-scripts.js?ver=1.57.3

    It appears multiple times while the Forminator editor is loading.

    The Network tab shows that form-scripts.js?ver=1.57.3 itself loads successfully with HTTP status 200, so the script appears to be downloaded but fails during execution.

    Immediately before the Forminator error, the console also displays this WordPress React 19 compatibility warning:

    [wordpress-react-19] Accessing __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED was removed in React 19 and is provided by a compatibility shim.

    I also checked the WordPress JavaScript environment. typeof wp returns "object" and wp.element is available.

    4. Plugin conflict testing

    I tested the site using Health Check & Troubleshooting Mode and enabled only Forminator for my troubleshooting session. The Forminator editor still displayed the blank white page.

    Therefore, disabling the other plugins, including TranslatePress, did not resolve the issue.

    5. Additional WordPress.com diagnostic information

    WordPress.com also reported a separate critical error associated with the WPCode Content Ratio v2.0 plugin. I have identified this as a separate plugin issue and can deactivate it. However, the Forminator editor problem also occurs during troubleshooting with only Forminator enabled.

    I also found a database deadlock in the logs involving the TranslatePress table wp_trp_machine_translation_locks. However, this appears to originate from TranslatePress machine translation rather than Forminator. The Forminator editor still fails when TranslatePress is disabled in Troubleshooting Mode.

    Current environment:

    • WordPress: 7.1.2
    • Forminator: 1.57.3 (Free)
    • PHP: 8.4.26
    • PHP memory limit: 512 MB
    • Web server: nginx
    • Hosting: WordPress.com Premium

    I have reproduced the issue in both Chrome and Safari and have cleared the browser cache.

    Based on these tests, the problem appears to affect the Forminator admin builder/editor across Forms, Quizzes, and Polls, while the front-end functionality continues to work.

    Please let me know if there are any further diagnostic steps I can safely perform.

    Thank you.

    Thread Starter fajarsusilowati83

    (@fajarsusilowati83)

    1 week, 2 days ago

    Additional troubleshooting update

    I have now carried out some further troubleshooting:

    • The Forminator editor still shows a blank white page in an Incognito/Private browsing window with browser extensions disabled.
    • I also tested using Health Check Troubleshooting Mode with only Forminator active. The Forminator editor remained blank even when TranslatePress and the other plugins were disabled.
    • This issue affects not only my existing forms, but also a newly created Blank Form, Quiz, and Poll. They can be created successfully, but opening them for editing results in the same blank white page.
    • The front-end forms and previews are still working, and a test submission was successfully processed and emailed.

    The browser console consistently shows:

    Uncaught TypeError: Cannot read properties of undefined (reading 'transition')

    originating from:

    form-scripts.js?ver=1.57.3

    There is also a preceding WordPress React 19 compatibility warning:

    [wordpress-react-19] Accessing __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED was removed in React 19 and is provided by a compatibility shim.

    I have also contacted TranslatePress support regarding a separate database deadlock involving their machine translation locks. They noted that because the Forminator editor remains blank even with TranslatePress disabled, this appears to be a separate issue.

    Could you please advise whether the transition JavaScript error in form-scripts.js could indicate a compatibility issue with the current WordPress/React environment, and whether there is a safe workaround or fix that I can test?

    I would prefer to avoid resetting or reinstalling Forminator because the existing assessment form is currently functioning correctly on the front end.

    Plugin Support Jair – WPMU DEV Support

    (@wpmudevsupport15)

    1 week, 2 days ago

    Hello @fajarsusilowati83

    I’m sorry to hear you’re having issues with your site. The information you shared, including the PHP version, are good enough for Forminator, and since you already tested how Forminator works with the rest of the plugins deactivated, the only thing that may be missing, is to check if the form editor loads when you switch the current theme to a default one, like Twenty Twenty-Five. Inspecting the source code of the site, I can see that the plugin you use is not available in the WordPress.org repository, so I’m unable to test Forminator using that theme.

    Also please try to reset the permalink structure. By going to your site’s WP Admin, under -> Settings -> Permalinks, simply go there and without changing any settings, just click on Save Changes. It shouldn’t matter the permalink configuration you use, but if you have it set to “Plain”, please let us know.

    Kind regards,
    Jair.

    Thread Starter fajarsusilowati83

    (@fajarsusilowati83)

    1 week, 1 day ago

    Hi Jair,

    Thank you. I have now completed both tests.

    First, I went to Settings → Permalinks and clicked Save Changes without changing the current permalink structure. My permalink structure is Day and name, not Plain. Unfortunately, the Forminator editor still showed a blank white page after this.

    I then used Health Check & Troubleshooting Mode, with only Forminator enabled. In Troubleshooting Mode, WordPress automatically switched to the default Twenty Twenty-Two theme.

    With only Forminator enabled and Twenty Twenty-Two active, the Forminator editor successfully loaded and I can access the form builder normally.

    Therefore, it appears that the issue may be related to my site’s current theme or its interaction with Forminator.

    Could you please advise what you recommend as the next step to identify the specific theme conflict without changing the live site’s appearance?

    Thank you for your help.

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    1 week, 1 day ago

    Hi @fajarsusilowati83,

    Is it a premium theme? I checked your site to detemine the theme but couldn’t find a free theme with such a name when checked. Or is it a custom theme?

    Is it possible to provide us with a zip copy of the theme so that we could test and see what might be causing the conflict?

    You can use Google Drive to upload the theme zip, and can share that privately to the following email  wpsupport@incsub.com  using this template to share the site URL:

    Subject: ATTN: WPMU DEV support - wp.org 
    Message:  Message:
    Ticket URL
    URL to Google Drive

    Please do make sure the Google Drive URL is marked as public, so it would be visible on our side.

    Please do follow up in this thread once shared.

    Regards,

    Nithin

    Thread Starter fajarsusilowati83

    (@fajarsusilowati83)

    1 week, 1 day ago

    Hi Nithin,

    Thank you for your reply.

    My currently active theme is Kamala. I did not upload or install it manually as a custom theme; I selected it directly from the themes available through my WordPress.com site.

    I have also confirmed through Health Check & Troubleshooting Mode that when only Forminator is enabled and the default Twenty Twenty-Two theme is active, the Forminator editor loads successfully. When I return to my normal site configuration with the Kamala theme, the Forminator editor shows the blank white page again.

    Since Kamala is provided through WordPress.com rather than a theme ZIP that I installed myself, I am not sure whether I have access to a downloadable ZIP copy of the theme.

    Could you please advise how you would like me to proceed in this case, or whether there is another way to provide the theme files for testing?

    Thank you.

    Plugin Support Nebu John – WPMU DEV Support

    (@wpmudevsupport14)

    1 week ago

    Hi @fajarsusilowati83,

    Can you please confirm whether you are using the following theme?

    https://wordpress.com/theme/kamala

    As it’s available only on WordPress.com Premium, we do not have access to the theme files. Do you have SFTP or File Manager access to your WordPress website? If yes, would it be possible for you to download the theme files and email them to us, as mentioned in our previous response?

    Without the theme files, what we can do is limited. Would it be possible for you to check this with WordPress.com support and see if they can provide some help?

    Looking forward to hearing back from you and helping you diagnose the issue further.

    Best Regards,
    Nebu John

    Thread Starter fajarsusilowati83

    (@fajarsusilowati83)

    1 week ago

    Hi Nebu,

    Thank you for your response.

    Yes, I can confirm that I am using the Kamala theme available on WordPress.com at the link you provided.

    As my website is hosted on WordPress.com Premium, I am not currently sure whether I have SFTP or File Manager access that would allow me to download the Kamala theme files directly.

    I have confirmed through Health Check & Troubleshooting Mode that the Forminator editor loads successfully when using the default Twenty Twenty-Two theme with only Forminator enabled. However, when I return to the normal site configuration with Kamala, the Forminator editor displays the blank white page again.

    I will contact WordPress.com Support and ask whether they can assist with this theme compatibility issue or provide an appropriate way to obtain the Kamala theme files for troubleshooting.

    I will update this thread once I receive their response.

    Thank you for your continued assistance.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    1 week ago

    @fajarsusilowati83 To clear up any confusion, WordPress.com and WordPress.org are two different entities: https://wordpress.org/documentation/article/difference-between-wordpress-org-and-wordpress-com/

    Because this is an issue with your wordpress.com hosting, you should ask WordPress.com support instead: https://wordpress.com/support/help-support-options/

    kylebeattie

    (@kylebeattie)

    4 days, 3 hours ago

    I’m seeing the same issue, and I don’t think it’s theme-specific: it’s React 19.

    WordPress: 7.1.2
    Forminator: 1.57.3
    WordPress.com (Business, with wpcomsh), custom block theme.

    The editor fails for every form, including new ones.

    WordPress.com has the Gutenberg gutenberg-react-19 experiment switched on, so WordPress registers React 19.3.0 for the react, react-dom and react-jsx-runtime handles. Running React.version in the console on the Forminator builder page returns 19.3.0; WordPress 7.1 normally ships React 18.3.

    Forminator’s build/form-scripts.js bundles React 18’s react-dom but uses WordPress’s global React. That bundled react-dom reads React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED.ReactCurrentBatchConfig.transition. React 19 removed that internal object, and the [wordpress-react-19] compatibility shim doesn’t provide ReactCurrentBatchConfig, so the builder throws Cannot read properties of undefined (reading 'transition') and renders a blank page.

    On WordPress.com the experiment can’t be turned off from wp-admin. The Gutenberg settings page is hidden, and saving gutenberg-experiments through the REST API doesn’t stick.

    azacharias360

    (@azacharias360)

    4 days, 3 hours ago

    After a lot of stumbling around. I paid the $50 to be able to create a support ticket. This was their suggestion.

    RESOLUTION: deactivate Gutenberg plugin!

    Plugin Support Fida – WPMU DEV Support

    (@fidawpmudev)

    3 days, 21 hours ago

    Hello @fajarsusilowati83 , @kylebeattie , @azacharias360 ,

    I hope you are doing well.

    It seems Gutenberg React 19 is conflicting with the Forminator plugin.

    We have already reported the issue to our developers, and they are working on it to release a fix in an upcoming version. However, there is no ETA.

    As a workaround, if you want to use React 19 in Gutenberg, you can try this snippet to fix the conflict. 

    <?php
/**
 * Plugin Name: Forminator React 18 on admin screens
 * Description: On Forminator admin screens, load Gutenberg's React 18 builds while the React 19 experiment stays enabled everywhere else.
 * Version: 1.0.0
 */

if ( ! defined( 'ABSPATH' ) ) {
    exit;
}

/**
 * Point the three vendor handles back at React 18
 * 
 */
add_action( 'admin_enqueue_scripts', 'forminator_react_18_on_forminator_screens', 0 );

function forminator_react_18_on_forminator_screens() {
    if ( ! function_exists( 'gutenberg_is_experiment_enabled' ) || ! gutenberg_is_experiment_enabled( 'gutenberg-react-19' ) ) {
        return;
    }

    $page = isset( $_GET['page'] ) ? sanitize_text_field( wp_unslash( $_GET['page'] ) ) : '';
    if ( 0 !== strpos( $page, 'forminator' ) ) {
        return;
    }

    $scripts     = wp_scripts();
    $extension   = SCRIPT_DEBUG ? '.js' : '.min.js';
    $vendors_dir = gutenberg_dir_path() . 'build/scripts/vendors/';

    foreach ( array( 'react', 'react-dom', 'react-jsx-runtime' ) as $handle ) {
        $asset_file   = $vendors_dir . $handle . '.min.asset.php';
        $asset        = file_exists( $asset_file ) ? require $asset_file : array();
        $dependencies = isset( $asset['dependencies'] ) ? $asset['dependencies'] : array();
        $version      = isset( $asset['version'] ) ? $asset['version'] : '18.3.1';

        gutenberg_override_script(
            $scripts,
            $handle,
            gutenberg_url( 'build/scripts/vendors/' . $handle . $extension ),
            $dependencies,
            $version
        );
    }

    if ( SCRIPT_DEBUG ) {
        $react = $scripts->query( 'react', 'registered' );
        if ( $react && ! in_array( 'wp-react-refresh-entry', $react->deps, true ) ) {
            $react->deps[] = 'wp-react-refresh-entry';
        }
    }
}

    The above snippet is more of a workaround that disables React 19 on Forminator admin pages until the issue is sorted on the plugin side.

    You can implement the above code using mu-plugins. Please check this link on how to implement the above code as a mu-plugin:
    https://wpmudev.com/docs/using-wordpress/installing-wordpress-plugins/#installing-mu-plugins

    Kind Regards,
    Fida Al Hasan

Viewing 12 replies - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.