Upgrading Drupal

Hi
i have updated the core . But after upgrading the aggregator module remains sam ein 7.16 .in the reports section i am getting as follows

Drupal 7.18

Drupal core update status Not secure! (version 7.18 available).

Any idea?thanks in advance

I don't mean any of this as a rant, but after working on numerous drupal 6 to 7 upgrades, I feel like offering a suggestion I thought of earlier today while working on yet another seemingly needlessly complicated migration.

There are no shortage of posts that many are concerned about the path of drupal generally and some are shying away due to poor upgrade paths and not agreeing generally with future roadmaps and the work this creates for developers, module maintainers, etc. Personally I think drupal is quite good, those with limited dev experience can do great things with it, those with strong programming skills can still benefit, but upgrading in particular is often a nightmare except for the simplest of sites. This is not entirely uncommon with -some- other cms systems however.

As drupal really grew with d6 and now more with d7 many of the larger adopters have yet to go through an actual version upgrade and when they do they may or may not change their opinions/adoption of drupal - this part only time will tell... In the last few weeks I've learned more and more (in part by looking at alternatives with similar feature sets and better backwards compatibility) about where drupal is heading and I'm mostly intrigued. That said, I have one interesting suggestion....

I've been using drupal for 3 years now and although I have had errors on updates before, I've always managed to get passed them. The site has civicrm installed but apart from that isn't very complicated. At various times I have added a number of modules but I usually get rid of them when I find they don't do what I want.

All of the information below is from the Wampserver version of my site.

I tried upgrading drupal a couple of days ago (6.26 to 7.18) and it failed, although I think I followed the instructions precisely. I was able to restore it to the earlier version and tried again today.

This time I disabled even the core modules (except Database logging & syslog), and the Civicrm root module (as advised by Civicrm). Everything appeared to run smoothly until very near the end of the upgrade process when it gave me this message:

I seem to have become entangled in trying to do a major version upgrade (on a bit of a Frankenstein project to boot), and wondered if anyone could set me on a better path.

My backup is done, I thought my mess of contributed modules was all spiffy and up to date, and I am running the lasted version of 6, so I thought I would be in a good place to try the drush site-upgrade command (referred to as magic in some posts ) but while I get to Stage 1 of the status report I seem deeply stuck there. The list of possible issues is LONG, so I don’t want to jam up a poor generous soul willing to read/chat/respond with them all but (BUT….) prioritizing them is a little beyond me, I think.

Possible big picture show stoppers include: I have read site-upgrade is not good for remote set ups, and not all drush commands work w Windows (though I think I downloaded the sup stuff and charged on w blind hope anyway). So maybe I’m dead in the race before the gun.

Some details:
Running D6.27 on a hosted development space (which I have fallen fast in love with) optimized for Drupal running Drush (5.1)

I update my site from Drupal 7.15 to 7.18 today and after updating, I am able to see the frontpage and the aadmin page of my website (subsite). Apart from this, I am unable to access any other pages of this site.

When I try to access the pages, I get this message
404 Not Found

The resource requested could not be found on this server!

Hi,
I've been with Drupal for 5 or 6 years - working on an XP laptop and an old WAMP instalation, and never had such a problem. Now I've finally built a powerful desktop with Windows7 and WAMPserver. I've exported all of my old 43 databases and imported them into the new WAMPserver. The results are unpredictable at best:
the Drupal 5 projects work like a charm (D5 is as simple and reliable as an AK-47)
the Drupal6 projects work on and off (I'm assuming that admin_menu module is causing some hickups, but it'simpossible to get to /admin section at all)
BUT Drupal7 projects are not working at all ! In most cases of D7 I get this:

Error
The website encountered an unexpected error. Please try again later.
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'drup7.semaphore' doesn't exist: SELECT expire, value FROM {semaphore} WHERE name = :name; Array ( [:name] => variable_init ) in lock_may_be_available() (line 167 of C:\wamp\www\drup7\includes\lock.inc).
Uncaught exception thrown in shutdown function.