Some non-public pages show to the public [#181897]

I have this page:

It is assigned to the Stout Family group, and it is not marked as a public page. However, it shows to the public. It's the only page like this right now, and I'm not sure when it started not working. I tried these things:

* mark it public, save, then remove the public check-box and save again
* remove all organic groups from the page, save, then re-assign to the Stout Family group without "public" checked
* create a new page from scratch with the proper assignments

In fact, all new nodes do not seem to work with OG anymore... Here's another non-public page, assigned to the Stout Family group:

http://flfn.org/test

All pages that were working before I discovered the problem seem to still be working, except the one I first mentioned. What can I do to resolve this?

Comments

Comment #1

moshe weitzman CreditAttribution: moshe weitzman commented 9 October 2007 at 11:44

remove all other contrib modules and try to reproduce.

Comment #2

brasto CreditAttribution: brasto commented 10 October 2007 at 04:20

Please clarify what you mean by contrib modules. If you mean all other modules, I have a lot of them, and I'd be afraid of losing data if I disabled them, so I'd need to back up my whole database. If there's a less time consuming way to do this, I'm open to that as well.

Comment #3

moshe weitzman CreditAttribution: moshe weitzman commented 10 October 2007 at 11:47

ok, then start with a fresh web site and fresh database. basically, i don't think this is an og problem and i'm trying to help you isolate where the problem is.

Comment #4

scor CreditAttribution: scor commented 10 October 2007 at 12:43

Ideally you would make a copy of your site, and you could safely mess around with it. Once you have found the problem and how to fix it, you can apply the fix to your production site.

Comment #5

brasto CreditAttribution: brasto commented 21 October 2007 at 07:33

I've created a temp test site, and disabled all other non-core modules. I have a handfull of non-required core modules and og enabled only. Still this page shows although it is not marked public, and assigned to the stout family group:

http://tmp.flfn.org/?q=node/3/

Comment #6

moshe weitzman CreditAttribution: moshe weitzman commented 21 October 2007 at 12:39

you enabled access control on admin/og/og?

Comment #7

brasto CreditAttribution: brasto commented 21 October 2007 at 16:37

Yes. In fact, I cannot disable it. I reset to defaults, and tried to disable/re-enable, and now I get this no matter what I do for the config settings:

Validation error, please try again. If this error persists, please contact the site administrator.

Comment #8

moshe weitzman CreditAttribution: moshe weitzman commented 23 October 2007 at 14:55

Status:

Active

» Postponed (maintainer needs more info)

you started with a fresh database or a backup of live site? fresh is better.

Comment #9

brasto CreditAttribution: brasto commented 30 October 2007 at 15:51

I started with a backup of a live site since I want to fix a live site. I recently disabled OG on the test site, uninstalled it, and reinstalled it, but the issue continued. I will now start a site from scratch, and try to rebuild my site. Whether or not I can duplicate the issue, I believe the OG group should seriously consider some tool or some method of finding the problem source, even if it's caused by something wrong in the core instead of OG. I recommend this because this is a serious drawback if I have to completely redo my live site from scratch to resolve a security issue, especially if the issue recurs and I have to do this every time it recurs. Even more important - not many people will be willing to do this.

This will likely take me a couple weeks or more to complete, so stay tuned for an update - unless someone has a less time-consuming recommendation. I'll need to: