Biblio Search returns error
princeofwales - June 25, 2009 - 12:25
| Project: | Bibliography Module |
| Version: | 6.x-1.5 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Thanks for wonderful Biblio module!!!
Installed, any search yields results, but preceded by following error message:
user warning: Table 'ages.node' doesn't exist query: SELECT distinct(i.sid) FROM AGES_search_index i INNER JOIN node n ON n.nid = i.sid WHERE n.status = 1 AND (n.type = 'biblio') AND (i.word = 'role') AND i.type = 'node' GROUP BY i.type, i.sid HAVING COUNT(*) >= 1 in /home/.sites/112/site7/web/sites/all/modules/biblio/biblio.pages.inc on line 805.
Any tips what I've done wrong?
#1
Correction: results are not results, just list of docs in biblio.
http://ages.ca/documents
#2
Hi,
There was an ever so small omission in the biblio.pages.inc file which causes this error when db_prefixes are set (as you have). I have corrected this in the -dev version and if you want to fix your installation just edit line 799 in biblio.pages.inc and put curly braces around the word "node" like this...
INNER JOIN {node} n ON n.nid = i.sidRon.
#3
Like Magic!!!
Thank you!!!!
But now getting
user warning: Duplicate entry '78-132' for key 1 query: INSERT INTO AGES_term_node (nid, vid, tid) VALUES (132, 132, 78) in /home/.sites/112/site7/web/modules/taxonomy/taxonomy.module on line 693.
when updating biblio nodes.
cb
#4
All biblio nodes or only selected ones? I've seen this on my test system with a few nodes, but it's usually related to some funky state the database got into.
How do you have your keyword/taxonomy integration setup (in the keywords section of the /admin/settings/biblio page)?
#5
Taxonomy set up is:
keyword separator: ,
automatically remove orphaned keywords (checked)
copy any selected taxonomy terms to the biblio keyword database (not checked now)
Use keywords from biblio entries as taxonomy "free tags" (not checked now)
I played with various of the settings (including these) for biblio after installing it, noticed that database errors started occurring after I RESET TO DEFAULTS. Perhaps my database having a prefix affected the setup or reset of tables, and now paths are not correct? Just a wild guess. Perhaps I need an install package that more fully takes into account database prefixes?
I really like the module, its lean-ness while having the possibility of so many fields and document types, and including a URI to a digitized version of the document just by attaching the document during the create biblio node process!
#6
Interesting, you know I've never pushed the "reset to defaults" button, nor do I know what it does since this button is supplied by Drupal core not Biblio. I'll have to look into that.
#7
Problems seem to occur only on new document types added after install. Perhaps this is when database got screwy? Now getting funny entries in first field when reading bibliograpy.... http://ages.ca/documents
#8
Figured out how citations are made and stored...cleaned up mess I made by changing keys several times. All seems to be working now, no errors, when creating or revising old or new. May have been web hosting limit on database connections?
Great instructions for biblio at http://drupal.org/node/111016
Seems to be working cleanly now.
Thanks again for your help!!!
cb
#9
Shouldn;t have trempted fate. I still get error when I create a new biblio node using a new type I've defined.
warning: Invalid argument supplied for foreach() in /home/.sites/112/site7/web/sites/all/modules/biblio/biblio_theme.inc on line 224.
I would just delete biblio database tables and reinstall biblio from scratch, using existing updated files, but for the possibility there are other iterations of the database-prefix problem.
Can above result from my not entering URL or DOI info in Biblio config?
I am really keen to use this module to document thirty years of advocacy work, 5,000 pages of pdfs, wmvs, etc, are ready to upload, but it needs to get off on a clean foot.
#10
OK, I think I know what the problem is... After you created your new type, you will need to edit that newly defined type and select which fields you want displayed. Go to admin/settings/biblio/fields/type and click the "edit" link to the right of the type you created, then make a few of the fields "visible" by default they are all "invisible" which is obviously not such a great thing :-)
I think once you get the settings sorted out, you will find that it should be able to handle your needs. There are some very large production installations with 10's of thousands of biblio entries.
Let me know it this doesn't fix the problem...
Ron.
#11
Ron -
I am proceeding with type definitions, had started it anyways--making certain fields visible for each type.
Thanks again. The module looks solid, especially considering installed community.
cb
#12
Ron -
I re-saved each of the document type field-visible pages and have created a half dozen new nodes in new document types with no error messages. Once again, your fix seems to have worked. Many thanks!!!
cb
#13
No problem, I've modified to code so that no one else will trip over that error.
(http://drupal.org/cvs?commit=230714)
Ron.
#14
Automatically closed -- issue fixed for 2 weeks with no activity.