Page 1 of 1
MLE phylosophy - Why cms_content_name_xx, menu_text_xx and so?
Posted: Thu Mar 12, 2009 10:19 am
by spammy
I'm new to CMSMS. I just working on my first CMSMS site which will be multilanguage. I feel a bit complicated to add new fields to the database whenever I want to add another language to a site. I'm thinking about and trying to guess why MLE version uses this medhod. As I'm a programmer I feel that it should use one 'lang' field in content table instead. I feel it more simple, convenient and flexible. Did you (Alby?) think about this? Or did I miss something?
Re: MLE phylosophy - Why cms_content_name_xx, menu_text_xx and so?
Posted: Thu Mar 12, 2009 12:50 pm
by alby
spammy wrote:
Did you (Alby?) think about this? Or did I miss something?
You are right but when I have take this project there is already.
For no invent wheel again and mantain the past compatibility
I kept this.
In 2.0 will be different....
Alby
Re: MLE phylosophy - Why cms_content_name_xx, menu_text_xx and so?
Posted: Thu Mar 12, 2009 2:49 pm
by TeXnik
alby wrote:
In 2.0 will be different....
Alby
Does this mean, one can not upgrade from 1.5.x to 2.x?
Re: MLE phylosophy - Why cms_content_name_xx, menu_text_xx and so?
Posted: Thu Mar 12, 2009 3:01 pm
by alby
TeXnik wrote:
alby wrote:
In 2.0 will be different....
Does this mean, one can not upgrade from 1.5.x to 2.x?
2.0 will be very very very different and will be not back compatible (including original CMSMS 1.X).
I suppose that will be a "bridge" version for minimize the problem of conversion.
Some thing for many modules and I will try to do the same thing with MLE but now is very early
Alby