TypeError: i is not a function | Unable to edit site content

  • Resolved l0gan0

    (@l0gan0)


    11 months ago

    I am having a strange issue where the Yoast plugin causes an error on posts/pages/custom post types when editing. The page editor loads, and then I receive this error:

    TypeError: i is not a function
    at n.resetDisplays (https://sitename.org/wp-includes/js/media-views.min.js?ver=6.4.2:2:11862)
    at n.initialize (https://sitename.org/wp-includes/js/media-views.min.js?ver=6.4.2:2:11112)
    at h.Model (https://sitename.org/wp-includes/js/backbone.min.js?ver=1.5.0:2:4722)
    at n.constructor (https://sitename.org/wp-includes/js/media-views.min.js?ver=6.4.2:2:17442)
    at new n (https://sitename.org/wp-includes/js/backbone.min.js?ver=1.5.0:2:23777)
    at n.createStates (https://sitename.org/wp-includes/js/media-views.min.js?ver=6.4.2:2:74101)
    at n.initialize (https://sitename.org/wp-includes/js/media-views.min.js?ver=6.4.2:2:73561)
    at h.View (https://sitename.org/wp-includes/js/backbone.min.js?ver=1.5.0:2:14872)
    at n.constructor (https://sitename.org/wp-includes/js/wp-backbone.min.js?ver=6.4.2:2:2602)
    at n.constructor (https://sitename.org/wp-includes/js/media-views.min.js?ver=6.4.2:2:106817)

    I have copied the site to a staging server and a local device where I am unable to replicate the issue.

    Additionally, when I go to Yoast > Settings > Site Basics, I receive the same “i is not a function” error.

    My initial investigation suggests that it may be a javascript conflict, but it doesn’t make sense that the issue only happens on the live site.

    What I’ve tried

    • Deleting/re-installing Yoast
    • Disabling other plugins
    • Using Yoast Test Helper to reset all settings (although it doesn’t allow me to reset site information for some reason)
    • Cloning site to staging and local site (where I cannot replicate the issue)
    • Rolling back to previous Yoast versions

    What fixed the problem

    Rolling back from WordPress 6.4.2 to WordPress 6.3.2

    –

    Since I am unable to replicate the issue on staging/local servers, I cannot change themes or disable CPT or ACF plugins. However other plugins have been disabled and did not affect the behavior.

    I realize this is a temporary solution, so any insight would be much appreciated.

    • This topic was modified 11 months ago by l0gan0.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support devnihil

    (@devnihil)

    @l0gan0 We’re sorry to hear you are experiencing this issue on your site.

    We understand that you aren’t able to modify/disable the theme or critical plugins on the live site, but would you be able to perform a conflict checking using the Health Check & Troubleshooting plugin? It allows you to perform a conflict check without affecting the front end of the site. We have instructions on this available here.

    Also, can you please confirm that the live site environment meets all of the plugin requirements?

    Thread Starter l0gan0

    (@l0gan0)

    Hi Devnihil – Thanks for your response and the link to this tool. I can confirm the server environment meets the plugin requirements.

    I re-updated to the latest version of WP and was able to edit the site content in Troubleshooting mode. I could edit the content on both my theme and the TwentyTwentyThree theme with all plugins enabled except Yoast. Once I enabled Yoast, it gave the same error on both themes.

    Strangely enough, this doesn’t happen when I roll back to WP 6.3.2.

    Plugin Support Rohan Sadanandan

    (@rohans123)

    Hi @l0gan0,

    I understand that you’re unable to reproduce the issue on your staging server and a local device.

    As the next step, can you please try clearing your browser cache and cookies before restarting your browser? If you’re unfamiliar with clearing cache, we have a?guide?to walk you through the process. Please try a different modern browser or another device if the issue remains after clearing the browser cache.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘TypeError: i is not a function | Unable to edit site content’ is closed to new replies.