Hi everybody,
I would like to ask if CKK has some limitation (in one content type, will helps me numbers from live websites. ):
A, How many CCK groups I can use ?
B, How many CCK fields (in one group) I can use?
C, Values in CCK fields (Allowed values list:) - If I set “unlimited” how many values I can use ?
D, How I can translate text values from Allowed values list? I can’t find the text values via translation interface.
Thank you a lot.
Comments
Comment #1
yched commentedA / B / C : no limit
D : allowed values are currently not translatable
Comment #2
sentinelcz commentedto yched:
Thank to you for quick answer.
Can you recommend me if I have:
AA, create one field with translated values in all languages (in one text field I will have the same values but translated in several languages)
or
BB, I can create x fields (one field for one language), and every field will contains only own language values ?
What is better from speed point of view ?
In real I need translate 50 values and I have propose 10 languages.
Question is I will have to have "AA" - one field with 500 values or "BB" - 10 fields with 50 values.
What you think ?
Comment #3
GN commentedI don't think it's a good idea to translate the allowed values - it makes more sense to translate their labels.
They are translatable, though it can be a little bit tricky -- see e.g. discussions on
http://drupal.org/node/182884
http://drupal.org/node/248573
http://drupal.org/node/293297
Comment #4
GN commentedAlso, I would note that, even if the number of cck fields is theoretically unlimited, in the practice you may bump into server memory limitations, especially if you use cheap shared hosting and cannot change its memory settings (max_allowed_packet and so on).
See e.g. http://drupal.org/node/121390.
Comment #5
sentinelcz commentedI found solution. I will not translate values, I will solve it via recognizing of page language.
I have hosting where is possible buy more memory. Thank you GN for tips. I will read all.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.