By hyerstay on

I've been running Drupal for years, and have worked thru most problems I've found. I did an update from 6.3 to 6.4, and now my home page (http://lcyc.info) doesn't load (404 page not found), but I can go http://lcyc.info/node and everything is there, all all clean url links work. I've tried various settings in my .htaccess and settings.php files, but I still can't get the home page to load normally. If I turn off clean URLs, none of the pages work. They load as ?q=pagename instead of index.php?q=pagename

Can anyone offer some help?

Thanks,

Jason Hyerstay
http://lcyc.info/ (http://lcyc.info/node)
Lake Champlain Yacht Club
Volunteer Webmaster

⋅ Categories: Drupal 6.x

Comments

cog.rusty’s picture

cog.rusty commented

Is your "Default front page" set to just node in the admin/settings/site-information page?

Have you made any changes to your .htaccess file? If you have, check what happens with a fresh one.

Have you set a $base_url in your settings.php file or is it commented out? If you have, is it just http://lcyc.info ?

Also check if there is a "Rebuild permissions" button in the admin/content/node-settings page. If there is, try it.

hyerstay’s picture

hyerstay commented

Yes, default front page is node. I've tried with a new .htaccess file, and with the one modified by Gallery (no difference). I do think I let my old .htaccess file get overwritten when I uploaded 6.4.

I can't find anything to rebuild permissions. Is there another way to do that?

Is there anything I should be manually checking in the database?

I get the problem with our without the base url setting in my settings.php.

I even tried setting the default front page to be index.php?q=node, and I get this error:

The path 'index.php?q=node' is either invalid or you do not have access to it.

Thanks,

jason

cog.rusty’s picture

cog.rusty commented

Do you have any other .htaccess file in a parent directory higher up, which contains any RewriteRule lines or redirects?

hyerstay’s picture

hyerstay commented

Any other suggestions?

I could really use some help on this, please.

Thanks,

jason

hyerstay’s picture

hyerstay commented

I tried a bunch of other stuff, went thru all my Drupal/Gallery integration again, and here are the fundamental (and annoying) facts about my situation:

1. lcyc.info/?=node (or whatever) only works when my .htaccess file (any version) is removed, regardless of my clean url settings.

2. Removing .htaccess breaks clean urls.

3. with .htaccess present, clean urls work, regardless of my clean url setting.

One thing that happened with this upgrade that I forgot to mention, is that I neglected to take the site into maintenance mode, and it was maybe 30 minutes between when I uploaded the new drupal files and when I ran the upgrade script.

Also, I'm on Dreamhost, if that matters.

Thanks very much. I'm feeling a bit lonely with this problem, after hours of searching, reading, and testing.

jason

hyerstay’s picture

hyerstay commented

If I knew how to code my own htaccess entries, I would add an entry to convert ?q= to index.php?q=

I can manually add index.php to broken unclean urls, and then they work.

jason

vfranklyn’s picture

vfranklyn commented

I'm a new user, but I had that same problem when I enabled CleanURLs in 6.3. The problem for me turned out that there was an 'admin' subdirectory in my public_html directory. In my case, the 'admin' subdirectory didn't do anything useful, so I renamed it. Once I did that, CleanURLs worked and I was able to view my home page.

I'm not sure if this will help or if you've tried this already, but that was my experience.

Steel Rat’s picture

Steel Rat commented

I've got a similar problem, I think.

Upgraded from 5.x to 6.4. The site had no content so the default page was showing. I created a page and promoted it to the front page. Works fine when I'm logged in as admin, as soon as I attempt anonymous access, the user gets either the default page after install, or, if I specify the node to be shown, an access denied error.

I went through the permissions (I've also been running drupal for years), and checked anything for anonymous I thought might be appropriate. No change.

I installed a fresh 6.4 for someone else a few days ago and did not have this problem. Sounds like something left over from an upgrade in the db...

Steel Rat
My Drupal Sites:
Helm's Deep RPG Network
RPGMapShare.com
Infinite Ordnance
Ma

cog.rusty’s picture

cog.rusty commented

Your problem seems different.

I guess you have enabled "access content" in the admin/user/permissions page.

If you have installed and then uninstalled any access control modules, check the admin/build/modules/uninstall page. If there are any leftover tables from disabled modules there, uninstall them.

Check the admin/content/node-settings page. If there is a "Rebuild permissions" button there, try it.

Steel Rat’s picture

Steel Rat commented

Thanks Rusty! The Rebuild Permissions option did the trick. I've never had occasion to use that before. Learn something new every day.

Steel Rat
My Drupal Sites:
Helm's Deep RPG Network
RPGMapShare.com
Infinite Ordnance

Netzarim’s picture

Netzarim commented

I tried the things mentioned above, but was unsuccessful. My site: http://www.amazinggroups.com was recently upgraded to 6.4 from 5.3. I have installed the Advanced frontpage module. I have the frontpage settings the same for authenticated and anonymous users.

Authenticated users get a nice preview list of lat 10 published/promoted node. Anonymous users get nothing. I have no clue what I am missing at this point.

Authenticated, anonymous, and administrator users have access to content.
no uninstall left overs appear to be remaining
rebuilding permissions did not correct the issue.

cog.rusty’s picture

cog.rusty commented

What I see is two list of links, "Recent blog posts" and "New forum topics", but the links don't work. When I click on any of them the URL path changes but I am still looking at the same page. Are you seeing something different as an admin?

Another strange thing is that when I type a non-clean URL (with ?q=) it is automatically rewritten to a clean one. This shouldn't be happening. In short, I am not sure that this is a node access problem and you need to narrow it down and locate the problem by disabling stuff.

If you have added any rewrites of your own to your .htaccess file, remove them to see if that corrects the problem.

Also try to disable your front page module and restore your home page to node in admin/settings/file-information, in case the problem is a bug in that module.