After og.module upgrade, any subsequent content is not indexed for searching. This can be worked around by forcing the index to rebuild itself, and from that point on content is indexed properly.

Could this be included in the upgrade script?

Comments

moshe weitzman’s picture

moshe weitzman commented

I can't think of a reason why this would be so. i'd like to know what is happpenning on the code level. is this 4.6 or 4.7?

geodaniel’s picture

geodaniel commented

Could it be something to do with node_access maybe? Maybe it's an issue in search, not og - or somewhere in between. It's running on 4.6.

Just to expand on the original description a little: the search index was showing as being at 100% even though there were definately items missing, so it's not as though the search had seen them but not indexed them, it was positively ignoring them for some reason. I'm not sure why resetting the index would change this behaviour though...

mgabalins’s picture

mgabalins commented

I notice similar behaviour with 4.7 version. Originaly I thought that this is taxonomy or search bug see more on my post: http://drupal.org/node/63392

geodaniel’s picture

geodaniel commented
Status: Active » Closed (won't fix)

Haven't come across this issue for quite some time, assuming obsolete.