How to upgrade subtheme from 1.x-beta?

Same issue here....

Found the solution:

Go to the .info file of the sub theme. Change at the end of the file the line:

version = "6.x-1.0-beta3"

into

version = "6.x-1.0"

Then all notices of updates are gone.

@joostvdl: That's one step. More may be needed.

I am swamped right now. I only just had time to release 6.x-1.0. I probably won't have time to write upgrade docs until after Drupalcon DC in March.

Subscribing...

I had the same problem upgrading Zen 6.x-1.0-beta3.

I have a subtheme that was created from that version and after updating to Zen 6.x-1.0, the version for the Zen theme shown on the Available updates-page didn't change, and continued to show in red with "Update available" next to it. The right version was shown on the Themes list-page.

Doing the solution in #374832-2: How to upgrade subtheme from 1.x-beta? seems to have solved the problem, but is it as simple as that? Are there any other merging steps required?

Subscribing!

Subscribing as well.

I don't have a subtheme, I'm just running Zen classic for now, and I am having the same problem with the "Update available" not going away.

EDIT: Turns out, big surprise, it was user error. I went back over my folders and realized I unpacked Zen in the modules folder. Derrrr!!! Deleted that and unpacked in themes and all is well.

Something that would improve subtheming in Drupal. When a subtheme is in a separate directory instead of a subdirectory, list subthemes as separate themes in the themes update list. Have them display a prerequisite in the same way as modules list prerequisites. The subtheme could remain 1.0-beta3 and list Zen 1.x as the prerequisite.

I do not know how this could be added to Drupal. Suggesting it as a Drupal enhancement would push it out to Drupal 7 with the Drupal 6 version backported in 2012.

While we are fixing up the themes list, modules should be able to load CSS and js through the .info file the same way as themes. Module and theme processing could share more features and more code.

Subscribing ... I have the exact same code in my staging and production environments. In staging, the update message went away, but it still exists in production. I still have 6.x-1.0-beta3 listed in my subthemes, but not in the base zen theme, which should be the only one that matters. This is very strange!

So - any advises on how to correctly update? Is it enough to just change the sub theme's version information (http://drupal.org/node/374832#comment-1260907)? Or are other steps neccessary?

I upgraded to D-6-10 and at the same time upgraded CCK and the Zen theme yesterday. I waited until yesterday becasue when the first of the three was flagged, due to the current passion for upgrades where minor patches would suffice within Drupal, I knew there would be at least a couple more very soon.

Since yesterday's reinstallations I've had the same problem as above, fixed thanks joostvdl, but I also lost navigation and login/logout in the admin interface. I was logged in at the time and have nowhere to log out. Luckily this site does not have "members" but it's a hell of a pain nonetheless. To get around I have the main admin page open, luckily, so I can get where I want to go but have to use the browser back button to get back before I can go anywhere else. To get there in the first place I go to mysite/admin and not mysite/user, which is crippled altogether.

Oddly, everything else works.

I'd really love to see an instruction or a tutorial for this, too. Anyone? Please?

Closing this old issue since the 6.x-2.x branch is out, and 7.x-3.x will soon be released.