Bug – Problem with Bricksable after update from 1.6.44 with motion.page

  • Resolved mad99

    (@mad99)


    7 months, 3 weeks ago

    Hi Bricksable support,
    Your plugins is a great extension for bricks and I love it.

    # BUG/Problem in frontend.min.js
    Unfortunatelly since the update from 1.6.44 the motion.page (GSAP-Animation) Plugin does not working properly anymore.
    First I thought it has to do with bricks update. But at the end with a lot of try&error I found out -> It has to do with your update.
    Particular with your JS-Code under/bricksable/includes/elements/read-more/assets/js/frontend.min.js

    # Exclusion procedure
    Have tried different approaches. The Scroll-Trigger is always shifted a lot. with begining of the section with read-more Elements in it. In the linked page in 3.th section after logo’s on black bg. And it continues right to the end of the page. It looks totally broken.

    No Idea why, but when I replace this particular js-Code within 1.6.48 with the “old” code 1.6.44 all is fine on every page until the very end of the page.

    When I replace the JS-Code with new 1.6.47 or 1.6.48 the broken scrolling is back until the very end of the page.

    # Conclusion
    So it has to do something with the read-more element JS code.
    Would be great if you could analyse the problem and fix the bug in the js-code, so it will also work with the motion.page animation plugin.

    # Details
    Bye the way, the trigger-class for animation has nothing to do with the classes direct used from read-more elements.
    The trigger class (“mp-slide-up”) is added to the bricks element directly within bricks builder.
    Tried also your settings in the plugin. But there is nothing to find about the js.code or workarounds.

    Looking forward to your help or hint if there is some workaround or setting in your plugin.


    PS: Can send you credentials for backend/sftp if you need. But I guess the change has to be minmimal. Because the JS-code only differs only minimally. But because of minfying code it is hard to grasp the logic/change in depth for me.

    • This topic was modified 7 months, 3 weeks ago by mad99.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter mad99

    (@mad99)

    I have to ask again ?? Sorry…
    But in new Update Version 1.52, Bricksable’s read-more Element still breaks the page and the motion.page animation.
    Unfortunatelly the js-Code undder [wp-plugins]/bricksable/includes/elements/read-more/assets/js/frontend.min.js os only stored in minimized version. So it is hard to debug.

    But at the end although the Meta-Data says it is the same version: 

    /*!
 *  @preserve
 * 
 * Readmore.js plugin
 * Author: @jed_foster
 * Project home: jedfoster.com/Readmore.js
 * Version: 3.0.0-beta-1
 * Licensed under the MIT license
 * 
 * Debounce function from davidwalsh.name/javascript-debounce-function

    It is obvious different from Version 1.48 above

    beforeToggle is in the new code 4 times to find. in the old verson only 3 times.
    As I wrote, it is hard to debug in mininized version.
    Would be great to get some help or answer, what is added in the new version.
    Would be also great if you could change the Version-Number so it refleces the reallity. The it would be much easier for me to see the break-point in versions…

    Currently I have to copy-paste the old code to your plugin. Then all is working fine. Maybe there is a way for you to debug your additional beforeToggle insert-code about some problems on the linked Website. As I wrote, I could send you the credential if needed.
    Looking forward to your reply/help.
    Kind regards
    Martin

    • This reply was modified 6 months ago by mad99.
    Plugin Author Bricksable

    (@bricksable)

    Hi @mad99 replied to your email. All good now!

    Thread Starter mad99

    (@mad99)

    Hey Ken,
    had also a new content-version for StageServer and would also check on that end.
    But as always times fly ;))

    Have checked now on the page sent to you and also local and stage. Seams to be solved.
    Sometimes is hard to be sure with the caching-mechanisms. ??
    Looks great!! thank you.
    If there should be some issues about (arising later), I will connect again.
    Thank you for your fast and professional help.
    Cheers
    Martin

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Bug – Problem with Bricksable after update from 1.6.44 with motion.page’ is closed to new replies.

Tags