It's pretty easy to hide a criticism and a recommendation that no one will look at in a back page, but I figure it's worth someone on the team having a look. I might be way off base here, but I don't think this is even still valid (I'm running Drupal 5.x and I tried creating the tables and the module didn't show up in admin->modules. This seems obvious to me since it doesn't have a .info file, but I could just be smoking crack.) Please review and update/remove if necessary, or just let me know if I'm a total n00b.

Comments

sepeck’s picture

sepeck commented
Assigned: Unassigned » sepeck
Status: Active » Postponed

umm... not sure what you are talking about

A look in the CVS shows the module still active and part of core.

The core module pages are undergoing an update right now but some of the confusion is do to massive changes in 4.7 -> 5/6 series /admin menu and locations. This will be updated soon enough.

In the meantime,
see administrator >> site building >> modules to enable
see administrator >> content management >> news aggregator to configure.

zirvap’s picture

zirvap commented
Assigned: sepeck » zirvap
Status: Postponed » Fixed

I think MooMaster is talking about the handbook page for the contrib module User Aggregator, and sepeck is talking about the core module Aggregator. Right?
For the future, MooMaster, it helps if you include a link to the problematic page.

A handbook page for a contrib module doesn't belong under Core modules. Normally I'd move it to the Contrib section, but since the module in question never had a release and hasn't been touched in a year, I've moved it completely out of the handbook. (I'll make and close an issue about this in the module issue queue, so the information can still be found if the module is un-abandoned in the future.) Thanks for the heads up!

If you'd like to adopt this module, see Dealing with abandoned projects.

sepeck’s picture

sepeck commented

you're right, I'm blind.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.