• Resolved Ali

    (@alikm)


    Hey, after upgrading I am getting the following erorr in console, which leads to not being able to resize the cover photos on profiles.

    Uncaught TypeError: Cannot read property ‘split’ of undefined
    at HTMLDivElement.<anonymous> (um-functions.min.js?ver=4.9.5:1)
    at Function.each (jquery.js?ver=1.12.4:2)
    at a.fn.init.each (jquery.js?ver=1.12.4:2)
    at um_responsive (um-functions.min.js?ver=4.9.5:1)
    at um-responsive.min.js?ver=4.9.5:1
    at dispatch (jquery.js?ver=1.12.4:3)
    at r.handle (jquery.js?ver=1.12.4:3)
    um-functions.min.js?ver=4.9.5:1 Uncaught TypeError: Cannot read property ‘split’ of undefined
    at HTMLDivElement.<anonymous> (um-functions.min.js?ver=4.9.5:1)
    at Function.each (jquery.js?ver=1.12.4:2)
    at a.fn.init.each (jquery.js?ver=1.12.4:2)
    at um_responsive (um-functions.min.js?ver=4.9.5:1)
    at um-responsive.min.js?ver=4.9.5:1
    at dispatch (jquery.js?ver=1.12.4:3)
    at r.handle (jquery.js?ver=1.12.4:3)

Viewing 5 replies - 1 through 5 (of 5 total)
  • nvm

    • This reply was modified 6 years, 11 months ago by txpmr.
    Thread Starter Ali

    (@alikm)

    @txpmr – does this not point to a larger issue?
    Here’s my soltuon… the data-ratio was attributed but was not being pulled in for some reason. I edited /wp-content/plugins/ultimate-members/assets/js/um-functions.js on line 193 to the following:

    		if (typeof ratio === 'undefined') {
    			ratio = '2.7:1';
    		}
    		var ratios = ratio.split(':');

    Then I saved it as um-functions.min.js.

    • This reply was modified 6 years, 11 months ago by Ali.
    • This reply was modified 6 years, 11 months ago by Ali.
    • This reply was modified 6 years, 11 months ago by Ali.
    • This reply was modified 6 years, 11 months ago by Ali.

    i just upgraded to 2.10.0 can you walk us through the steps to reproduce this error?

    not seeing this……

    Thread Starter Ali

    (@alikm)

    @txpmr It occurs when I load in any profile, until this fix. My guess is possibly conflicting enqueue priorites or other plugins. For me its resolved and I’ll be keeping an eye out for the next update.

    Thanks for an awesome plugin btw!!

    This has been Fixed in 2.11.0

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘2.0.10 JS Error’ is closed to new replies.