Plugin Conflict

  • Resolved Kevin Vess

    (@kevinvess)


    1 year, 1 month ago

    Hello, we’ve been made aware of a conflict with the Force Login plugin.

    Upon inspection of your plugin code and some minimal testing, I believe the issue stems from where your plugin hooks into WordPress to run its process for rendering the calendar landing pages.

    Specifically in the /fluent-booking/app/Services/LandingPage/LandingPageHandler.php file and using the init hook to run LandingPageHandler::handleUrlParamsPage().

    Our plugin checks if a user is logged-in or not and then forces visitors to the login screen. It runs at the template_redirect hook with the default priority. There may be conflicts with other plugins if you render your plugin pages earlier than the time when WP determines which template to load.

    Thanks!

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

Viewing 1 replies (of 1 total)
  • Plugin Support Ruman Ahmed

    (@algorithmsunlocks)

    1 year, 1 month ago

    Hello @kevinvess,

    Thank you for bringing this to our attention. We appreciate your detailed analysis of the potential conflict between FluentBooking and the Force Login plugin.

    We understand that your plugin enforces login requirements at the template_redirect hook, while FluentBooking landing pages are handled within init. This may indeed lead to conflicts in how WordPress determines the appropriate template for rendering.

    We’ll review this further and explore possible adjustments to improve compatibility.

    Best regards!
    Ruman Ahmed.

Viewing 1 replies (of 1 total)

The topic ‘Plugin Conflict’ is closed to new replies.