• Resolved fringewood

    (@fringewood)


    I updated to 6.7 this morning, and Safari 18.1 (MacOS 15.1, Intel) will not access the editor, via dashboard, edit button, etc. Firefox will access the editor. Safari error codes in Inspector:

    [Error] TypeError: undefined is not an object (evaluating ‘tu.unstable_scheduleCallback’)
    n (react-dom.min.js:10:105894)
    (anonymous function) (react-dom.min.js:10:129075)
    Global Code (react-dom.min.js:10:129109)

    [Error] TypeError: (0,l.createRoot) is not a function. (In ‘(0,l.createRoot)(c)’, ‘(0,l.createRoot)’ is undefined)
    oo (edit-post.min.js:2:41071)
    (anonymous function) (post-new.php:1826)

Viewing 15 replies - 1 through 15 (of 17 total)
  • Hi @fringewood

    Seems like a javascript error. I have tried logging in wp dashboard on 6.7 in latest Safari and couldn’t replicate.

    It could be a plugin/theme conflict or an extension in Safari. Try using the incognito and if it doesn’t help try to disable plugins 1 by 1 to find the culprit. You can also try switching to default theme.

    You can also try adding this to your theme functions.php file but I didn’t tested it

    // Add this code to your theme's functions.php or a custom plugin

    function fix_react_in_safari() {
    // Only apply fix if user is in admin area
    if (!is_admin()) return;

    // Dequeue problematic React and ReactDOM versions
    wp_dequeue_script('react');
    wp_dequeue_script('react-dom');

    // Enqueue stable versions of React and ReactDOM
    wp_enqueue_script(
    'react-stable',
    'https://cdnjs.cloudflare.com/ajax/libs/react/17.0.2/umd/react.production.min.js',
    array(),
    '17.0.2',
    true
    );

    wp_enqueue_script(
    'react-dom-stable',
    'https://cdnjs.cloudflare.com/ajax/libs/react-dom/17.0.2/umd/react-dom.production.min.js',
    array('react-stable'),
    '17.0.2',
    true
    );

    // Add compatibility layer for newer React features
    wp_add_inline_script('react-dom-stable', "
    if (typeof window.createRoot === 'undefined') {
    window.createRoot = function(container) {
    return {
    render: function(element) {
    ReactDOM.render(element, container);
    },
    unmount: function() {
    ReactDOM.unmountComponentAtNode(container);
    }
    };
    };
    }
    ");
    }
    add_action('admin_enqueue_scripts', 'fix_react_in_safari', 100);
    Thread Starter fringewood

    (@fringewood)

    I tried the mod to functions.php in my theme, and I tried turning off all Safari extensions. The standard themes (2022, 2023, 2024, 2025), all are inactive. There are no other themes installed. No plug-ins installed. The editor still doesn’t show up.

    • This reply was modified 1 week ago by fringewood.

    @fringewood got it

    Did you tried disabling wp plugins?

    What happens if you switch to standard theme like 2024?

    Thread Starter fringewood

    (@fringewood)

    No wp plugins are installed.

    I dropped themes 2022 – 2024, kept 2025. I switched to it, no difference. Editor still not available.

    @fringewood I see.

    Ok, let’s try to replicate. Can you paste me the link from here https://www.whatsmybrowser.org/

    You’ve used wp 6.7 with no plugins and 2025 theme, correct?

    Thanks

    I’m assuming you are using Cloudflare – I had the same error in my browser’s console (on various browsers) on 2 sites behind CF. Ended up changing the caching level in Cloudflare from “Standard” to “No query string” and this sorted it for me.

    Thread Starter fringewood

    (@fringewood)

    https://www.whatsmybrowser.org/b/KPUJ9

    Not using Cloudfare, I manage my own domain and WordPress.

    Same for me. Select Edit Post. Blank Screen – JavaScript Error
    “You’re using Safari 18.”

    [Error] TypeError: undefined is not an object (evaluating ‘tu.unstable_scheduleCallback’)
    n (react-dom.min.js:10:105894)
    (anonymous function) (react-dom.min.js:10:129075)
    Global Code (react-dom.min.js:10:129109)

    Downgraded to 6.6 – same symptoms

    • This reply was modified 6 days, 11 hours ago by wilkouk.
    • This reply was modified 6 days, 11 hours ago by wilkouk.

    @fringewood @wilkouk I have tried Safari 18 on Catalina and on latest version of the OS (Sequoia) too. Both worked. Are you using the block or the classic editor? Did you tried using incognito (private) window in Safari?

    Thread Starter fringewood

    (@fringewood)

    Private window brought up the editor. I have to set the log in to the private window with remember me checked to be able to edit a post from a private window. A standard window won’t carry over the cookies to private mode.

    I can use this as a work around for the time being. Safari has my amended dictionary, and FireFox has an end of line placement on left arrow. Annoying little things.

    I hope that this issue gets resolved in the next update. It’s not the first time I’ve had this issue, and it usually gets fixed in the next release.

    Thanks for the assistance.

    You’re welcome @fringewood

    If it works in private most likely it means that some of the Safari extensions or cookies or cached files are the reason for those react errors.

    Thanks

    Thread Starter fringewood

    (@fringewood)

    I cleared the cookies for my domain, still no editor. All extensions disabled, didn’t help. No plugs. Maybe a rogue bit of code in the settings not agreeing with the new release. Hard to tell, not worth debugging with the work around.

    @fringewood yes, it will be hard to debug. It can be local storage, service workers etc. You can also try adding versioning to the url like https://myproject.com/wp-admin/post.php?post=9999&action=edit&version=1

    I note this has a ‘resolved’ tag. What was the resolution?

    Hi @wilkouk

    The resolution was to use the private window in Safari. It looks like extensions or cached data in Safari is the reason of this bug.

    Thanks

Viewing 15 replies - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.