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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Label of existing DB field is not overridden #8

Open
marcoseiler opened this issue Aug 6, 2016 · 6 comments
Open

Label of existing DB field is not overridden #8

marcoseiler opened this issue Aug 6, 2016 · 6 comments

Comments

@marcoseiler
Copy link

If I use an already existing DB field in mask, the label of this field can be overridden.
In the exported extension, the field is displayed with it's default label instead.

@IchHabRecht
Copy link
Owner

Unfortunately this is not as trivial as it may sound. Currently it's a known missing feature but for me it was more important to generate a locallang file instead of the fixed labels, mask provides.

@marcoseiler
Copy link
Author

The locallang reference to a new label can be set in the showitem string directly after the field name, separated by a semicolon. But maybe the difficulties are in another area.

@IchHabRecht
Copy link
Owner

The export reuses the TCA generated by mask. If it is not provided there, it is currently a bigger task. But you can of course edit the export afterwards and adjust it to your needs.

@IchHabRecht
Copy link
Owner

As far as I remember mask generates the labels via TypoScript for each CType. As I said, mask is not able to use labels with multi language support and that was more important for the export than having different labels ;-)

@marcoseiler
Copy link
Author

I don't know if putting the alternative labels from the mask.json to the locallang file is a big task. If not, it would be nice to have them there already in place.

@vaxul
Copy link

vaxul commented Jul 26, 2019

Hi @IchHabRecht . Since EXT:mask got a lot of updates since 2016, is this topic still as complex as you mentioned it at that time?

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

No branches or pull requests

3 participants