Port to Drupal 6.x? Remove per-theme settings?

I had no idea anybody was using this module. :-p

It should be straight-forward to port it.

Is there any work underway to port this to Drupal 6? This is the last module that I would need to upgrade a couple of sites to Drupal 6.

-Brian

Ok, looks like there's good usage of this module, so I'll port it to Drupal 6.

However, the more I've played with the code, the more I realized that having per-theme settings is difficult to get right.

The per-node-type settings are very useful, but I'm not sure that per-theme settings are that useful. When I first wrote this module, I was wildly optimistic about giving all sorts of flexibility. But it makes the code hard to grok and ugly-looking.

So can I get some opinions about removing the per-theme settings? i.e. The admin/build/themes/settings would have Theme Settings widgets and those settings would affect all themes (and admin/build/themes/settings/THEMENAME wouldn't have any Theme Settings widgets.)

i believe that the "string overrides" module for d6 replicates all of this functionality, as well as "form edit" - between those two you can replace strings, manage the replacements in a central admin screen and also move the elements of forms up and down by weight, an also edit text within forms not touched by strings directly (per the output)

before you spend time porting to d6, you may want to take a look at those two other modules already out on d6 - feels like identical functionality (though form edit is really quite useful for non-stringed output like little text bits below boxes or whatever)

@JohnAlbin
+1 For Port w/ Per Node Settings but not Per Theme (never used that one anyway)

@zilla
String Override is only adequate if your string changes are site-wide, which doesn't work if, say, I want "read more" replaced on only my podcasts content with "Listen >>". Plus Theme Settings allows for relocating of read more and other elements which is not duplicate functionality.

subscribing

subscribing :-p

sub

I've rolled this functionality into a patch over at #538376: Logic problem with per-type settings and isset() Assigned to: mikey_p.

#538362: Initial port to Drupal 6

Just for the record.....

Are there plans for a proper release?

#538376: Logic problem with per-type settings and isset() has been committed.