Profile Picture Apply Crop Issue – Conflict with Avada

@kyotechu

There were updates done by the UM developers for UM 2.8.1 in this Cropper code.
I have made a new bug report about your issue.

https://github.com/ultimatemember/ultimatemember/issues/1424

kyotechu missveronica?

Different but too close not to mention. This one is strange, because another site with an identical setup on the same server is not experiencing this problem which makes it difficult to understand why UM/Avada is breaking with a function with 2.8.1

With all plugins deactivated on this site except “Ultimate Member” the user can upload photos, cover images, any png or jpeg/jpg etc. on the front end (in 2023 or 2024 theme) on their user profile, activity feeds and groups (see attachement). When Avada theme or even just the Avada builder plugin activated the submit button ceases to work which led me to do this conflict test. 

I am not getting any php errors. In a chrome console I get this warning:

Uncaught TypeError: Cannot read properties of undefined (reading 'scaleX')
    at n.getData (cropper.min.js?ver=1.6.1:10:25897)
    at HTMLAnchorElement.<anonymous> (um-modal.min.js?ver=2.8.1:1:1666)
    at HTMLDocument.dispatch (jquery.min.js?ver=3.7.1:2:40035)
    at v.handle (jquery.min.js?ver=3.7.1:2:38006)

I also get "Label" warnings which I'm not familiar with. 

Glad I found this thread I worked on it for too long already.

thanks

stu

Hi @dblinks @kyotechu

When Avada has enabled lazy-load setting you can face this conflict. We have added the fix to the next version release. See details https://github.com/ultimatemember/ultimatemember/pull/1401

The new version will be released this week or at the start of the next week.

Best Regards!

Thank you for looking into this @nsinelnikov @missveronicatv, I have verified on my installation that if I turn off Avada’s image lazy loading (& sub it out for WP Rocket’s image lazy loading) I am able to successfully apply crop to profile pictures.

I have upgraded to 2.8.1 (accepting that Avada elements prefer Avada’s lazy loading, but this particular tradeoff is worth it for now) [& @dblinks maybe subbing out the image lazy loading would work for your installation as well if you need this in before 2.8.2]. & I am looking forward to the next version with the Avada fix, thanks again! ??

• This reply was modified 10 months, 2 weeks ago by kyotechu.

Worked perfectly. Avada would not look into my ticket and I guess in fairness it is UM but simply choosing WordPress lazy load worked instantly (after messing around for 3+ days). Glad I found this thread it really is the only one that addressed the issue and worked !!

Thanks again @nsinelnikov?@missveronicatv !!