Title: Plugin Conflict
Last modified: March 10, 2025

---

# Plugin Conflict

 *  Resolved [Kevin Vess](https://wordpress.org/support/users/kevinvess/)
 * (@kevinvess)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/plugin-conflict-443/)
 * Hello, we’ve been made aware of a conflict with the [Force Login](https://wordpress.org/support/topic/fluent-booking-landing-pages-bypass-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](https://developer.wordpress.org/reference/hooks/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](https://developer.wordpress.org/reference/hooks/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](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fplugin-conflict-443%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  Plugin Support [Ruman Ahmed](https://wordpress.org/support/users/algorithmsunlocks/)
 * (@algorithmsunlocks)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/plugin-conflict-443/#post-18358867)
 * Hello [@kevinvess](https://wordpress.org/support/users/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.

 * ![](https://ps.w.org/fluent-booking/assets/icon.svg?rev=3119303)
 * [Fluent Booking - The Ultimate Appointments Scheduling, Events Booking, Events Calendar Solution](https://wordpress.org/plugins/fluent-booking/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/fluent-booking/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/fluent-booking/)
 * [Active Topics](https://wordpress.org/support/plugin/fluent-booking/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fluent-booking/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fluent-booking/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Ruman Ahmed](https://wordpress.org/support/users/algorithmsunlocks/)
 * Last activity: [1 year, 3 months ago](https://wordpress.org/support/topic/plugin-conflict-443/#post-18358867)
 * Status: resolved