[support] access denied when upgrading from 4.6.3 to 4.7.3

[Chris Johnson]

Laura Scott wrote:
> On Oct 18, 2006, at 8:00 AM, John Angelmo wrote:
> 
>> John Angelmo wrote:
>>> Hello
>>>
>>> I have upgraded from 4.6.3 to 4.7.3 with no errors.
>>> But now when I am logged in everything works fine, but as anonymous I
>>> get 403 errors.
>>> I have run chmod -R 777 on the drupal directory just to be  
>>> certain, and
>>> I can't find any other message then access denied in the drupal log.
>>>
>> I need to add that I changed the right for anonymous to have all  
>> rights
>> but I still get the same 403 error, what could I have missed?
> 
> Did you have any access control modules in place on your site, such  
> as taxonomy access, organic groups or like that? These modules  
> generally need to be properly disabled before undertaking an upgrade.  
> Just a wild guess here, but it's something I did on one site last  
> year -- it's easy to overlook.
> 
> Laura

Now I'm confused.  According to this page, http://drupal.org/node/57822, if the 
contrib module has a *.install file, it should be left enabled.  OG has an 
og.install file.

The same page also says:

"The Basic Upgrade Steps handbook page recommends to turn off all modules that 
are not core modules before starting the update. Since Drupal 4.7 provides an 
install and update system for contributed modules this is not always correct."

I have to admit this is the first time I've heard of disabling non-core modules 
when doing an upgrade!  Maybe that explains some of the past problems I've had 
-- or not.  :-)

..chrisxj