Support D6 for as long D6 core will be supported

Agreed.

If the 6.x version isn't being supported, but is still OK to use, please could you re-publish it as a non-recommended version?

Just so I don't have to keep ignoring the "Project not supported: This project is no longer supported, and is no longer available for download. Disabling everything included by this project is strongly recommended!" message.

+1 - Atrium time tracker depends on views calcs and so I cannot disable it.

I would be really grateful if you could re-publish to avoid me having to ignore message.

+1 for re-publish it as a non-recommended version
It forces my site keep displaying the "Project not supported" error and is very annoying.
Putting it into non-recommended version should be enough to keep people from using it in new projects.

Dropping support for a fully working project doesn't make sense. I mean, if it was broken and the maintainer actually had to do work on it in order to maintain it then so be it. But doing it like this is simply not nice.

Any comments?

totally agree to grey_
Putting it into non-recommended and then stop all developments on 6.x except security fixes should be enough

+1 for keeping D6 version a published non-recommended project.

+1 for keeping D6 version a published non-recommended project.

+1 for leaving the D6 branch & releases available, if unsupported.

Can I pledge a few € or $ to persuade the maintainer(s) to at the very least remove the message "Project not supported: This project is no longer supported, and is no longer available for download. Disabling everything included by this project is strongly recommended!" until D8 is released?

I would also pledge.

somewhat off topic; but wouldn't it be nice if the update module had a method to ignore certain modules? I mean this is really what most people are asking for here isn't it - more so than maintaining an old release of a module which works just fine?

it is up to the maintainer to not want to support an old version of a module and since having it listed on the project page means you can still post issues to a rel; not really any other way to do this. but pretty annoying for the update module to be all or nothing... "sorry, if you want to know about security updates then i will annoy the hell out of you forever if someone decides to stop maintaining a module."

and yes, i get that maybe this is dangerous.. what if someone "ignores" a module by mistake.. omg.. such a huge security violation! so how about a weekly or monthly reset on the ignores? security isn't the be all that people think on d.org... it could be months or never before the d.org security team finds a security hole in a module; which typically are not critical.

There is a module for ignoring module updates: https://drupal.org/project/update_advanced

Mike, even security fixes take developer's time. So i guess you would always need a maintainer (which i get is part of this thread); but you wont always get that for every module (like i guess this one doesnt have yet).

But yes, if not listed as supported i guess project misses the "free" security team analysis. Thats open source.

@fonant - thanks for the module tip; will check it out.

Personaly I would like to see a reaction from the maintainer(s) of this module why the D6 version was dropped.

Meanwhile… Does anyone know any good ways to silence the non-support notification from this module?

I want to upgrade my sites to get off Drupal 6 but am unable to because the upgrade process seems virtually impossible for sites with complex functionality in a way where our data is preserved. I do not understand pulling support for Drupal 6 in ways such as this when there is seemingly no way to get off Drupal 6 without a complete site rebuild. This mindset of forcing people off Drupal 6 by ending support is putting a lot of us in a seriously bad position.

From the maintainer of this module in several closed / won't fix D6 issues:

The D6 version is no longer supported.

e.g.
https://www.drupal.org/node/1210038#comment-8486337
https://www.drupal.org/node/1363650#comment-8486353
https://www.drupal.org/node/1215582#comment-8486343

etc...

... but no reason ever given.

- Installed 6.x-1.x-dev downloading from the releases list. Still it did not do the job as expected... dont know why.

So I had to do call this function in a view header footer:

( feel free to adapt and debug via print_r() )

function __views_calc() {

$v = views_get_current_view();
$r = $v->result;

if ( ! empty( $r ) ) {
  foreach ( $r as $i => $vals ) {
    $sum_auto += $vals->node_data_field_date_field_hours_total_computed_value;
    $sum_man  += $vals->node_data_field_date_field_hours_total_value;
  }
}


echo "
Sum Hours (auto) ${sum_auto}h<br />
Sum Hours (man.) ${sum_man}h ";



}

+1 for keeping D6 version a published non-recommended project.

FYI: I'm the (new) maintainer of the chart module, and despite that this module is commonly perceived as "nearly end of live" (because of Google's deadline imposed), I'm working on getting it in good shape again soon.

The D6-version is used in +5K sites today ... still. One of its submodules of it (in the D6-version) depends on this module also. Which is why I'd rather want to say something like 5.000 * 50% = + 2.500 (instead of just +1) ... So if the D6 version of 'this' module would become published somehow again, it would help me a lot also (i.e. I wouldn't have to spend time on coming up with an alternative for this unsupported dependency).

PS: Please don't challenge me to become the D6 (only) maintainer of this project ... Before anybody wants to consider doing so, checkout #2368793-29: Chart 2.0.

Update about my prior #31 .. I just discovered that the D6 version of charts (which is not all the same module as chart ...) ALSO depends on the views_calc module. Be it that it is only a "weak module dependency", as you can see around here. Guess what: I am also the maintainer of charts these days.

The D6 version of charts is still used in nearly 600 sites today, while the D6 version of Views Calc is used today in 2.327 (EUR fmt!) sites. By considering the number of D6 sites using either chart or charts, I believe that "nearly ALL" sites using the D6 version of Views Calc, or also using either chart or charts. If there is anybody following this issue who does not use either chart or charts, please let us know about it.

Because of this new discovery, I would like to rephrase my PS in my #31: "Would you consider me to become the D6 (only) maintainer of this project?" ... Even if it was only to prevent me from "cloning" what is needed from this module into some new submodule related to chart and/or charts (which I'm considering adding in module csvchart, for which I'm about to release a D5-upgrade also).

Another option (which I'm not sure if it is possible), is to split the D6 and D7 version of the Views Calc project (and its D6 related issue queue). Or moving (instead of splitting) it to the csvchart module. Anybody familiar with what is possible to achieve such split or move?

What could be a possible explanation of the recent increase in the usage statistics of the D6 version of this module? Which as of today is still not showing up on the project page.

A hidden release that until recently was (still) used in about 50% of the D7 users, has now evolved in "about 200% of the D7 users" ... I don't understand ...

I've contacted Karen about this. If there is no response within a week please ping this issue again.

@dddave: any news from your side? I haven't seen/heard anything, except my reminder in my calendar today (related to your #34) ... Suggestions about how to move forward now? FYI: my offer (in red) in #32 still stands. Maybe I should add to that "for as long as D6-core continues to be supported" (and slightly adapt the title of this issue also)?

PS: I like the "legacy maintainer" title from @mgifford).

I've not heard back from Karen. Therefore I've made Pierre.Vriens co-maintainer to deal with the D6 support.

Thank you David! Guess what kind of update I just applied to the supported releases, right ... 6.x-1.3 is marked supported again (+ related dev snapshot ofcourse)! With that, I hope the over 8K D6 sites are "happy" again.

What I'm not sure about yet: what to do with the 6.x-3.x-dev version (used in 139 sites)? Anybody out there who can help me understand/decide please?

To all participants in this issue: thank you for your patience. I may need some time to come up to speed, any help, like pointers to existing docu, would be greatly appreciated ... same for docu contributions ... Where do we start?

PS to Karen (if she ever finds this comment): just trying to help, OK?

Thanks a lot for supporting this module again!

Speaking as the owner of one of those sites, it would be nice to have a 6.x-1.4, even if it was just the -dev version repackaged (though I suspect there are a few fixes that have been suggested since the last release of -dev). The reason we're on -dev is that -1.3 was so old, even then, and the -dev version was clearly larger.

Also, the -dev version is still showing up as "Not Supported" on our Available Updates panel, even though the date is the same as the last available date (2013-Oct-18).

@GreenReaper: thanks for the feedback. I agree with you on such 6.x-1.4 (= repackaged -dev version, etc). Give me a little time to see what I can do for that.

Also thanks for the "still showing ..." hint (I didn't know, or I wasn't sure about that yet). Not 100% sure if I now "solved" that "still showing", but I just applied a modification like so (all 6.x related, and only 6.x, that "my" territory, remember?):

• For 6.x-3.x-dev: I just enabled "supported" and "show snapshot release"
• For 6.x-1.3: I already enabled (some days ago) the "supported" and "show snapshot release"

Please let me know "how close I am" with these changes (i.e. if there is anything "still showing" that should no longer be like so, ok?

I'm still getting this after a manual refresh:

Views Calc 6.x-3.x-dev (2013-Oct-18) Not supported! error
Recommended version: 6.x-3.x-dev (2013-Oct-18)

I don't know if there is some kind of caching on the Drupal side, though. I can check again later

My views_calc.info file is:

name = Views Calc
description = This module will allow you to add calculated fields to views tables and compute columns of numeric data in a views table.
core = 6.x
package = Views
dependencies[] = views

; Information added by drupal.org packaging script on 2013-10-19
version = "6.x-3.x-dev"
core = "6.x"
project = "views_calc"
datestamp = "1382152442"