Why is maintext field needed?

Hi

If we would disable/hide the maintext/Description field, the following is stated:

Hide the maintext field in the item form (not recommended !!!). TAKE CARE, you will loose the com_content backwards compatibility for these items !!!

If Flexicontent would be programmed to take the inputs(text, textarea, etc...) and put them all together into the com_content description/maintext database, why should this broke?

I ask this because in other cck's this is no problem because they use the descriped method. How does flexicontent?

For example i would use only text(title) and 3 images to be obligatory for the user to input into the form. I assume the images are placed into the com_content description db and after hypothetically uninstalling flexicontent, this record remains styled like it was within flexicontent in the core com_content. Not?

Hello

-- All FLEXIcontent core fields and a few other parameters, are stored inside the #_content DB table,

Benefits:
1. You maintain compatibility with various Joomla extensions: modules, content plugins,etc

2. If uninstalling FLEXIcontent then these will be removed: extra CUSTOM fields and content types, and template data, etc
but
the CORE field data title,description,publishing info, meta, etc will remain usable via the Joomla article System

e.g. the maintext field is the description of Joomla articles (intro text+full text)

so you would normally want this

Regards

hi ggppdk

thank you for answering, also the other question.

. If uninstalling FLEXIcontent then these will be removed: extra CUSTOM fields and content types, and template data, etc
but
the CORE field data title,description,publishing info, meta, etc will remain usable via the Joomla article System

I see. Than this is quite different at flexicontent. I assumed flexicontent also creates "just" a template for the custom fields and than inserts them into the description(intro/main)from com_content. This has some advantages and is very straight.

So this means if any content is created by flexicontent (aka custom fields) it shouldn't be uninstalled because those contents will be incomplete. cool. :roll:

thanks for your tyme.

Hello

if the field did not exist in separate DB table(s) then our capabilities would be greatly limited