1. Home
  2. Knowledge Base
  3. Frequently Asked Questions
  4. BuddyBoss Web
  5. Pages
  6. What are the BuddyBoss Paths that Should be Excluded from Page Caching

What are the BuddyBoss Paths that Should be Excluded from Page Caching

Introduction

Dynamic and user-specific pages in BuddyBoss must bypass page caching to function correctly. Caching these paths can prevent real-time updates to profiles, activity feeds, messages, and group content. Exclude the following URL patterns from your cache rules to ensure all dynamic features work as intended.

Paths to Exclude from Caching

Enter each of these patterns (with * wildcards) into your cache exclusion settings:

/members/*

/profile/*

/groups/*

/groups-single/*

/activity/*

/notifications/*

/messages/*

Including the asterisk (*) ensures all sub-paths are excluded. For example, /groups/* covers /groups/, /groups/xyz-group, /groups/123/manage, etc. Omitting * would only exclude the base URL (/groups) and not its children.

Troubleshooting and FAQs

Q: I’m still seeing cached content on a dynamic page—what should I check?
A: Ensure your exclusion patterns match exactly (including leading slash and *), then clear or purge your cache completely (plugin, server, and CDN levels).

Q: My caching plugin doesn’t support wildcards—how can I exclude these paths?
A: Consult your plugin’s documentation. Many offer regular-expression or directory-based exclusions (e.g. ^/groups/.*).

Q: Will excluding these paths significantly impact my site’s performance?
A: No. Only a small portion of pages (dynamic user or group pages) are excluded. Static content and most visitors still benefit from caching.

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Support

To speak to our Agency consultant, fill in the form found at our Contact Page.

  • Get Started

    Enter your name and email address to get started with your project...

  • This field is for validation purposes and should be left unchanged.

Not recently active