Hi,
I have tried and tried, but I can't get the inline setting to work for my field labels. When I set the display to "inline" the label disappears completely. I have had several people look at it and they can't figure it out either. Another small issue I am having is that I created a file upload field with a description, but even though you put in a description, the description does not display. When you go back to configure the description, the text is gone.

My site is www.familytreebank.com/drupal

I have a tester login:
abell
tinker43

After login, click on "recent posts" and click on a content with the type "individual." Right now, all my fields are set as "above" with the exception of "sex" which is set to "inline." You will notice that now the "sex" label is missing. The upload file field with a description is for the field called "Census X." You can try to edit an "individual" content type created by abell for this field and enter a description. After saving, you will notice that the description is missing.

Seems to be a theme issue because everything works when I switch to Blue Marine.

Thanks

Comments

ghede’s picture

Playing around with firebug, I noticed that in the CCK module it'self, in this file:

CCK/theme/content-module.css

visibility is set to hidden.

.field .field-label-inline {
visibility:hidden;
}

Try commenting out this code. Of course, if you update the module, you may have to redo your changes. You may also try overriding this in Marinelli's css files.

kbellcpa’s picture

Hi,
I tried to comment out the line you suggested, but id didn't work. I don't think it is CCK that is causing the problem because when I switch to Blue Marine, my labels work perfectly. Unfortunately, I have worked on Marinelli so much and like the way it looks, I don't want to change themes.

Any other suggestions?

oadaeh’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

This issue is being closed because it is against a branch for a version of Drupal that is no longer supported.
If you feel that this issue is still valid, feel free to re-open and update it (and any possible patch) to work with the 7.x-4.x branch.
Thank you.