Decrease "view (1700)" priority in ext:theme template selection

[Sengchheang]

in web/typo3conf/ext/theme_t3kit/Configuration/TypoScript/Library/plugin.themes.setupts

plugin.tx_themes { view { templateRootPaths { 1700 = EXT:theme_t3kit/Resources/Private/Templates/ } partialRootPaths { 1700 = EXT:theme_t3kit/Resources/Private/Partials/ } layoutRootPaths { 1700 = EXT:theme_t3kit/Resources/Private/Layouts/ } } }

the above TS defines the priority of theme_t3kit in view selection of ext:theme.
However ext:theme seems to take this into account already even without above code when the template is activated in Theme module.

see in web/typo3conf/ext/themes/Configuration/TypoScript/setup.txt
view { templateRootPaths { 100 = EXT:themes/Resources/Private/Templates/ 500 = {$themes.resourcesPrivatePath}Templates/ } partialRootPaths { 100 = EXT:themes/Resources/Private/Partials/ 500 = {$themes.resourcesPrivatePath}Partials/ } layoutRootPaths { 100 = EXT:themes/Resources/Private/Layouts/ 500 = {$themes.resourcesPrivatePath}Layouts/ } }

In this case, the selected theme is 500 while 1700 brought by ext:theme_t3kit is too high for sub-theme to take place.

see https://github.com/t3kit/subtheme_t3kit_template/blob/master/Configuration/TypoScript/Library/plugin.themes.setupts

there is an example block (supposed to be always un-commented) to make the template overriding works. This block will be not necessary when 1700 in ext:theme_t3kit is decrease to less than 500.

If the above suggestion is not applied, the image below will demonstrate the particular case for sub-theme user having issue with view priority.

(I am not t3kit Slack, please ping me if the above comment is not so clear.)