Members can't see home page

[michelle86]

When members click on "Home" in the navbar, they get this message:

[member name] you do not have permission to access this page. This could be due to one of several reasons:

1. Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
2. If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Anyone know how I can make it so my members can see the home page?

[vijayninel]

You must give the usergroup that your general members are in permissions to view the page.

[michelle86]

I've already tried going into the usergroup manager to edit my registered users permissions, but I don't see an option for making them able to view the home page (or not view the home page for that matter).

[Lynne]

Home is the CMS, so the permissions for it are done under the vBulletin CMS section in the admin cp. Two things to check.... first, make sure the main section is published (it used to be, and may still be, that the default is unpublished) and also look under vBulletin CMS Permissions and make sure the users Can Read the section.

[michelle86]

So I went to vBulletin CMS > Permissions. Everyone was already set to see the home page except for banned members.

Then I checked vBulletin CMS > Content Manager, and the home page was already published.

BUT members still can't see the home page.

Really confused...

edit.... I just checked under the section manager, and it wasn't published under there. So I published it there. But it still isn't viewable by members. I don't know what I'm missing

[Lynne]

Not Content Manager, *Section Manager*. Make sure the *section* is published. whoops, just saw you did an edit on that.

Try Clear CMS Cache.

[michelle86]

Thank you so much! Clearing the CMS cache worked.

[abouthere]

I'd like to offer my thanks also - I had several custom usergroups who had no rights to view the CMS side of things and were confusing this with no access to the forums too.

All sorted now.