Paypal Product Pay Later Messaging Block destroys the page product layout

This topic has 3 replies, 2 voices, and was last updated 4 months, 2 weeks ago ago by DEVELOWEB

  • Avatar: DEVELOWEB
    DEVELOWEB
    Participant
    December 28, 2023 at 23:46

    Hi,
    I send you the video link (into private area) to show you an error caused by the block Paypal Product Pay Later Messaging.

    entering this block in any layout, the page is completely destroyed. some CSS class/id conflicts.

    I ask you to help me.

    many tanks

    Please, contact administrator
    for this information.
    2 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    December 29, 2023 at 14:18

    Hello, DEVELOWEB,

    Thank you for reaching out to us and providing the video.

    1/ Please check how it works when not XStore theme is activated, but the default WooCommerce theme – Storefront.

    2/ Regarding the PayPal Product Pay Later Messaging element, could you please confirm which plugin this functionality is associated with? We suggest reaching out to the support team of the respective plugin for further assistance.

    Please be advised that while we strive for broad compatibility, we cannot guarantee that our theme will function seamlessly with all third-party plugins. In certain instances, additional customization may be required to ensure compatibility between the theme and plugins. It is important to note that the responsibility for such customizations falls beyond the scope of support we can offer as theme authors.

    We regret any inconvenience this may cause and thank you for your understanding.

    Kind Regards,
    8theme team

    Avatar: DEVELOWEB
    DEVELOWEB
    Participant
    December 29, 2023 at 16:25

    ok. Thanks the same for the tips. I solved the same by applying a custom css code.

    many thanks

  • Viewing 3 results - 1 through 3 (of 3 total)

The issue related to '‘Paypal Product Pay Later Messaging Block destroys the page product layout’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.