Hiding some field totally like in TCEFORM

[subnoodle]

Hi Nicole,

i'd like rather to "blind" some fields for one colpos.

In TCEFORM it would be written like:

TCEFORM.tt_content.image_zoom.disable = 1

But there are no conditions for colpos since it's backend related.

Other then that, with your AWESOME extension, i can archive like:

...
                rows {
                    1 {
                        columns {
                            1 {
                                name = Slider (5)
                                colPos = 5
                                colspan = 5
                                allowed {
                                    CType = textmedia
                                    imagecols = 1
                                    imageorient = 0
                                }
                            }
                        }
                    }
...

Means, restricting the field to just one value.

But i cannot, e.g. disable field "bodytext".

Do you see any chance or need to make this work?
Or does it already work, but is just not mentioned in the README?

Many Thanks, Thomas

[IchHabRecht]

Hi @subnoodle,

To be honest I don't understand what you want to achieve here. TCEFORM already provides some features to disable fields even for specific types. Maybe you can give me some more examples.

[subnoodle]

Hi Nicole,

thank you for your feedback.

I'll try to explain in another way:

Let's say there is one backendlayout with two colpos: 0 (content) and 1 (header)

I e.g. want to have:

• image-zoom field appears in content-type "media" in colpos content
• image-zoom field does not appear in same type in colpos header (there, e.g. an adapted fluid template does not consider "zoom")

"image zoom appears / does not appear" means: admins and editor can see / edit it or is hidden / inaccessible in the backend

Hope, this is clearer.

Until now, i can determine valid values for fields per colpos, but cannot hide / show a field completely per colpos.

I needed it once - and could still be useful in a current project.
However, i thank you for your efforts in this extension of yours - it's already really great!

Bye, Thomas

[IchHabRecht]

Hi @subnoodle,

Thank you for your further explanation. Currently I don't see any way to include this feature in a configuration-able way. I would recommend to add an own DataProvider for this kind of case and exclude necessary fields in there.