Re-enable http://drupal.org/project/modules/index

From a user standpoint, +1.

With caching, I would hope this View would not be a performance bear, but afaik any implementation would need to be approved by the Infrastructure team. As such, this ticket might need to end up in a different issue queue, assuming community consensus on the desire for this feature.

I, too, found this single-page title-only list highly useful and would like to see it made available again. Having it available to authenticated users only would be fine with me.

The view isn't really that bad but the resulting html is huge and I've found it to at least stall my browser.

the discussion I've had with Neil had the following result:

1) have the current link link to a paged list of module. Maybe the one that is already in existence.

2) below the link offer a link to this complete list and add a comment that it is only available for authenticated users.

Anybody interested in implementing this?

Anybody interested in implementing this?

I'm happy to do this configuration. However, my account does not have the necessary Views permissions. Also I will not be available to do this until after the weekend.

You'll need a dev site to do this since all d.o views should be in code.

I would love to have this list back in place too. I prefer to scan all the modules by name instead of using the search function.

Isn't it possible to cache this page and recreate the cache only once a day (or even once a week) to prevent huge server loads?

I am just adding my voice to request this functionality to be returned, as I find it very useful.

Luke

I think the Theme list is gone too.
http://drupal.org/project/themes/index

I too always enjoyed this opportunity, as a standard search does not suit me. Return, please!

https://drupal.org/node/1247730#comment-4858048

has all the info required to get this back.

Yes, i do support mikegfx and even me also using the link twice in a week. I think that link is most useful for the new comers. As they want to test some modules and will try to find new modules. So it would be handy for them if you re-activate the link. Please activate it. Please!

Since Drupal.org's custom views are exported to drupalorg module, moving there. I don't know the details of it offhand, but http://drupalcode.org/project/drupalorg.git/blob/refs/heads/6.x-3.x:/dru... has some stuff involving project_index. In the end, I expect this might be a patch for that file.

To get started using development sites, see http://drupal.org/make-drupalorg-awesome.

Just to say I also found this page fantastically useful and miss it a lot!

@lin you can't see the page atm? i see it at http://drupal.org/project/modules/index but i'm assuming that's cause of my perms?

Also, updated docs plans here for reference http://groups.drupal.org/node/175174

@arianek I get "Access Denied" with my site maintainer role.

Yeah, for some reason, the view is now overridden in the DB (naughty, naughty!) to only be visible to users with the "administrator" or "git administrator" role. Since this wasn't done in code with version control, there's no record of the actual change or why/when it was made. Given the comments in this issue, we can only assume that killes did this at some point via the views UI...

Anyway, that's the current status. I still think this is silly, and we should just let authenticated users get the whole page again. If you want a paged list, there's already all the solr-based browsing pages. The only value this page has to anyone is having everything on one page. If we go down the road killes proposes in #3 with a paged listing, we all know people are going to start requesting more and more data on the page, and we'll slowly creep back towards the solr-based listings, only without solr. No thanks. Let's just bring the view back. If it stalls your browser, don't load it. ;)

IMHO...
-Derek

@dww thanks for the info!

@linclark - if the view is made accessible again, will that suffice your needs for the module, or do you need anything additional?

I want to state that I strongly agree with Derek about this issue. And as I said above, if the page brings too much load on the server it should probably be possible to cache the page and update it once every 24 hours (in worst case scenario's).

Cheers,
Bram.

Heck, update it once a week if needed - I'm pretty sure that it doesn't need to be accurate to the minute. ;)

Huh. I did not even know this page was there. Useful!

Subscribing. Happy to deploy whatever code changes to my d.o sandbox for a testrun.

Sounds like what we need is someone to:
1) Download and install http://drupal.org/project/drupalorg_testing
2) Edit the views so they're both a) not accessed controlled, and b) cache the results for one week (or some other long period of time)
3) Re-export them to drupalorg module
4) Upload a patch.

I'm being bold! This sounds like a novice issue.

No patches necessary. All we need to do is revert the view and let the one in version control resume working. That doesn't have access control, and (IMHO) we don't need any extra caching, either. We should already be hitting the Drupal page cache for anon, and squid (or whatever we're using now) for auth users. Besides, the query for this view is very trivial and should be served entirely by the DB index -- I don't think anyone's ever claimed that the query to generate this page is expensive -- the only problem is the size of the payload (for some users on some browsers). Caching page generation won't help that.

So, IMHO all this needs is to somehow convince killes that his undocumented and non-version-controlled modification should be reverted, thereby restoring this view to how it already exists in code. However, we shouldn't claim that getting killes to change his mind is a "Novice" task, and I'd hate to be the newbie who tried. ;) Gerhard eats newbies for breakfast. ;)

Cheers,
-Derek

p.s. Upon closer inspection, we're already altering this view via drupalorg.module to add caching. See _drupalorg_views_default_views_alter() in drupalorg/drupalorg/drupalorg.views_default.inc. So the only thing that's been overridden is the access control.

Therefore, this is all that needs to happen once we get agreement:

drush views-revert project_index

Cheers,
-Derek

+1. Needed this page. Im tracking for stats.

sub

We'd be really interested in having access a list of all modules, their descriptions, and perhaps some other metadata. Using this we could make a "drush module-find" type command that would let the user search through module names and descriptions. Kind of like "apt-cache search". Another (even more convenient) approach is having read-only (GET-only) access to the Drupal.org Solr instance.

It is! Yay!

http://drupal.org/project/modules/index

http://drupal.org/project/themes/index

Page not found. the page that list all the modules and all the themes is gone.

Should be fixed. See #1627228: Broken link to the Modules Page

it's ok now thanks

Let's leave this one year old issue closed. There is fresh report in D7QA queue #2155517: Project index page not found