When you install the module on a site that uses table prefixes, it fails. Warnings are issued indicating that the table "prefix_term_lineage" can't be found.
I've reviewed the code, and found the issue. The .install script doesn't properly escape the table and index names (e.g., "{term_lineage}"). I've fixed it on my installation, and it now works.
I can provide a patch on request.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | lineage.install.patch | 1.35 KB | guardian |
| #6 | lineage.install.patch | 1.28 KB | guardian |
| #3 | lineage.install.patch | 1.05 KB | guardian |
Comments
Comment #1
ingacosta commentedplease, send me a patch. You can send it to [mail deleted]
I have the same problem. I tried to fix it but I couldn't resolve the problem at all. I have problems when others modules need this module.
Comment #2
jhun vert commentedI also had the same issue. Please send me your patch, I am not a php coder, and I know very little about database. Please send the patch to (email - I removed my email address), thanks.
Comment #3
guardian commentedhere is a patch and also all you need to know about patches is here.
Comment #4
guardian commentedComment #5
ingacosta commentedI patched it for myself, but thank you very much for your help.
Comment #6
guardian commentedplease wake up :)
Comment #7
guardian commentedsorry for the broken patch
Comment #8
xjmTested patch; it resolved the same issue for me. Hope to see the fix in a release.
Comment #9
AD-DA commentedTested the patch.
It works.
Is this module still maintained? Could this patch be committed?
Comment #10
agileware commentedThis patch is in the development version of the module.
After I've been through the issue queue, I'll create a new release. Then the port to 6.x will begin.
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #12
xjm