TYPO3 Core

Older versions tend to have the following entry in their localconf.php:

$TYPO3_CONF_VARS['BE']['defaultUserTSconfig']='';

I looked at my localhost's test version of TYPO3 4.5, that did not sport this line. On the webserver this line was still carried along from previous versions. Until today it did so without any damage.

After removing this line, the context menu worked like it's supposed to.
Is this a proper way to handle the problem?

Seems that the current internal handling of the default user ts config must be changed. The current defaults must be merged with the configured ones from the localconf.php or extension configurations. However this would also affect the already existing options before 4.5 alongside the new tree and contextmenu related ones.

what we need is to respect that in update wizard. As the default string was empty before 4.5, this was never a problem. But now new defaults were added, and this has to be merged with existing configuration if any.

Similar problem as with requiredExt (which was overwritten in some installations with improper values).

What we provide here is not only a "default" but a core setup which cannot be overwritten, because we might want to enhance that in future versions also.

So having a "similar" solution as requiredExt problem would be most appropriate:

1) defaultUserTSconfig = leave that to the user,
2) coreUserTSconfig = provided by the core, cannot be changed by localconf.php,
3) merge both together (via TypoScript array "merging") so that our basic configuration is always loaded in any case.

Any candidates for a patch? :) I would also like to see that in 4.5.x, because else we will carry on that problem forever (3 years at least).

I've got the same problem here with two installations regarding the not appearing context menu but in my installations the mentionend CONF_VARS never was set.

Additionally the new "create page"-wizard doesn't show any icons but one "missing img"-icon. Moving pages + renaming them's working. Cleared all caches, re-installed t3-skin + all not necessary extensions but without success.

If you need additional infos please say so + say what exactly you need.

Michael, go to the Admin Tools > User Admin and check the "TSconfig" of your users (tick the checkbox, click "Update"). You should see a tree of TSconfig for each user. Check if you have a branch called:

options.contextMenu. ...

If you don't then there is something in your installation that is overwritting $TYPO3_CONF_VARS['BE']['defaultUserTSconfig']. Grep for it in your localconf.php file and also in ext_localconf / ext_tables.php of your extensions, maybe you find something.

Shame on me, there was a left over $TYPO3_CONF_VARS['BE']['defaultUserTSconfig'] indeed. Fixed now, thanks a lot!

BTW. seems like options.contextMenu doesn't lead to the mentioned behavior as this is set in my installation but the context menu is working anyway. So it's only the the "defaultUserTSconfig"-setting.

What if the install tool`d grep the localconf.php for any leftover, empty defaultUserTsconfig and delete the entry if empty?

Actually, I just found out / remembered that we have an API for adding new default UserTS without touching the "defaultUserTSconfig", so I guess this is what the pagetree should also use:

t3lib_extMgm::addUserTSConfig(' ... ');

This should then be added at some central place like t3lib/tables.php

What do you think?

I would really prefer using such a call.. also for the default bookmark options.
I think sb. started with 4.3 or 4.4 to preset the value of defaultUserTSconfig and some people (including me..) jumped up that train.

Ah, that was the reason why my contextmenu didn't show up ;)

I think this is not a bug: in localconf.php one should set
$TYPO3_CONF_VARS['BE']['defaultUserTSconfig'] .= 'whatever = foo'; (mind the dot)
to append /overwrite config_default.php defaults.

The issue only just popped up now, since we started to use the text field from core side for defaults.