| Project: | Content Construction Kit (CCK) |
| Version: | 6.x-2.x-dev |
| Component: | General |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I came across some layout issues on "admin/content/node-type/cck-help-screenshots/fields" page after i translated Multigroup: fields that move in unison to a very long string. It showed me that there are layout issues if the fields are going to be very long.
You can try with the latest German translation and must enable the Multigroup module. You will see the widget boxes are mobing outside the page... the same will happen if there are fieldtypes with very long names or fields in "existing fields" that have a very long human-readable name.
I changed the wording now for the Multigroup selectbox, but the select box is nevertheless too big. I don't know how to solved this... I think we should wrap to the next line... to mostly prevent enlarging the table cells.
Comments
#1
For the Multigroup selectbox we may also workaround with a colspan=2, but I think we should wrap...
#2
Actually I'd vote for the removal of the 'simple field collection' and 'fields that move in unison' texts. The rest of the form elements in this page do not provide descriptions of the choices, and defer explanations to the advanced_help pages.
"the same will happen if there are fieldtypes with very long names..."
We trust field modules not to come with too long human names :-)
"... or fields in 'existing fields' "
The content of this select is automatically truncated to 80 chars
#3
Do you like to name the two select options
StandardandMultigrouponly?#4
@yched: We should fix this for 2.0 as string change exception.
#5
Changing this to 'Standard' and 'Multigroup' is fine. I added the extra help text because I can't add anything to the regular help for this until the module is 'official', but anyone using it now should be able to figure it out. And I agree it is too long, even in English.
#6
OK, done.
#7
Fine... why are you not making it "offical"? From the discussions I thought it is soooo well tested and *important* that we haven't been able to delay this to v2.1 and it was a must in 2.0... :-)
#8
#9
There are still some problems to be worked out, most importantly that if you erase a value in the middle of other values, CCK will shift the data up, changing the delta and breaking the relationship between field values. This is a deal breaker right now that needs to be figured out, and I haven't had time to work on it any more. So it's committed without an .info file, which makes it 'invisible' but available for testing and improvement.
It *is* important, but it's a really really hard thing to do :(
#10
Automatically closed -- issue fixed for two weeks with no activity.
#11
Nevertheless the above issue is fixed now - I saw other content is moving out of layout and goes hidden (theme have overflow hidden to keep the layout intact) at "admin/content/node-type/my-test-content-type/display". The exclude column is partly invisible in my themes. This seems partly caused by the translation of "fieldset - collapsible" (DE: "Feldgruppe - Zusammenklappbar") and "fieldset - collapsed" (DE: "Feldgruppe - Zusammengeklappt") that is a little bit longer in German than in English. I would expect French will be more longer...
It might be too late for final, but I think we should try to solve this layout issue later.
#12
I'm experiencing the same problem here with the garland theme and a german translation. I'd suggest to devide the "basic" tab into two tabs, named "teaser" and "full node".