Notifications
Clear all

[Closed] Guest can still view first page of member directory even when Usergroup disallows

9 Posts
4 Users
1 Likes
401 Views
Posts: 94
Topic starter
(@vanessa)
Estimable Member
Joined: 6 months ago

I've setup Guest and unchecked 'Front - Can view members' in the Usergroup setup.

However when testing a Guest will still see the Members tab in the forum head, and on clicking will see the first page of the member directory.

When clicking through to the second page it correctly shows 'You do not have permission to view this page'

 

8 Replies
Posts: 986
Moderator
(@martin)
Support Team
Joined: 8 years ago

Hi @vanessa,

I think this is a cache issue. Please make sure wpForo pages are excluded from your cache solutions.

5 Replies
(@vanessa)
Joined: 6 months ago

Estimable Member
Posts: 94

@martin thx, that was the issue.

To other folks reading this, be careful with excluding more than /participants/ from the cache if you run a public forum you probably want all the topic and reply pages cached.

dimalifragis
(@dimalifragis)
Joined: 4 years ago

Famed Member
Posts: 2569

Posted by: @vanessa

@martin thx, that was the issue.

To other folks reading this, be careful with excluding more than /participants/ from the cache if you run a public forum you probably want all the topic and reply pages cached.

 

OF COURCE NOT.

NO CACHING for wpForo, the whole of it. wpForo has its own internal caching.

Please do not give such advices.

 

(@vanessa)
Joined: 6 months ago

Estimable Member
Posts: 94

@dimalifragis wpForo does *not* have edge caching.

If you're running a forum accessible to Guest users without edge caching, then you're doing it wrong.

dimalifragis
(@dimalifragis)
Joined: 4 years ago

Famed Member
Posts: 2569

Posted by: @vanessa

@dimalifragis wpForo does *not* have edge caching.

If you're running a forum accessible to Guest users without edge caching, then you're doing it wrong.

https://wpforo.com/community/faq/wpforo-and-cache-plugins/

No caching for wpForo, PAGE caching or else.

The reason is simple. NO CACHING plugin or server plugin "understands" wpForo. wpForo has its own ecosystem. Caching will make wpForo to serve old content and in some cases DB corruption happens.

Also caching blocks several Security plugins for Wordpress. Wordfence RATE LIMIT doesn't work if any caching is active. Because caching happens BEFORE Wordfence and the pages are already served. And for other technical reasons.

Still, you are free to use whatever you wish.

 

(@vanessa)
Joined: 6 months ago

Estimable Member
Posts: 94

@dimalifragis Do you know what an edge cache is?

Robert
Posts: 10503
Admin
(@robert)
Support Team
Joined: 8 years ago

Hi @vanessa,

All wpForo pages should be excluded from any kind of caching, even if you use edge cache you save some snapshot in a server which is close to current user. This is also a cache and this will prevent current visitor to see changes on the forum page. The forum page will be a static list.

wpForo does as much as possible to cache requests and data pulling from database in a correct way. Only wpForo know when the data should be cached and which data should be cached. That's why we always recommend exclude wpForo page from all cache layers, excerpt static data like CSS and JS files. For example, you can enable AWS CloudFront without any issue.

This topic provides some good information about the issue and how to exclude wpForo pages from some popular plugins: https://wpforo.com/community/faq/wpforo-and-cache-plugins/

1 Reply
(@vanessa)
Joined: 6 months ago

Estimable Member
Posts: 94

Hi @robert 

The concern you raise about mixing member data with guest data in the edge cache is only applicable in the simple case.

Many edge cache providers allow caching to be done selectively depending on a user's login state. E.g. This can be accomplished in Cloudflare using the 'Bypass Cache on Cookie' - https://developers.cloudflare.com/support/third-party-software/content-management-system-cms/caching-static-html-with-wordpresswoocommerce/

I agree that logged in pages should not be edge cached unless you're using a complex setup with edge computing made possible through features like Cloudflare Workers. I imagine very few folks in this forum have such a setup.

However IMO if you have the ability to only edge cache guest pages, and deliver them through the edge cache to guests, then this will offer a significant performance boost.