Title: “Secure User Profiles” component not working
Last modified: October 28, 2016

---

# “Secure User Profiles” component not working

 *  [wpfiend](https://wordpress.org/support/users/wpfiend/)
 * (@wpfiend)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/secure-user-profiles-component-not-working/)
 * Hello.
 * I am using the latest Avada theme with the latest builds of WordPress and bbPress.
 * Under “bbPress Global”, this option is not working on the front end:
    **Secure
   user profiles so they cannot be seen by non logged-in users.**
 * I have checked it off and then have left the URL field blank as well as added
   the FQDN of my site. Neither options worked. A non logged-in user could still
   see a profile by clicking on their name anywhere in the Forums.
 * Can you please help…??

Viewing 1 replies (of 1 total)

 *  Plugin Author [Pascal Casier](https://wordpress.org/support/users/casiepa/)
 * (@casiepa)
 * [9 years, 5 months ago](https://wordpress.org/support/topic/secure-user-profiles-component-not-working/#post-8862839)
 * Hi,
    It seems to work on other installs I have. Do you have any other plugin 
   that could cause this behaviour ? Pascal.

Viewing 1 replies (of 1 total)

The topic ‘“Secure User Profiles” component not working’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/bbp-toolkit.svg)
 * [bbPress Toolkit](https://wordpress.org/plugins/bbp-toolkit/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/bbp-toolkit/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/bbp-toolkit/)
 * [Active Topics](https://wordpress.org/support/plugin/bbp-toolkit/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bbp-toolkit/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bbp-toolkit/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Pascal Casier](https://wordpress.org/support/users/casiepa/)
 * Last activity: [9 years, 5 months ago](https://wordpress.org/support/topic/secure-user-profiles-component-not-working/#post-8862839)
 * Status: not resolved