Closed (fixed)
Project:
Acidfree Albums
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Nov 2006 at 23:01 UTC
Updated:
17 Nov 2006 at 10:32 UTC
Jump to comment: Most recent file
Comments
Comment #1
anthon1 commentedOK, the problem is not fixed, but I had to do something, we have a high traffic site, and the error just kept getting worse everytime someone tried to look at the pictures. I commented out that part of the acidfree.module (lines 1884 - 1917)
Of course I cant add any new albums and when you upload photos no albums show up to select. But it's ok. I have faith in you guys, and I know you can give me some great support in getting this resolved.
Thanks
Comment #2
MikeyGYSE commentedAcidfree has been nothing but trouble so far, have used it in the past and it was fantastic however what with having to manually create it's database tables and having it run haywire and create over 4000 albums is NOT ON!
This needs to be fixed, quickly!
/* $Id: acidfree.module,v 1.62.2.58 2006/10/24 14:32:49 vhmauery Exp $ */Drupal Version 4.7.4Not only has it given me tons of extra work to do what with manually removing the content but my pathauto module is STILL trying to create aliases for all of these albums...
Comment #3
MikeyGYSE commentedAttached Screenshot showing phpMyAdmin viewing 999 rows on page 5...
I've had to disable the module because it just... keeps .... going!
Comment #4
MikeyGYSE commentedThe final count was actually 18,642 albums,
Anyone else having the same issue, there is a simple way to remove the albums:
First: Empty the "acidfree" and "acidfree_heirarchy" tables,
Second: Establish the NID of the FIRST AcidFree album (from the "node" table.)
Then run the following:
DELETE FROM `node` WHERE `nid` > NID;Replacing NID with the NID of the first album.
It saves you manually removing them...
Comment #5
vhmauery commentedLook MikeyGYSE, I would love to help you, but there is obviously something that you have done to botch your install. Try starting over with a *NEW* install of drupal and acidfree and see if that works for you. I don't see this problem myself or I would have fixed it.
There are thousands of other acidfree users that are very happy, so stop pointing your finger at acidfree.
Comment #6
anthon1 commentedOK, here's what I've been able to work out.
Apparently if the function, "function _acidfree_fix_root" for whatever reason gets more than one item with a parent id of "-1" it will create more root nodes. I dont know all the particulars as to why and how it happened in the first place, and such, but if you want to fix it do this;
Make sure that in the table acidfree_hierarchy, there is only ONE entry with a parent value of -1. Once that is set, make sure you uncomment the "function_acidfree_fix_root" from the acidfree.module (If you had commented it in the first place, otherwise ignore this part)
Good luck to all.
Sincerely
Anthony
Comment #7
MikeyGYSE commentedClosed this issue, the developer who commented doesn't seem phased so I'll guess that it is a glitch in my drupal install, unlikely as that may be.