Hide fields - fatal error

Thank you for your answer. It's very good news. Might I ask you when approximately is the next release? If it's not too far-off, I'll wait for it.

Sorry I can't contribute with the code at all, but I'll try to translate this module in Italian: it's really worth it.

Thanks again,
Calimera

Hi,

thank you for the last release. I have already downloaded it and was testing it.
Unfortunately I am still unable to find out how to hide "DOI Lookup", "Paste" and, now, "PubMed". I would like only "Publication type:" to appear at the beginning. You said it was possible with this release. I must be so stupid I can't find out how. Could you give me a hint, please?

Thanks again,
calimera

Hi Ron,

thank you for answering promptly -- sorry, I was away for a week and couldn't reply earlier. Modularization sounds great but I realize that it will take some time.
I have one more request which basically still deals with hiding things. I strongly need to modify the input form and hide several fields, which must not appear in the form at all. I read #337247: Howto: hacking forms and outputs and the following replies, as well as the latest attempts made by others.
I was wondering about this: just as in Biblio settings -> Fields -> Publication types you can choose which types will be shown or hidden -- and those which are hidden won't be displayed anywhere --, couldn't there be the same option provided for the field settings? I am thinking of a small check box named ‘Hide’ near 'common', 'required', 'autocomplete' in the page "Field settings common to all publication types".
I guess providing this option for each publication type requires a lot of time, but maybe providing it in the common settings takes a shorter time. I don't know...
It would be really of great help.

Best regards,
Calimera

Hi Ron,

it would be really great if I could hide the fields completely. I know about the check box which must be un-checked so that the field input box goes into "Other Biblio Fields", but then the field is still available because I can't hide this fieldset. If you give this option, it will be absolutely perfect!

Thanks,
Calimera

Hi Ron,
I've found the 1.9 version and I have installed it. Thank you for the changes to the code and the option to hide the "other fields" fieldset.
Unfortunately, it does not seem to work at all on my drupal.
Example: I checked "Year" and "Primary Author" as ‘common’ and ‘required’ in the “Field settings common to all publications” (so that these fields appear as grey in all the types of publications) and then I modified the “book” settings and I added “Publisher”, “Place published” and “Keywords” as visible fields. I did the same thing with the settings of the "Book chapter". Then I tried to create a book entry and a book chapter entry.
I always get this message:
“Fatal error: Unsupported operand types in C:\Programmi\Apache Software Foundation\Apache2.2\htdocs\drupal-6.14\sites\all\modules\biblio-6.x-1.9.tar\biblio\biblio.module on line 1243”

I have also checked if the error was connected to the checkbox "required" but it's not: even though I don't uncheck any default required field, I keep getting this error. I have changed the weight of the fields which I was not interested in, yet I got the same message.

I've tried it on my old drupal 6.13 installation and on two new fresh installations of both drupal 6.13 and 6.14. There can't be anything interfering with the module because it is the only one which I have enabled. What else can I try to make it work?

One minor thing: this is the message written in the Options “Fields set as "Common" on this page or "Visible" on one of the Type specific edit pages are normally moved to the "Other Biblio Fields" fieldset, selecting this check box will hide that fieldset completely”. Actually the contrary should be true: all fields that are not "common" or "visible" should be moved to "Other Biblio Fields" (and thus be hidden by checking the box). Right? If it’s just a small mistake in the message, it has minor importance; if it’s conceptual, it might be more problematic.

Thanks again.
Calimera

Hi Ron,
as soon as I added the code, the module worked perfectly. That's great!!!
Thank you very much for all this work!
Calimera