[TYPO3-core] RFC: #8939+#3705: Menu sitemap doesn't respect pages field
Ernesto Baschny [cron IT]
ernst at cron-it.de
Thu Jul 10 19:53:48 CEST 2008
Hi,
this is the "good old" http://bugs.typo3.org/view.php?id=3705. The
mentioned TypoScript lines are probably ones that all agencies start
with in their default TypoScript when creating a new site.
Currently I believe there is no backwards compatibility problem with
changing that, as Steffen noticed, if the field was empty before, the
behaviour doesn't change.
So +1 on that change, even without a [compatVersion] checking.
Cheers,
Ernesto
Steffen Kamper wrote: on 10.07.2008 17:07:
> this is an SVN patch request.
>
> Type: Bugfix
>
> Bugtracker references:
>
> http://bugs.typo3.org/view.php?id=8939
>
> Branches: 4.2, trunk
>
>
> Problem:
> there is something missing in
> tt_content.menu.20.2
>
> All other menu types are copied from default and modified, so they have
> special = list
> special.value.field = pages
>
> Solution:
> Modification is one line:
> instead of 2 = HMENU
> use
> 2 < .default
> and all is done.
>
> Leaving field pages empty shows complete sitemap, so it doesn't break
> backwards compatibility.
>
> vg Steffen
>
More information about the TYPO3-team-core
mailing list