Feed aggregator

I want rip out the suggestion classes for one of my themes - at first I thought this looked strait forward and could do something like this in themename_process_html()

$classes = str_replace(theme_get_suggestions(arg(), 'page', '-'), '', $classes);

This removes the page-arg(0) bit but nothing after it, see the screen-shot as to what is left behind.

Could someone point out what I'm doing wrong here, since this is using the same function that is being used to build these classes.

The screen shot is taking when I am on node/1, so the classes added by Drupal are page-node, page-node-, page-node-1

I created this issue to focus on some small changes to ThemeAPI that will make
D7 theming much more flexible and consistent. This issue is related to #812796
and #364470. I know I'm late. But, as for D7 user I think that without small
improvement, D7 will look like incomplete.

My goal is to create D7 theme using only css and template.php files. For D6
themes I always changed following things:

- submitted message (both for nodes and comments)
- comment title (with number of comment included)

In current D7 ThemeAPI I cannot change this variables without using tpl files.
Comment title is hardcoded, submitted message is hardcoded. I think, creating
translation for submitted message to change how it looks, is not the way it
should be used. I cannot achieve my no-tpl-files goal with hardcoded variables.

What I propose is to:
- make comment title as variable (like I did in patch in #812796, for
comment-wrapper.tpl.php) - now I have to use comment-wrapper.tpl.php to add,
for example, number of comments
- do not hardcode submitted message (if not an old $submitted variable (see
#364470), then, maybe something like theme('links'), which is also quite
difficult for new Drupal themers, maybe something like a theme setting).

Any other variable can be adjusted in template.php, thus I think leaving those
I mentioned will make D7 ThemeAPI incomplete.

Drupal.org will soon be moving to Git, and will provide two types of repositories:

- "development repositories", which are basically what we have in CVS right now
- "release repositories" (AKA: "stable" repositories), that contain only released versions of the projects, one commit per release

What about integrating that as a package handler for Drush PM?

Hi there
Very interesting module.
In the installation instructions, you mention "delayed payment".

I don't see anywhere in Ubercart where this can be configured.
Any tips?
Does it only work with certain payment methods?

Regards
Alan