Replication of stream items w/ Archive module
spiffyd - August 15, 2008 - 22:34
| Project: | Archive |
| Version: | 6.x-1.2 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Not sure if this belongs here or in the Archive module issues but I'll post here any way in case others have the same issue.
Archived Activity Stream module items are duplicated and/or replicated when viewing the Archive model page. I'm not sure what's the cause but maybe it's replicated every time cron is run.
Archive module: http://drupal.org/project/archive

#1
Can you look in your node table and see if there's duplicate items in there? I took a quick look at the code in archive.module and don't see anything that would cause a node to appear twice unless it were in the DB twice.
What's the source of the stream items that you're seeing duplicated? I can take a look and see if it might be returning duplicate items or sending in items that might make Activity Stream think a single item is two different items.
#2
@akalsey, I looked in my node table (Contents) and see no duplications of any entries.
I disabled the archive module (there was no option for uninstallation) and re-enabled it. Ran update.php and cron. Problem still existed.
Optimally, I'd like to deleted all database entries associated with Archives module ("full uninstallation") and reinstall it to test things out. Because Archives module does not show up in the uninstall page after disabling, I cannot test this unless I go into PHPMyAdmin and manually delete tables. What do you think?
Another weird observation is that previously deleted items and non-selected node type entries are also showing up in Archives. These problems don't seem to have anything to do with Activity Stream so I'll bring it up in Archive module's issues area.
#3
Hate to pass the buck here, but if Activity Stream isn't creating any duplicate nodes, then any duplicate items that appear in Archive have got to be an issue with Archive.
#4
Archive doesn't create any of its own tables; it doesn't need to. All archive does is pull nodes from the node table.
An uninstall function should really be added, and I've added it as a new task, but if you want to clear any archive settings just TRUNCATE or delete all rows in the cache* tables. There's one that deals with settings, I forget which one, but it's safe to clear out data from all of them.
You could try that first. If that doesn't work, disable the Activity Stream module and then check if the archive page is working correctly.