Version 5.x is not supported

It means I don't have any more sites running on D5, so I'm not supporting it in 5 anymore.

Hi,

there are still people out there using D5 with blocked upgrade paths to D6, so at least I need the D5 release. Since this is a very fine module giving excellent results, and running stable for months, please keep the D5 release available.

Unpublishing the D5 release causes all kinds of trouble; /admin/logs/updates complains ("The installed version of at least one of your modules or themes is no longer supported. Upgrading or disabling is strongly recommended! Please see the project homepage for more details. See the available updates page for more information") and sets the module's status to "Not supported!". That seems to invoke other mechanisms I don't yet understand fully, but in the result this breaks at least one of my sites, see Modules list empty.

I'm not using the "Similar Entries" block in a sidebar but integrated it into my theme ("Slash"); somehow due to unpublishing the recommended release for D5 this caused to disabled all modules to become disabled (and listed at the "Uninstall" page!). Since the modules - including "Similar Entries" - are no longer available, all Templates with the embedded block break, and with the Templates the whole site breaks. I have a similar configuration running on D5 sites; this problem so far only occured at one of them, however it simply seems a matter of time until the other sites are affected also. And yes, the problem is directy connected to unpublishing the D5 release, and yes, I can reproduce the error (switching to "Garland" without modifications gives me the (disabled) modules back, after enabling them again and switching back to "Slash" the modules list again empties).

I'm re-opening this issue due to the strange error caused by unpublishing the D5 release; until I've understood why unpublishing a module's release can cause this kind of damage, I'm considering this as "critical". Please consider an alternative to completey unpublishing the release. If you don't want to support the release anymore, maybe you can make a note at the project page, stating that installing the module on D5 isn't supported by you anymore and that the user will be on his/her own. Since the module is stable and cannot be replaced (no other modules comes even close to the quality of the similar content harvested by "Similar entries"), maybe it will suffice when the module becomes community supported - there are lots of other modules that even have been completely abandoned (like "Amazontools") which are handled similarily.

I fully understand that the problems described above are not caused by your module directly (but by some other mechanisms in Drupal I still have to figure out so I can post a more appropriate issue in a more appropriate place), and for that I apologize. If you feel that it is asolutely necessary to unpublish the D5 release and don't agree that the problems mentioned above rectify to mark it as a critical issue, please feel free to set it to a more appropriate status (like "won't fix).

Thanks & greetings, -asb

PS: This issue might also apply to one of our other modules (Atom) that has also been unpublished yesterday; I've yet to investigate this further.

The supposed automatic disabling of your modules is some freakishness I have not heard of and is not related to similar module being unsupported in 5. I suggest you merely re-enable your modules that got disabled and tell whoever disabled them to stop doing that.

As for your use of "unpublished," you are incorrect. All releases of the similar module, including 5, are still available on http://drupal.org/node/25974/release.

Hi,

> I suggest you merely re-enable your modules that got disabled [...]

As stated in the issue Modules list empty referenced above, the Modules list is empty, thus there is nothing I could re-enable; cf. attached screenshot taken from /admin/build/modules. Since the only change "update status" registered yesterday was your unpublishing respectively changing your module's status to "Not supported", there are not so many probable causes for this vanishing of my modules. If the changed status of the "Similar Entries" module did not cause this directly, it might have triggered some mechanism in the "update status" module.

Regards,- asb

You're wasting a lot of time arguing with me. Software gets old and unsupported. Modules do not get disabled because they're unsupported unless you've done something to make it do otherwise. You're better off spending your time figuring out why your site is not loading your modules page. I disabled 5 support knowing the implications of ugly red notices on users' sites and it was no accident.

If you really think update_status is blocking your modules page, execute this SQL query to disable it on your database:

UPDATE system SET status = 0 WHERE name = 'update_status' LIMIT 1;

Or if you're not sure which module might be doing it, disable them all with

UPDATE system SET status = 0 WHERE name NOT IN ('block','filter','node','system','user','watchdog');

I second (or third) the motion to keep the 5.x version of the module active.

Even if you don't support it anymore (bugfixes, etc.), there are plenty of people who still run D5 sites because they can't upgrade to D6, and this module is still very useful for those people. You can put a note on the project page specifically saying "I'm not supporting 5.x anymore, and if anyone wants to be a co-maintainer of 5.x please contact me".

PLEEEASE reactivate 5.x!

Eric, I accept. CVS access granted.

I am also with you. Version 5.x is needed!!

It won't last long. Please visit admin/logs/updates/settings and learn how to disable notices per module.