module browsing pages ignores release publish status and 'enable releases' settings

never mind. I was able to unpublish the project and that removed it from the modules page.

Dub

Just to update this in case anyone else is having the same problem...

the option to disable RELEASE LINKS when you Edit a project ([PROJECT NAME] -> EDIT -> RELEASES doesn't work. When you disable releases, the DOWNLOAD link is still active when viewing the modules page.

I'll raise a seperate issue about that. Just thought I';d mention it on this issue as it's related.

It appears that the only way to disable the DOWNLOAD link for a module is to UN PUBLISH the release node. (go to [project name] -> EDIT and under publishing options, disable PUBLISHED)

Dub

what are you talking about? ;) there's no such setting on the "Releases" subtab of the edit tab on project nodes. no wonder it doesn't work. maybe you're talking about this checkbox:"Display snapshot releases on project page"

Nope...I was referring to the ENABLE RELEASES option when editing a PROJECT. If you DISABLE RELEASES, the 'DOWNLOAD' link is still live.

I have attached a screenshot of what I see when editing a project.

Maybe it's a wording thing..but, disabling an ENABLE RELEASES option would give most the impression that you're disabling RELEASES from the project page. Which would be very useful if you don't want Drupal users to download old versions of a module and especially if you're having difficulties branching and tagging.

Anyone else stumbling across this issue, please note that the only way to disable module download links is to un-publish the project page. Un-publishing RELEASE NODES doesn't make any difference to the module page.

As an example, I was completely baffled yesterday because I had unpublished the RELEASE NODES for a project (to avoid Drupallers downloading old releases of a module while I was working out the new tagging/branching system) thinking that it would disable RELEASES and subsequently the DOWNLOAD links.

The DOWNLOAD link and releases disapeared, as they should, from the project page, but, if a person viewing the module page was filtering by a particular version, they would still see a download link for the unpublished RELEASE for that version.

I'm still not sure what the advanced options (see screen shot attached) actually do. My guess is that the code that generates the module page is ignoring whatever you have set for ENABLE RELEASES, i.e. it doesn't check to see if releases are available for a given project.

Anyway..I hope that helps others...that stumped me for ages yesterday and it wasn't until I went on to the #drupal channel that the guys there helped me out with the tag/branching problem.

Dub

Sorry for opening this back up..but, I think this needs to be addressed.

An example of the 'download link' problem I'm doing my best to flag here is as follows:

1. If you go to: http://drupal.org/project/Modules/name
2. filter modules by version 4.7.x
3. scroll down to the Front Page module
4. You should not see a DOWNLOAD link for front-4.7.x-1.0.tar.gz because that Release is unpublished

I have added in a temporary note that most Drupal users should notice, until the correct release for Drupal 4.7.x is picked up by the site, but, I think this is pretty important for a number of reasons:

1. Most Drupal users would tend to use the module page to download modules and might not click through to the FIND OUT MORE link and discover that there are more recent releases
2. Most Drupal module maintainers, I guess, would assume that when they add a new release for compatibility with a specific Drupal version it will be picked up by the module page.
3. The result is Drupal users inadvertantly downloading old versions of the module and Drupal module maintainers scratching their heads to why old bug reports are being submitted in the issue que for the module

Not sure if that makes sense or not..or if I have missed something, but, I thought it might be better to flag it up here.

Like I said in the previous post, I'm guessing that the code that is generating the module page isn't checking to see what releases are actually published for that project..or whether the module maintainer has ENABLED RELEASES or not.

Hope that helps others.

Dub

please stop changing the title of this issue.

Thanks

Dub

no offense dww...There's no need to threaten anyone by the way.

but I checked with other Drupal developers on the #drupal channel and they confirmed the same observation I made.

I must remember in future not to bother posting possible problems.

Cheers

Dub

must admit, I'm afraid I don't share your same attitude, Dww.

I wasn't looking for help, I was flagging a potential problem to help others. That's what I always thought contributers to Drupal did and I don't really get your "helping you" comment.

I've reset the title of this issue to be more accurate and helpful.

If you have a problem with that, you can go ahead and revoke whatever permissions I have on my account like you threatened earlier. The general attitude and atmosphere on here is sorta putting me off posting anyway so it won't really make much difference.

cheers

Dub

If you're taking a reported issue as some sort of attack on you personally, there's not a lot I can say, Derek.

The only thing I would ask of you is to please please please don't threaten people who are trying to help. There is no need for it.

I've been around long enough to let things like this slide, but, Drupal is dependent on a vibrant community that are encouraged, not scared, to help out. In future, when someone posts a problem, please check it out first to see if the problem actually exists before threatening them or flying off the handle.

As for the new contributions system..I'm obviously too thick to work it out, so don't worry about it.
I'll just pull back from contributing and look for a volunteer to help out in future. I'm not only tentative about updating any modules now, I'm also very nervous about posting an issue for fear of getting my head bitten off.

That's not a condusive atmosphere that enourages the community to engage and get involved. It took me a few hours to check the problem with the modules page and double check on the IRC channel to make sure it really was an issue. I imagine many others who took time out to try and help out might not have the same patience. As I say, I'm around long enough to let it slide, but, the community is too important and I'd prefer to nip this in the bud if I can. So, if you could please try and be less abrasive and threatening in future it would be appreciated.

As for the handbooks, please read the "contributing handbook pages" guidelines. If you are adding a handbook page and *don't* want people posting comments you should switch OFF comments for that handbook page. Otherwise, readers will assume that comments are welcome.

cheers

Dub

Seriously Derek. I really think you need to preview before posting. Is digging up an old post another veiled threat or is it supposed to be helpful in some weird way?

Please check the "contributing handbook pages" guidelines. Comments on handbook pages are not site-wide settings, you can disable comments for individual hand book pages.

If you're under pressure to get the new contributions system working properly because users have donated money to the initiative I can only suggest you take a break and come back to it refreshed. The Drupal community is very resourcefull and will struggle on despite the problems.

And please please please try and be a bit more diplomatic in future. As a community it's vital to encourage people to contribute...not alienate them, threaten them or bite their heads off.