Update Status - Themes

themes will need some kind of .info file like modules have in order for that to happen. So this won't happen for Drupal 5 -- maybe if Drupal 6 gets a .info file for themes we can do it.

can't make progress on this until there's an issue in core and/or the project packaging scripts to support .info files for themes...

As a theme developer i'm open minded to this. I don't need to wait for Drupal 6. I have no problem to put a .info file inside the themes root directory. Then you are able to implement such a check... your module does not required to wait for Drupal 6 regarding this nice feature!

Are you able to support the theme check in v2.0?

Please, add an optional URL parameter for non-GPL themes... i'd like to check the update_status for 20 Themes licensed under a Creative Commons license and i don't like to build an extra module for this... :-)

Sorry, not under Drupal 5.

Ups, i thought update_status v2.0 will go into D6 core? So it was more an D6 question...

We're changing the protocol and then we'll integrate it into core, but 2.0 is still a standalone product for Drupal 5. Hopefully what ends up in core will be largely the same, but will likely be integrated directly into system.module

And yes, in Drupal 6 themes have .info files, so themes will be covered too.

given that the D6 port (http://drupal.org/node/153503) will be committed any day now, it's now possible (and important) to get this feature working. however, i'd consider it still blocked on http://drupal.org/node/147000, so i'm still leaving this "postponed" even though i'm bumping it again. ;)

Fixed in my D6-port (renamed to update.module for inclusion in core) in my sandbox:

http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/dww/update/

Better yet, see the patch where this is moving into core at http://drupal.org/node/94154#comment-266414 (comment #25).

@dww: i know there is no official .info file for themes in D5, but aren't we able to backport this small thing only for update_status? If the theme developer likes to support update_status (like me), i'm able to add this .info file to my themes without any harm and give the users a big benefit *today* and not making them to wait for D6 and an possible core update (with some custom hopefully available contrib modules) in 6-10 months?!

nope. it's actually a bunch of changes to the source and UI if you look at my sandbox. i don't want to go through the trouble for the tiny handful of people who want to host themes not on drupal.org. if you want to hire me to do so post-freeze, let's talk. otherwise, "won't fix". that's life...