Upgrading Drupal

I'm using the taxonomy access control and menu per role modules to control access to content on my site. Neither of these modules support Drupal V6. Is there any chance the functioning these modules provided is now native to V6? I was hoping that I wouldn't need to modules anymore. Thanks!

I've attempted many different times to get 5.7 to 6.0/6.1/6.2. With 5.7, it works wonderfully. However if I attempt to upgrade from 5.7 to 6.0 it simply asks me to install and not upgrade.

I'm out of ideas and haven't found any posts with this issue. Is there some obvious issue that anyone can think of?

All of the modules are marked as 5.7 and using the same MySQL connection string I'm unable to do the upgrade. I just prompts me to install it if I use 6.0, 6.1 or 6.2.

Any help is appreciated.

I am attempting to upgrade from 4.6.2 to 6.2. (Yes, I know I should have upgraded many times before, but this is my situation.) I followed the steps in the documentation, but when I ran upgrade.php, I got a blank screen and op=info. I followed the advice on this page - http://drupal.org/node/112884 - and turned error reporting on, as well as setting higher memory levels. I now get these errors:

Warning: Unknown column 'serialized' in 'field list' query: SELECT data, created, headers, expire, serialized FROM cache WHERE cid = 'variables' in /home/nceprcf/public_html/ncepr/drupal/includes/database.mysql.inc on line 128

I had a problem with cron not running after upgrading from 4.7 to 6.2 (with a hop thru 5.x). The log kept showing the error "Cron run exceeded the time limit and was aborted.". I could kick off the cron.php script, but it would always come right back with the error.

I checked php.ini it allowed longer running scripts, so the error was spurious.

Since the error message only meant that cron.php was crashing (not taking to long), I thought it might be a problem with one of the modules failing. I only had a few modules running, other than core and the standard ones, so I kept disabling them until cron.php would run. I found that if I disabled search, cron would run.

I had cut the number of items to index down to 10 in the search settings, so it seemed there was some problem with content on my site as it went thru search. I had too many entries to go thru things one at a time, so I decided to reset the search tables and see if search stopped on a certain node and I could then tell what was wrong.

I'd recommend you do a backup of your database before trying anything like this. Also, using something like phpMyAdmin might save you a little trouble.

I dropped down to the MySQL command line and reset all of search tables by hand:

mysql> DELETE FROM search_dataset;
mysql> DELETE FROM search_index;
mysql> DELETE FROM search_node_links;

Ok, this is the situation. I've neglected a Drupal install for quite some time now which has 30 contributed modules installed and it has over 280 registered users, over 3000 nodes, 11,000 url aliases and the database is over 200MB. This version is 4.7.3 and still going strong, a testament to the resilience of Drupal, I'm surprised that I've escaped any of the security problems too, (knock on wood).

I'm in the process of upgrading a 4.7 installation to 5.x (so I can upgrade to 6.x). My 4.7 installation used the flexinode module, and the event module on top of flexinode, to maintain a calendar of events. I would like to maintain a calendar in the upgraded system, and migrate all the old event content into it. But I am perplexed about the relative roles of CCK (in particular CCK date) and the 5.x event module (which appears to be backward compatible with 4.7) and calendar modules as replacements for flexinode and 4.7 events. 5.x has no flexinode module.