Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Sadman Sakib Nadvi

    (@sadmansakibnadvi)

    Hello @ck-macleod ,

    Greetings.

    We have already fixed the issue. Please download the dev version from here and check: https://d.pr/f/uBIglQ

    Let me know the update. Thank you.

    Plugin Support Sadman Sakib Nadvi

    (@sadmansakibnadvi)

    Hello @ck-macleod ,

    Greetings. Hope you are doing well.

    I haven’t heard from you since then. So, I was wondering if you could check the dev version or not.

    Please let us know. I wish you a good day.

    Thank you.

    Thread Starter CK MacLeod

    (@ck-macleod)

    Sorry, I did not realize you were actually awaiting a reply.

    I replaced the prior 4.02 with the new one. Maybe because the version # hasn’t changed – I haven’t looked into the details – I needed to clear caches before the fix took effect.

    I’ll check further with colleagues when they return to work next week.

    Thanks!

    • This reply was modified 5 months, 2 weeks ago by CK MacLeod.
    Thread Starter CK MacLeod

    (@ck-macleod)

    Actually, the fix does not seem to work. To double-check, I re-installed the version from the link above, made sure I’d removed our own CSS fix code, cleared browser and site caches, and the pretty player loses opacity. When I restore our fix, it comes back.

    Plugin Support Sadman Sakib Nadvi

    (@sadmansakibnadvi)

    Hello @ck-macleod ,

    Greetings. Hope you are doing fine.

    We addressed this issue on our recent release(v4.0.3). Can you please update the plugin and check if you still have this issue or not?

    Let me know. Thank you.

    Plugin Support Sadman Sakib Nadvi

    (@sadmansakibnadvi)

    Hello @ck-macleod ,

    Hope you’re doing well.

    As we’re not getting any response from you, we are assuming your issue has been solved. And so, we’re going to mark this topic as resolved now.

    Thank you!

    Thread Starter CK MacLeod

    (@ck-macleod)

    Sorry for the delay in replying: Yes, the issue appears to have been fixed.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.