Support » Fixing WordPress » proxy-time.js undefined after 5.5.3 update

  • Resolved aecnews

    (@aecnews)


    I updated our sites to 5.5.3 and now there is a proxy-time.js error in backend dashboard that appears perhaps responsible for some other faults.

    \\Uncaught (in promise) TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at proxy-time.js:298\\

    \\browser.runtime
    .sendMessage({ type: ‘get-state’, payload: [‘proxyTimeEnabled’, ‘proxy’] })
    .then(([enabled, proxy]) => {x
    if (enabled && proxy.status === ‘connected’) shiftTime()
    })
    \\

    Anyone with any suggestions before I roll us back to V 4.x.x?

    All of the caches have been cleared, the fault occurs with plugins disabled and a default theme.

    Thank you.

    • This topic was modified 5 months, 2 weeks ago by aecnews.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue (theme functions can interfere like plugins).

    Thread Starter aecnews

    (@aecnews)

    Thank you, but: All of the caches have been cleared, the fault occurs with plugins disabled and a default theme. I’ve already gone way way beyond reset the plugins and change to a default theme.

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Try downloading WordPress again, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), and delete then replace your copies of everything on the server except the wp-config.php file and the /wp-content/ directory with fresh copies from the download. This will effectively replace all of your core files without damaging your content and settings.

    Some uploaders tend to be unreliable when overwriting files, so don’t forget to delete the original files before replacing them.

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