Upgrading Drupal

OK i'm a little confused here regards when to run update.php. On the modules page it says :-

It is important that update.php is run every time a module is updated to a newer version.

So say someone fixes something in the code, should i run the update.php on replacing the module ? Is it good practice to run everytime a module update (code or otherwise) is uploaded ?

The reason for the confusion is that when clicking update.php you get a statement like :-

i have gone thru the forums & checked the handbook, and i'm not finding anything that helps.

the .htaccess file that came with 4.6.x worked just fine; i'd upload it with the rest of the files, enable clean url's and hey-nonny-presto.

with 4.7.2, i do the same thing, and diddly-squat. i've tried the various modifications, everythng short of the apache mods, but a) i have no access to that (few of us will) and b) if it worked before, why isn't it working now?

I just notice that a whole bunch of fields in a number of tables are now varbinary ... I think I read something briefly about the upgrade process converting varchar to varbinary and then back to varchar for utf-8 support. Maybe something went wrong in my upgrade from 4.6x to 4.7.0, but fields like node.title were varbinary when I just checked because we were encountering a problem with case sensitivity during selects. I changed the field back to varchar, but it looks like the content is still case sensitive. Any ideas??

Thanks!

I just updated to from 4.6.7 (4.6.?? I think it was 7) to 4.7. Most everything seems to be working fine except for what's most important, the content. On the main page (/node/) and the group blog (/blog/) every entry contains simply "n/a". If I try to access the content directly via administer>content, I can see all the content titles and authors and they all show as published, but clicking a title gives me an Access Denied page though I'm logged in as user1.

Greetings,

Looks like this is a popular problem. I have disabled all the modules, logged as user id 1, removed all by files directory, copied new Drupal distribution, called the update.php script and all the hell broke loose. The missing fields errors, and so on, and when I manually renamed them, the site used to display 'Page not found'.

MySQL: 4.1.19, PHP 4.4.2 (CGI mode)

somewhere in the late beta cycle, something went awry with the parsing of ampersands in blocks rendered with input content of full html.

take this bit of code: