Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backend form field not only if applied to tl_member #3

Closed
Defcon0 opened this issue May 10, 2016 · 5 comments
Closed

Backend form field not only if applied to tl_member #3

Defcon0 opened this issue May 10, 2016 · 5 comments
Assignees

Comments

@Defcon0
Copy link

Defcon0 commented May 10, 2016

Hello,

at first thanks for the great extension 馃憤 !

At the moment, a backend representation for the frontend widget is added to $GLOBALS['BE_FFL'] if $GLOBALS['TL_CONFIG']['checkedEmailForMembers'] is true.

Wouldn't it be better to add the line $GLOBALS['BE_FFL']['checkedEmail'] = 'TextField'; in every case? At the moment I would have to add the widget to my members if I want to make the fields visible in efg-stored data.

Bye Defcon0

@cliffparnitzky
Copy link
Owner

Thanks for the praise.

What is wrong with using the system flag? ... Set it to true if you want this. I think the decision should be done by system admin.

@Defcon0
Copy link
Author

Defcon0 commented May 10, 2016

I thought I made it clear ;)

At the moment I would have to add the widget to my members if I want to make the fields visible in efg-stored data.

I want to have the fields of the checkedEmail type in the efg results. I don't want it in the members at the moment.

These two things don't necessarily belong together. There shouldn't be a hard dependency imho.

@cliffparnitzky
Copy link
Owner

ah, you want to see the field in the backend area, e.g. "Feedback" ???

@Defcon0
Copy link
Author

Defcon0 commented May 11, 2016

Exactly :) I don't know what's the English word for it in contao, but I mean the "Formular-Daten" integrated by efg.

@cliffparnitzky
Copy link
Owner

cliffparnitzky commented May 11, 2016

Ahhhh, ich schnall es ... denke mal das ist ein Fehler.

Sollte wohl eher immer eingetragen sein.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants