TypoScript configuration not in frontend

[Kaliumiodid]

When using the extension, I want to adapt the default settings by a setup.typoscript file in my site package. The extension finds the settings, because I can see them in the settings form of the plugin. But when taking a look at the website, the default settings of the extension seem to be used.
E.g. I adapted the slidesToShow to always show just one image on all screen sizes. In the settings form it is shown like set in typoscript, but when looking at the rendered website, it shows multiple images at once on smaller screens. I always have to open the settings form and set everything again, even after flushing the cache. Is this by purpose or do I miss a step?

[miko007]

It looks like, there is something fishy going on with the parsing of the TypoScript. The Typoscript

plugin {
	tx_wsslider {
		settings {
			defaultRenderer = slick
		}
	}
}

is yielding

which is obviously incorrect. The parser usually takes care of the trailing dots (renderer.), but in this case, it does not, so the whole configuration set by TypoScript is ignored.

[miko007]

@svewap did you have a chance to look into that already?

[codekapitaen]

Hi @svewap ...

sadly i can confirm this behaviour (T3 v12.4.5 / EXT:ws_slider v12.1.2) In my case i've got multiple Slider Plugins (Slick Slider) on one page. JS configuration for each instance is generated correctly with the specific content element id before closing body tag. But changing autplay [settings.js.autoplay] false/true has no effect in frontend. Debugged with <f:debug>{sliderSettings.parameters.autoplay}</f:debug>

Greetings

[rawsta]

It seems that the only way for now is, to write the configuration directly in the backend.
At least for me, all configuration inside files is ignored.