to not output individual streams as nodes - for example, to keep at low the number of nodes when displaying the stream is sufficinet or just not want to add to the huge number of nodes

Comments

gausarts’s picture

gausarts commented

plus 1 for this.

Thinking of thousands of members with millions of nodes imported, I think this is reasonable:) Perhaps adding another database table that can be purged at a predetermined period of time would be nicer.

Thanks

misty3’s picture

misty3 commented

Any help please ?

akalsey’s picture

akalsey commented
Status: Active » Closed (won't fix)

The module keeps most of it's data in nodes. So there's no way to have it not create nodes.

I'm not sure what the issue is with creating nodes.

misty3’s picture

misty3 commented
Status: Closed (won't fix) » Postponed (maintainer needs more info)

There is no problem in Activity stream keeping its data in nodes that is Activity stream nodes.
however each feed becomes a node in drupal which means if an user has over time hundred or thousand of feeds each of these becomes a separate node in drupal.
This becomes unmanagbly high when there are hundreds of users or thousands and difficult unnecessarily for backup or import export of database. This also slows up or throws more useless result by the drupal search which is apparently not very good.

Please see by example -
user A does xyz
user A does abc
user A does 123

Collectively if the above goes into ONE activity node its fine and make sense
- if each becomes a node the count multiplies at alarmingly high pace !

If I have understood wrong please tell.
Many or most people do not need each item to become a node and this is what is holding them from using it. See the poster above also. In shared or VPS hosting scenarios this issue does become important.

akalsey’s picture

akalsey commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)