Hello Ron,

I was curious why the keyword field has changed from a text box to a drop down menu. Is there way to change how the keyword is displayed on the filter page to show just a text box opposed to a drop down box. Do I need to delete the data from the database for this column?

Thanks
Mike

CommentFileSizeAuthor
#5 Picture 2.png19.61 KBlinuxGuru

Comments

rjerome’s picture

rjerome commented

Hi Mike,

The biblio keyword field hasn't changed from a text box, you may have to look in the "Other Biblio Fields" fieldset to see it. I suspect what you are seeing is a Taxonomy term list. Do you have a taxonomy vocabulary called Keywords assigned to the biblio content type? Did you use any of the beta releases? For a while during the beta series, I moved the keywords to taxonomy, then reconsidered and moved them back.

Ron.

linuxGuru’s picture

linuxGuru commented

Hello Ron,

In the past I used beta releases. I guess the only way to fix this is to revert the database to an earlier time and reinstall the module? I had a taxonomy called keywords assigned to the biblio content type, but I got rid of it.

Mike

linuxGuru’s picture

linuxGuru commented

Hello Ron,

is there an alternative solution to correcting this problem if I happen to not have a current backup of the database? Any feedback much appreciated

Mike

rjerome’s picture

rjerome commented

So are you saying that you currently have NO taxonomy vocabularies assigned to the Biblio content type? If that is the case, then I'm not sure where it's coming from. Could you post a screen shot to the offending "drop down" (including a few surrounding form items) that might give me a clue where it's coming from.

Ron.

linuxGuru’s picture

linuxGuru commented
StatusFileSize
new Picture 2.png19.61 KB

Hello Ron,

did you mean that you wanted to see a print out of the form array? Can you clarify, thanks

Mike

rjerome’s picture

rjerome commented

I'm sorry, I didn't read your first post thoroughly enough... It does state the filter form, but I was though you were referring to the input form.

Yes, that one has changed and the rational was that since we now have separate keyword table it is possible to filter on a specific keyword ID rather than searching for a keyword string. I suppose you want the ability to find partial matches on a keyword string?

Ron.

linuxGuru’s picture

linuxGuru commented

Hello Ron,

sorry for the confusion. Yes I want the ability to be able to type in a keyword into the keyword field and retrieve any rows that match a particular keyword. At the present time the keyword field appears to be a drop down menu with populated keywords.

Thanks,
Mike

linuxGuru’s picture

linuxGuru commented

Hello Ron,

Can I not just override your biblio_form_filter and change the keyword drop down menu to a text field and write a query to return matching rows? I started to write a module that extends the functionality of the biblio module (just to change the presentation of the tabs and buttons that appear on this form) Would this suffice you think or is there a more solid solution?

Thanks again
Mike

rjerome’s picture

rjerome commented

I guess I'm a little confused as to why you don't like the drop down list? This shows all the keywords in the database and selecting one will return all the rows (biblio entries) which contain this word. The benefit of this is that the user doesn't have to guess at which keywords may have been used. If they select one from the list,they are guaranteed to get a match.

In answer to your question, yes, you could write your own biblio_form_filter function, but you would have to delete (or rename) the existing one. In order to really "override" it, it would have to be written as the theme_ function which you can override without touching the original.

Ron.

linuxGuru’s picture

linuxGuru commented

Hello Ron,

If it were up to me I would leave the drop down list. However, the owner of the website wants a text box. I will override the theme function. Thanks again

Mike.

liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented
Issue summary: View changes
Status: Active » Closed (outdated)

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.