Home Page Not Showing

Hi, using Version 120703 + s2Member Pro v120703 on Firefox 16.0.1 on Mac OS X 10.7.5 – Running Quick Cache Version 111203 – emptied all Quick Caches, emptied Firefox’s caches, rebooted.

URL: http://members.skinnychef.com

I created a new home page and defined it under >> SETTINGS >> READING >> FRONT PAGE DISPLAYS STATIC PAGE >> FRONT PAGE: The Smart Way: Eat Yourself Into Shape

But the homepage is only shown to logged in members. If you’re not logged in, you’ll see the old homepage (a page which has been deleted!) What am I missing here?

Thanks,
Uli

• This topic was modified 4 years, 2 months ago by  Uli Iserloh.

Did you make sure that the page you’re selecting has not been restricted anywhere in Dashboard -› s2Member® -› Restriction Options? If it’s only being shown to logged in members, I would suspect that it’s restricted somewhere.

However, I think this might be a problem only on your computer, as I just visited the URL you linked above and the page loaded right up. See screenshot below:

Raam,
[1] Page has no restrictions, checked.
[2] The page that you’re seeing has been deleted from the system… how can it still show up? Cache folder is empty.
[3] Page should look like this:

Uli

What caching plugin are you using? Does it have a button to update the cache?

Also, not sure if it’ll help, but just guessing here: save your s2 General Options page again, same for your WP reading settings, and the permalinks settings, even if you didn’t make changes. I mention this because similar errors I’ve seen in the past, although not exactly the same, were fixed when re-saving one those.

Cristian,
thanks for weighing in… after thinking it through, I concluded that it must be something related to caching. So I removed the quick-cache plugin/folder, then reinstalled… same outcome.

Then I looked at my wp-config.php, and there was this nasty little remnant from when I was using W3TC… after removing all of that and its associated folders, the problem was resolved. Duh.

Issue resolved.

Thanks for the update, Uli. Glad to hear you fixed this. :)