TYPO3 Core

Are you talking about the kickstarter?
If not, could you please give an example to enable reproduction of this behaviour? Thanks!

I'm not talking about kickstarter but saved configuration in localconf.php

I have sometimes met this problem because of old plugin configurations in localconf.php. I have changed configurations but also I have forgotten to change everything. Plugin works because of old configurations but if somebody else install plugin firts time, it would not work.

Clicking 'Update' doesn't remove non-existing configurations.
For example the plugin 'tm_shared_lib' have now just two options.
I moved some features to a new plugin, but there is still.

$TYPO3_CONF_VARS['EXT']['extConf']['tm_shared_lib'] = 'a:4:{s:7:"enable.";a:5:{s:7:"topapps";s:1:"1";s:9:"userSetup";s:1:"1";s:11:"new_topapps";s:1:"1";s:12:"topapps_list";s:74:"menu,old_shortcuts,logout,clock,workspaces,user,cache,shortcuts,submodules";s:21:"dragndrop_for_tinyrte";s:1:"0";}s:16:"xyzcorp_position";s:5:"first";s:12:"companyImage";s:0:"";s:14:"companyAddress";s:0:"";}';

The CORRECT configuration fot this plugin should be today:

$TYPO3_CONF_VARS['EXT']['extConf']['tm_shared_lib'] = 'a:1:{s:7:"enable.";a:2:{s:9:"userSetup";s:1:"1";s:21:"dragndrop_for_tinyrte";s:1:"0";}}';

In order to avoid these kinds of errors, it would be nice, if
installation would have option (using a checkbox) to reset plugin configuration.
Then before new config has been written existing configuration would be first destroyed. This should be optional, if somebody would need older version.

When uninstalling plugin, it would be nice idea to have a checkbox to delete plugin configuration. If plugin would be newer used, why save non-used configurations. Typo3 should not however delete it automatic because plugin might be needed later.

Hi Tapio,

is that still a problem? If so, can you provide a patch?

This is covered by #0011560.

Resolved as duplicate of #0011560; please go on there!