Support Forum

Issues with Recent Post widget

PR Philip Ridley
Philip Ridley
Member

I have my forum page protected by MemberPress, but want the widget to show recent topics on a particular forum on my front page. They do not show when you are not logged in but show when you are, which defeats the objective. How can I fix this?

Only one of my three forums is for the homepage recent post widget and I changed that to allow Guest to have full access on the Simple:Press side, whilst still protecting the WordPress page that I have the forums on, have no idea why the widget is responding to me protecting the page this way.

4 Answers

New Answer

SS SP Community Support
SP Community Support
Admin

Does the widget show the recent topics when the user is logged out and without Memberpress enabled?

PR Philip Ridley
Philip Ridley
Member

Hi. I actually sorted this out now, thanks. It turns out that the forum wasn’t protected by MemberPress afterall, when I turned on the protection the widget started working again. None of this makes sense but at least now it works.

PR Philip Ridley
Philip Ridley
Member

SP Community Support said
Does the widget show the recent topics when the user is logged out and without Memberpress enabled?

  

I thought I had fixed it but I was wrong, it is still broken.

I am not really confident to turn off MemberPress. What I can say is that recent posts show when logged in but don’t show when logged out. The page that Simple:Press is on is protected by MemberPress. Website is https://westonaprice.london

SS SP Community Support
SP Community Support
Admin

You might want to have your host copy your site to a staging location where you can troubleshoot without worrying about breaking the site.  Once the site is copied you can turn off memberpress on the copied site (and other plugins and themes) to see if the widget shows data when the user is logged out.  I suspect that memberpress has applied permissions to the widget but the only way to know for sure is to turn it off to see it the widget works without it. It could also be a conflict with another plugin as well.