Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Would be awesome if future versions of TeaCommerce had a local "Lang" folder.
Currently, every time I upgrade Umbraco, I have to re-instate the TeaCommerce translations. My proposial would safe guard against this annoying step.
What do you think Team TC?
Hi Paul
From which version of Umbraco was this supported?
A small PR would be amazing as the idea for the enhancement is already on GitHub :)
https://github.com/TeaCommerce/Tea-Commerce-for-Umbraco/issues/42
Kind regards
Anders
7.3 Apparently...
https://our.umbraco.org/documentation/extending/language-files/Language-Files-For-Packages/
7.3 is 1,5 year old, so might be okay for us to say that we now support 7.3+ :)
Or just drop in a note on the xml file saying...
// Supported from 7.3+
It wouldn't break anyone's site on v7.1, just merely ignored.
I know - but we don't like to have legacy stuff where something works with one version and not with another one. Then we need to support multiple ways and we don't like that :)
is working on a reply...
Write your reply to:
Upload image
Image will be uploaded when post is submitted
Tip : TeaCommerce Language File in App_Plugins
Would be awesome if future versions of TeaCommerce had a local "Lang" folder.
Currently, every time I upgrade Umbraco, I have to re-instate the TeaCommerce translations. My proposial would safe guard against this annoying step.
What do you think Team TC?
Hi Paul
From which version of Umbraco was this supported?
A small PR would be amazing as the idea for the enhancement is already on GitHub :)
https://github.com/TeaCommerce/Tea-Commerce-for-Umbraco/issues/42
Kind regards
Anders
7.3 Apparently...
https://our.umbraco.org/documentation/extending/language-files/Language-Files-For-Packages/
7.3 is 1,5 year old, so might be okay for us to say that we now support 7.3+ :)
Or just drop in a note on the xml file saying...
// Supported from 7.3+
It wouldn't break anyone's site on v7.1, just merely ignored.
I know - but we don't like to have legacy stuff where something works with one version and not with another one. Then we need to support multiple ways and we don't like that :)
is working on a reply...