web-vision / wv_deepltranslate

TYPO3 Extension to translate content and TCA records with DeepL Translate
GNU General Public License v2.0
23 stars 40 forks source link

[FEATURE] Custom plugin fields are not translatable if theye are defined in flexform #341

Open MarineAs opened 3 weeks ago

MarineAs commented 3 weeks ago

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior: Please add a step-by-step guide to reproduce the issue.

If an exception is thrown or an error occurs, the full stack trace is also helpful to gain quick insight.

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

TYPO3 Setup

Additional context Add any other context about the problem here.

calien666 commented 3 weeks ago

At the moment, FlexForm is not supported while translating. Only filed type input (standard) and textarea are supported due to restrictions in Core translation handling. This was discussed several times until now, see https://github.com/web-vision/wv_deepltranslate/issues/71#issuecomment-1536194539.

As this is not a bug, but we could implement as feature, take a look at this comment: https://github.com/web-vision/wv_deepltranslate/issues/285#issuecomment-1866104607

Currently adding flexform support, will take a lot of code changes and changes in current work steps. This is a big change, we can't effrt at the moment. If you think, you will sponsor this feature, please contact @borishinzer.

calien666 commented 3 weeks ago

Duplicates #285