• Resolved G.

    (@accentsduterroir)


    Hello Meow Lightbox Team,

    I hope this message finds you well.

    I am writing to inform you about an issue that was identified by the WP Rocket support team. They discovered a conflict caused by the “Output Buffering” option in Meow Lightbox, which affects the PHP buffer.

    In my case, for example, this issue causes a fatal error with NinjaForms and makes the form unusable (broken).

    Here are the details:

    • The issue occurs when the “Output Buffering” option is enabled.
    • It clears the PHP buffer at an incorrect location, removing the HTML closing tags when those are inside text/template scripts.
    • This problem arises specifically when the “Remove Unused CSS” option is used in WP Rocket.

    The conflict is found on line 63 of /meow-lightbox/classes/core.php, where the following code is hooked to the init action if Buffer mode is enabled (isObMode):

    add_action('init', array($this, 'start_ob'));

    Disabling the “Output Buffering” option in production fixes the issue, but a more permanent solution would be appreciated.

    I hope this information helps in resolving the conflict. Thank you for your attention to this matter.

    Best regards.

Viewing 1 replies (of 1 total)
  • Plugin Support Val Meow

    (@valwa)

    Hey @accentsduterroir! ??

    If you can use the lightbox without Output Buffering (OB), it’s preferable to do so. This approach should be utilized if you’re using an older theme or have a specific use case that necessitates it. Running the lightbox without OB might be more efficient.

    The OB functions are invoked at “init” (start) and “shutdown” (cleanup). Without more information on when it could cause an issue, it’s challenging to adapt this behavior. If you’re already in contact with the WP Rocket team, please advise them to reach out to us through Contact & Support | Meow Apps with all the necessary information and their thoughts on the best way to make it work for both plugins.

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Issue with Output Buffering causing HTML Tag Removal’ is closed to new replies.