Upgrading Drupal

After upgrading to 4.6.5 from from a development version of Drupal released after 4.6.2, I have this strange problem:

When I come as an anonymous user the front page shows the "Welcome to your new Drupal-powered website"-page, i.e. the page that is shown when you have a fresh installation of Drupal that still has no content.

If I log in, everything works just fine. All the content are there, and I can do all things I should be able to do. This is true both when logged in as user 1, and with other accounts.

But as an anonymous user I can't see any content.

If I try to go directly to a node (by entering it's url), I get a "403 Access Denied". The 403 message is in the graphical style of my ISP. If I try to go to the same url when logged in, there is no problems.

In the 'access control'-page, the node module/access content is checked for anonymous users.

I have also created a fresh database (initilized with the database.mysql-script from 4.6.5). This works just fine, and after creating some content as a logged in user, I'm able to read it as an anonymous user. This leads me to the conclusion that the error is somwhere in my old database.

--

When upgrading, I checked the update.php script, but since there was no updates later than 2005-05-07 and 4.6.2 was released 2005-06-29 there was no upgrade to perform.

One strange thing with this though: when manualy checking the database I noticed that in the "users" table there is one new field "changed" that my old database did not have. So I added it by hand.

This wakes the suspicion that my old database is out of sync. But I can't find any other dicrepancies (exept that my old database has a "access" field in the "users" that the new one is missing).

--

In an attack of desperaton I even tried with selecting a number of tables from the old database, exporting them and then importing them into the new. But this did not help.

The only difference is that when I try to reach the node directly as an anonymous user, by entering the url, I do not get a 403, I get a 500 (An internal server error occured while processing your request), and the suggestion that this kind of error often is the result of that the program has not been made executable. (Accessing the same node when logged in works just fine.)

--

Any advice/pointers would be apreciated.

Conciedering the importance of the version number (you need to know it in order to select the apropriate upgrade instructions), I'm surprised to find that the only place it's noted is in the changelog file.

Wouldn't it be better to save it in the database, and have some small text like "Drupal 4.6.2" at the entrance page of the administration interface.

Can someone explain to me what I need to do with the following sentence?

"Apply the patches to the Drupal core that are provided. Located in the 'patches' folder"

under i18n/patches folder, there are two patch files (i18n_includes.patch, and i18n_taxonomy_module.patch), what do I need to do with it? I download patch.exe to my machine and I've no idea how to execute those two patch file. I know this is a stupid question but after hours of looking around, I still don't have a clue how to go about this thing.

Thank you

trantt

Hello Everybody:

Specifications:

Apache2 v2.0.54
Drupal v.4.6
Php v.4.3.10-16

I have a problem with my drupal site. I worked with it fine but when i create a virtual host i can't login into.

When i enter the username and the password it try to load but it doesn't load anything. After that if i try to go to other link it don't load. I check all the forum topics searching help, i do all the thing that i found: i changed the php.ini, i check the cookies and its enable, i check the database and the session its open correctly, etc but nothing works.

hi everyone... yet another surprise with 4.7... this one is that for some reason i'm finding 20mb files in my home directory titled core.846 and the like since i upgraded to 4.7 beta 3. perhaps they are unrelated... or perhaps this is drupal forcing a server crash and a core dump? you'd think my ISP would be all over me on this though, right :o?

any thoughts? or is it something else?

Theres a bug with HTML in the latest beta. Using any HTML tags in a post and then saving it results in the HTML tags being removed. Ive tried this on a fresh install, which also removes markup. Has anyone else filed an issue yet, or is this some unique bug due to an unusual configuration. Im running this in a test install on php 5.1.1 through FastCGI and Apache.