Duplicate Module?

Well, not really. IEDestroyer is warning users of IE, regardless of the version, and asking them to switch to Firefox. It also sets up referral links to Google program of promoting Firefox. Which is all good, but...

IE6_warning only phases out users with IE6 (not all IE versions). It suggests different browsers to download, and not only Firefox. It is in this sense less aggressive than IEDestroyer. We use it on large Drupal websites, to invite users to upgrade IE6, nothing more.

Further more the first module is abandonned and has only a dev version.
http://drupal.org/project/iedestroyer

There is also the Browser Support module... it could use updating to use jQuery, but it's pretty nice all in all. And there is a patch for Drupal 6 also.

http://drupal.org/project/browser_support

_{Well, not really. IEDestroyer is warning users of IE, regardless of the version, and asking them to switch to Firefox. It also sets up referral links to Google program of promoting Firefox. Which is all good, but...}

IE6_warning only phases out users with IE6 (not all IE versions). It suggests different browsers to download, and not only Firefox. It is in this sense less aggressive than IEDestroyer. We use it on large Drupal websites, to invite users to upgrade IE6, nothing more.

Um .. so the difference between the two modules is the phrasing of the wording it uses when doing the same job?
So with the option to change the text there is nothing to choose between them?
:-(
Duplicated Modules Hall Of Shame

OK, so for clarity, please just add an explanation and reference to the deprecated module on the project page and we can eliminate confusion.
This is not a criticism, it's a request for clarification for users trying to choose modules

As per http://groups.drupal.org/node/19573

IE6 is not stritcly speaking a duplicated of ie destroyer. Our module include :
- selective matching of the version of IE (only ie6)
- javascript detection of the User Agent (= work with cached pages)
- user can definitively cache the warning message (cookie based)
- ported to D6 (to come on the d.o project page).

A solution could be to add a configurable detection of all ie versions in our module to replicate the old ie destroyer module functionnalities.

Further more on the page of IE destroyer you can read :
THIS MODULE IS ABANDONED. THE DEVELOPMENT VERSION WORKS, BUT DO NOT EXPECT ANY BUG FIXES OR NEW FEATURES UNTIL THERE IS A NEW MAINTAINER.

It is more than a wording issue; the new module is quite different, filters out IE6 only, works with cached content, records the message's status in a cookie, and not setting any kind of referral links. Hope this clarifies the issue.

here is what I think:

1. Yes, the two modules discussed are currently different. (this one and IE destroyer)

2. The main problem we all need solved is browser support and how webmasters can:
- urge/warn their users to upgrade their browsers (not only IE is involved here - older versions of all browsers too )
- if the site owners/developers feel they have had enough bullshit with IE (6, 7, 8) or any other browser they are free to warn their users (with several levels of seriousness) and assist them in installing another browser ... Or maybe some sites would love to just say something to their users that use Chrome for example ....

So 1 + 2 =

3. The problem needs a general solution - please remember that this is Drupal here
- we build API-s = separate the task to sub-levels and on each level the job is done as it should be....
- we collaborate on these API-s

So I would love it if all the 4 modules think of a way to solve that problem the best way and with the least effort.

(I propose one module with different types of settings and operation - after a commonly shared browser detection code the module decides what to do based on the settings ... (show a block/ JS popup / a whole page banner that can/cannot be ignored ..) )

Module | drupal verision - usage

1. http://drupal.org/project/ie6_warning - 5.x. - 2
2. http://drupal.org/project/ie (ie notify) - 6.x - 34 (maintainer happy to collaborate with others and close his module)
3. http://drupal.org/project/iedestroyer - 5.x - 22 , 6.x - 56 (abandoned for now)
4. http://drupal.org/project/browser_support - 5.x - 20 (patch for 6 pending)

NOTE: More usage does not mean anything.
REQUEST: If someone knows of a relevant module I miss - name it.

So, all those 4 are variations of the same idea and if the maintainers have collaborated from the start and have separated things in API-s there wouldn't heve been the need for me to cross post this on 4 issue queues.... Not that it is not fun though...

Till later - and remember - if 4 (or 3 or 2) projects go into one - credit to the developers will be given easily by naming and linking to everyone that deserves it on the project page... So personally I am never scared of shutting down my project to contribute parts of it to another one.... (recently this happened with drush_mm merged into drush (actually on idealogical level - not much on the code level - but drush_mm played its great role ) )

CHANGELOG: 09/04/20 - 12:13 - added details to the list of 4 modules

I'm the maintainer of IE Notify (http://drupal.org/project/ie). I'd be more than willing to submit a patch to any unification efforts and quit maintenance of IE Notify in favor of that. Subscribing :)

As things are going we need to figure out : are we going to co-maintain a brand new all-in one project (with submodules if we decide) or migrate some code to an existing one - I suppose the browser_support module. It may need a complete overhaul ...

other opinions?

I am now the maintainer of iedestroyer; happy to collaborate with anyone. It's a tad ridiculous that there are four modules doing the same thing. I think browser_support may be the way to go. Much as we all like to bash IE, it might be more useful to make the module more generic and leave that option up to the user.

Just curious, has anything been decided as far as merging the IE modules?

Subscribing interested in this also, is http://drupal.org/project/browser_support chosen to be the umbrella module?

greetings, Martijn

The project has been marked as abandoned.