Datasource output breaks if textarea is included about subsectionmanager HOT 11 CLOSED

I think the $mode is used for output simulation. But I'm not sure. Has something changed in this area of Symphony?!

from subsectionmanager.

I think is has to do with formatted vs. unformatted output. For backward compatibility Alistair even included this in line 168 of field.textarea.php:

if ($mode == null || $mode == 'formatted') {
    ...
}

This means that you have decide if you want to output the formatted version or not. It would probably be the best to look up the desired output in the related section and set the parameter accordingly (formatted/unformatted, I guess).

from subsectionmanager.

Ah yes, that makes sense. Subsection Manager isn't backwards compatible at all so we should not have to care about that. If this is about the formatted and unformatted setting we should start thinking about a way how to integrate the included elements settings directly into the data source editor.

from subsectionmanager.

What about displaying them together with their section name? Let's say we have a section called "media":

• media: name
• media: file
• media: description

from subsectionmanager.

Sorry, it must be like this:

• media: name
• media: file
• media: description: formatted
• media: description: unformatted

from subsectionmanager.

That's a good idea - or their field name. E. g. a Subsection Manager field with the name 'photos' (linking to your media section):

• photos: name
• photos: file
• photos: description: unformatted
• photos: description: formatted

from subsectionmanager.

Exactly.

• section name: field name: formatting (if applicable)

from subsectionmanager.

I think I'll have to investigate how the textarea field handles the implementation of these different types.

from subsectionmanager.

The Textarea is broken in that its appendFormattedElement doesn't have a default set for $mode. All other fields do. I believe this has been fixed in 2.0.7 or 2.0.8, so it's not actually a bug with Subsection.

from subsectionmanager.

Looks like it was fixed in 2.0.8. So extension compatibility might be changed to 2.0.8+.

from subsectionmanager.

Great - thanks for the feedback.

from subsectionmanager.