Booster Plus breaks FAQ plugin

  • Resolved jkriester

    (@jkriester)


    1 month ago

    Hi,

    The paid plus version of 8.0.0 Booster Plus for WooCommerce breaks Ultimate FAQ Accordion Plugin Versie 2.4.10.

    Using the not Booster Plus version of the plugin removes this bug.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor David G

    (@gravid7)

    1 month ago

    Hi,

    Can you please share the configuration details along with a screenshot of the issue?
    If possible, a short video would be even more helpful for better understanding. so we can check and help you.

    Thanks!

    Thread Starter jkriester

    (@jkriester)

    1 month ago

    Replication of the issue is very easy:

    Just make a clean wordpress 6.9.4 install.
    And install only these plugins:

    Booster Plus for WooCommerce Version 8.0.0
    WooCommerce Version 10.7.0
    Ultimate FAQ Accordion Plugin Version 2.4.10

    And Add a new FAQ.

    While adding the new FAQ the lower half of the screen becomes unclickable.

    Now disable Booster Plus for WooCommerce Version 8.0.0 and the lower half of the screen become clickable again.

    Plugin Contributor David G

    (@gravid7)

    3 weeks, 1 day ago

    Hi,

    Booster Plus for WooCommerce Version 8.0.0
    WooCommerce Version 10.7.0
    Ultimate FAQ Accordion Plugin Version 2.4.10

    I tested the setup from my end and it’s working fine. Could you please share a screen recording of the issue so we can check and help resolve it?

    Also, please confirm which Booster module you are using.

    Thread Starter jkriester

    (@jkriester)

    3 weeks, 1 day ago

    Here is a video that shows the problem: https://youtu.be/Y8o5c7hyevE

    No modules are active.

    Plugin Contributor David G

    (@gravid7)

    1 week, 5 days ago

    Hi,

    Thank you for your for sharing the detailed feedback regarding this issue.

    We have tested the same functionality on our demo environment, and it is working correctly there. Based on this, it may be related to a server-specific configuration or something unique to your site environment.

    To help investigate this properly and avoid further delays, could you please contact us directly on our contact us page so we can debug the issue more closely with you?

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

You must be logged in to reply to this topic.