Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor Joe McGill

    (@joemcgill)

    Thanks Jesse,

    Can you tell me what the URL is for the page where you were editing the ACF groups?

    Thanks,
    Joe

    Thread Starter Jesse Graupmann

    (@jgraup)

    /wp-admin/post.php?post=488&action=edit
    Thread Starter Jesse Graupmann

    (@jgraup)

    Looks like wp.media is undefined when that function gets called.

    wp.media.events.on( 'editor:image-update', function( args ) {
    Plugin Contributor Joe McGill

    (@joemcgill)

    What version of WordPress are you running?

    Thread Starter Jesse Graupmann

    (@jgraup)

    WordPress 4.1.1 w/Advanced Custom Fields Pro 5.1.8

    Plugin Contributor Joe McGill

    (@joemcgill)

    Interesting. Does this error happen on all posts or is this a specific to a particular post or custom content type?

    Thread Starter Jesse Graupmann

    (@jgraup)

    Looks like it is just happening from Custom Fields -> Custom Fields -> Edit.

    I’m sure if you just added a null check on wp.media you could call it a day.

    Plugin Contributor Joe McGill

    (@joemcgill)

    Ah, I see it. Didn’t realize ACF used the post.php and post-new.php pages as a base. We’ll get this patched up.

    Thread Starter Jesse Graupmann

    (@jgraup)

    Awesome, thanks!

    Thread Starter Jesse Graupmann

    (@jgraup)

    If you get a chance, I noticed some issues (not related to this plugin) w/ACF 5.2.x so I haven’t upgraded. I would double check against that when you’re done as it seems some things have changed. It may not be that different but it’s worth making sure to QA the latest.

    Plugin Contributor Joe McGill

    (@joemcgill)

    For sure. If you find any weirdness after the upgrade, let us know. In the mean time feel free to test out the latest code on the master branch in Github, which includes a patch to this issue: https://github.com/ResponsiveImagesCG/wp-tevko-responsive-images/pull/71

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘[Bug v2.1.1] Uncaught TypeError’ is closed to new replies.