Plugin Author
Jose
(@giuse)
Hi @pkverma99
thank you very much!
The pages of BuddyPress are not normal single pages, so you need custom Frontend URLs.
Try closing the URL with a slash “/” and let me know if it works.
For example, you have the page https://your-domain.com/members, be sure in your Custom URLs settings you set https://your-domain.com/members/, not simply https://your-domain.com/members.
Plugin Author
Jose
(@giuse)
Hi, @pkverma99 do you still need help on this topic? Have you tried what suggested?
Thread Starter
bekind
(@pkverma99)
Hi @giuse
Apologies for the delay here. I verified with the slash “/” and it still does not work. Here are some more details:
- My method for verifying whether FDP is working or not is via doing view source on the page. There is a HTML comment that says “Freesoul Deactivate Plugins has disabled xx plugins on this page” and that comment is how I normally verify that the FDP is working. I also verify the behavior. But in this case, I am just checking the message which is not coming.
- I am using Custom URL -> Front End URLs for managing BuddyPress pages. And the URL that I have configured is https://[domain]/member/*.
Hope that gives enough details. Kindly let me know if I am missing something.
Regards
Plugin Author
Jose
(@giuse)
Hi @pkverma99
Really no problem, thank you very much for the information.
The HTML comment is the fastest way to see if FDP is working, but it’s not always true that if you don’t see that comment it means FDP is not working.
If for example, you strip out the HTML comments for performance purposes, also that comment will be stripped out. This happens for example if you serve a minified HTML.
Better you add this line of code in your wp-config.php before the comment “/* That’s all, stop editing! Happy publishing. */”:
define( 'EOS_DP_DEBUG',true );
After adding that line of code, you will be able to see the disabled plugins in the JavaScript console (Right-click => Inspect Elements => Console).
You will see something that looks like this:
*** PLUGINS DISABLED BY FREESOUL DEACTIVATE PLUGINS ***
…..
including the list of disabled plugins.
If you don’t see *** PLUGINS DISABLED BY FREESOUL DEACTIVATE PLUGINS *** in the console it means FDP is not working.
If you see it, but the list is empty, it means FDP is not able to detect that page and assign the set of disabled plugins.
Let me know what’s your case.
Thread Starter
bekind
(@pkverma99)
Hi @giuse,
I tried what you had suggested and I can see the console log on other pages where I can see the list of plugins disabled by FDP in the log. But on pages like https://[domain]/members/%5Bmember_id/, the console log has no FDP related message. I don’t see *** PLUGINS DISABLED BY FREESOUL DEACTIVATE PLUGINS *** message at all.
Regards
Plugin Author
Jose
(@giuse)
Hi @pkverma99
if you need to disable plugins on that kind of pages you need something like this:
*members/*/
*members/*/ will disable plugins on all pages that are https://your-domain.com/members/whatever-here/
I’ve right now tested with BuddyPress and it works.
Use always the star symbol “*” to replace variable parts of the URL.
Let me know if it works also for you.
Thread Starter
bekind
(@pkverma99)
Thank you @giuse for the help.
I had one query on this solution, would it impact the pages that contain “members” word in their post title? We do have many blog posts that contain members word in their title and I don’t want this FDP configuration activated on those pages with “members” word in their title.
Regards
Plugin Author
Jose
(@giuse)
Plugin Author
Jose
(@giuse)
Hi @pkverma99
do you still need help with this topic?
Thread Starter
bekind
(@pkverma99)
Hi @giuse,
Thanks for checking in. Yes, I do need help as I tried this pattern – https://your-domain.com/members/*/ and I am not seeing any FDP impact on BuddyPress pages. On other pages, FDP is disabling plugins as per configurations.
Plugin Author
Jose
(@giuse)
Hi @pkverma99
as written in the email, it was a typo error in your pattern. I will close this thread. I will answer soon to your last email.
Thread Starter
bekind
(@pkverma99)
Thanks @giuse. Much appreciate your help as always. I should have closed this thread earlier, it was my mistake on a misspelled word that caused my issue.