[TYPO3-english] Bug in TMENU with HMENU special=directory?

[Xavier Perseguers]

Hi,

I have following tree:

root
|-- page1
| `-- page1.1
| `-- page1.1.1
|-- page2
| `-- page2.1
`-- sysfolder
|-- page3
| `-- page3.1
| `-- page3.1.1
`-- page4

I have create a menu with

lib.menu = HMENU
lib.menu.1 = TMENU
lib.menu.1 {
expAll = 0
# standard stuff for menu
}
lib.menu.2 < lib.menu.1
lib.menu.3 < lib.menu.2

It shows me

page1
page2

Then when I click on page1 it shows me next level:

page1
page1.1
page2

And finally when I click on page1.1 it shows me third level. Great.

Now I have a special menu for pages under my sysfolder (uid=12):

lib.otherMenu = HMENU
lib.otherMenu.special = directory
lib.otherMenu.special.value = 12

lib.otherMenu.1 = TMENU
lib.otherMenu.1 {
expAll = 0
# same stuff as for lib.menu.1
}
lib.otherMenu.2 < lib.otherMenu.1
lib.otherMenu.3 < lib.otherMenu.2

Using special=directory only shows me 1st level, 2nd level is never shown.

If I change lib.otherMenu.1.expAll = 1, then I see all levels but that's
not what I want...

[StephenBungert]

I believe special = directory works this way, I don't think it checks for
sub-menus.

-----

[Xavier Perseguers]

Post by StephenBungert
I believe special = directory works this way, I don't think it checks for
sub-menus.

Well, my first menu is able to detect that there is subpages with
(ACTIFSUB and other related options). expAll = 1 shows other pages. I
don't understand why I could not use it as a standard menu that starts
with a given page.

[Xavier Perseguers]

Hi,

Post by Xavier Perseguers

Post by StephenBungert
I believe special = directory works this way, I don't think it checks for
sub-menus.

Well, my first menu is able to detect that there is subpages with
(ACTIFSUB and other related options). expAll = 1 shows other pages. I
don't understand why I could not use it as a standard menu that starts
with a given page.

Actually *there is* a bug when using mount points. I'm trying to track
it down. Again, if I have this tree (slightly modified from initial
post, I added a MP):

root
|-- [1] page1
| `-- [2] page1.1
| `-- [3] page1.1.1
|
|-- [4] page2
| `-- [5] page2.1
|
|-- [6] pageMP (--> 7)
|
`-- [7] sysfolder
|-- [8] page3
| `-- [9] page3.1
| `-- [10] page3.1.1
|
`-- [11] page4

If I generate a menu with

----------------------
lib.otherMenu = HMENU
lib.otherMenu.special = directory
lib.otherMenu.special.value = 1

lib.otherMenu.1 = TMENU
lib.otherMenu.1 {
expAll = 0
# standard menu stuff with ACT, NO, IFSUB, ...
}
lib.otherMenu.2 < lib.otherMenu.1
lib.otherMenu.3 < lib.otherMenu.2
----------------------

I get a menu with page1.1 (2). If I activate it, I see next nevel
(page1.1.1 uid 3).

If I change entry point and set

lib.otherMenu.special.value = 6

I get a menu with page3 (8) and page 4 (11) but when I activate page3
(8), I don't get page3.1 (9).

[Xavier Perseguers]

Hi,

Post by Xavier Perseguers

Post by Xavier Perseguers

Post by StephenBungert
I believe special = directory works this way, I don't think it checks for
sub-menus.

Well, my first menu is able to detect that there is subpages with
(ACTIFSUB and other related options). expAll = 1 shows other pages. I
don't understand why I could not use it as a standard menu that starts
with a given page.

Actually *there is* a bug when using mount points. I'm trying to track
it down. Again, if I have this tree (slightly modified from initial

line 330 of class.tslib_menu.php:

// Notice: The automatic expansion of a menu is designed to work only
when no "special" modes (except "directory") are used.

But actually it does work when no MP is involved...

[Xavier Perseguers]

Post by Xavier Perseguers
// Notice: The automatic expansion of a menu is designed to work only
when no "special" modes (except "directory") are used.
But actually it does work when no MP is involved...

I read it wrong. Actually it should work. Great! It won't be a feature
request but a bug request ;-)

[Xavier Perseguers]

Post by Xavier Perseguers
Actually *there is* a bug when using mount points. I'm trying to track
it down. Again, if I have this tree (slightly modified from initial
root
|-- [1] page1
| `-- [2] page1.1
| `-- [3] page1.1.1
|
|-- [4] page2
| `-- [5] page2.1
|
|-- [6] pageMP (--> 7)
|
`-- [7] sysfolder
|-- [8] page3
| `-- [9] page3.1
| `-- [10] page3.1.1
|
`-- [11] page4
If I generate a menu with
----------------------
lib.otherMenu = HMENU
lib.otherMenu.special = directory
lib.otherMenu.special.value = 1
lib.otherMenu.1 = TMENU
lib.otherMenu.1 {
expAll = 0
# standard menu stuff with ACT, NO, IFSUB, ...
}
lib.otherMenu.2 < lib.otherMenu.1
lib.otherMenu.3 < lib.otherMenu.2
----------------------
I get a menu with page1.1 (2). If I activate it, I see next nevel
(page1.1.1 uid 3).
If I change entry point and set
lib.otherMenu.special.value = 6
I get a menu with page3 (8) and page 4 (11) but when I activate page3
(8), I don't get page3.1 (9).

Seems to be something like that:

http://bugs.typo3.org/view.php?id=10439

[Xavier Perseguers]

FYI: Bug report created, patch available:
http://bugs.typo3.org/view.php?id=11224

Patch will be pending in core list in a few minutes.

[Andreas Burg]

Xavier

Post by Xavier Perseguers
root
|-- page1
| `-- page1.1
| `-- page1.1.1
|-- page2
| `-- page2.1
`-- sysfolder
|-- page3
| `-- page3.1
| `-- page3.1.1
`-- page4

change your sysfolder to a shortcut, then your menu behaves like you want.

[Xavier Perseguers]

Hi Andreas,

Post by Andreas Burg

Post by Xavier Perseguers
root
|-- page1
| `-- page1.1
| `-- page1.1.1
|-- page2
| `-- page2.1
`-- sysfolder
|-- page3
| `-- page3.1
| `-- page3.1.1
`-- page4

change your sysfolder to a shortcut, then your menu behaves like you want.

I thought this kind of trick would solve the problem. However, the patch
is easily done and it's a bug that should be fixed.

Thanks anyway.

[Andreas Burg]

Xavier

Post by Xavier Perseguers
I thought this kind of trick would solve the problem. However, the patch
is easily done and it's a bug that should be fixed.

I agree, that a bug has to be fixed in any case.

[David Bruchmann]

Hi Xavier,

I've never had the idea to create a pagetree under sysfolders.
I saw this in some foreign installations and was a bit astonished about
that.
It's nice beeing able to create compatible Menus after your patch but
the sense of this combination still is not clear for me.

Regards
David

[Xavier Perseguers]

Hi David,

Post by David Bruchmann
Hi Xavier,
I've never had the idea to create a pagetree under sysfolders.
I saw this in some foreign installations and was a bit astonished about
that.
It's nice beeing able to create compatible Menus after your patch but
the sense of this combination still is not clear for me.

A shortcut does not make any sense for me. I have a page tree with many
websites under the world root.

Now, I want some pages to be shared among websites (aka domains). For
instance login page, impressum, help, contact, and other "intranet"
pages with data only shown when logged in.

What I do for these later is to create an "Intranet" mount page in each
website whose target is the sysfolder containing my shared pages. Why
would I create a a shortcut? I mean, perhaps it works, OK, but a
sysfolder is a repository for some stuff and my stuff are pages in this
case. Why would I use a shortcut page or even a standard page? Logically
it does not make sense to me.

[David Bruchmann]

----- Urspr?ngliche Nachricht -----
Von: Xavier Perseguers <typo3 at perseguers.ch>
Gesendet: Sonntag, 7. Juni 2009 20:42:22
An: typo3-english at lists.netfielders.de
CC:
Betreff: Re: [TYPO3-english] Bug in TMENU with HMENU special=directory?

Post by Xavier Perseguers
Hi David,

Post by David Bruchmann
Hi Xavier,
I've never had the idea to create a pagetree under sysfolders.
I saw this in some foreign installations and was a bit astonished about
that.
It's nice beeing able to create compatible Menus after your patch but
the sense of this combination still is not clear for me.

A shortcut does not make any sense for me. I have a page tree with many
websites under the world root.
Now, I want some pages to be shared among websites (aka domains). For
instance login page, impressum, help, contact, and other "intranet"
pages with data only shown when logged in.
What I do for these later is to create an "Intranet" mount page in each
website whose target is the sysfolder containing my shared pages. Why
would I create a a shortcut? I mean, perhaps it works, OK, but a
sysfolder is a repository for some stuff and my stuff are pages in this
case. Why would I use a shortcut page or even a standard page? Logically
it does not make sense to me.

Hi Xavier,

I didn't propose the solution with the shortcut so don't fix me at this
point ;-) But you are free to use normal pages instead.

Normally I add Sysfolders as Storage for administrative elements. Even
if there are stored content-elements or users I have a special folder
where rights can be set either by elements or by directory.
Mixing up those folders with content-pages is an option and perhaps it
makes sense in some cases but this concept is new to me because I
strictly separated mentioned elements, in other words: sysfolders I use
for elements that are independent from pagetree, for content or viewable
pages that means it has to be included by other elements in active pagetree.

Best Regards
David

[Andreas Burg]

Xavier

Post by Xavier Perseguers
What I do for these later is to create an "Intranet" mount page in each
website whose target is the sysfolder containing my shared pages. Why
would I create a a shortcut? I mean, perhaps it works, OK, but a
sysfolder is a repository for some stuff and my stuff are pages in this
case. Why would I use a shortcut page or even a standard page? Logically
it does not make sense to me.

perhaps it's because every webpage needs a rootline, and if you create a pagetree within a
sysfolder, there is no rootline because the sysfolder cuts it of. By using a mountpoint later, you
complete this missing rootline.

[JoH asenau]

Post by Andreas Burg
perhaps it's because every webpage needs a rootline, and if you
create a pagetree within a sysfolder, there is no rootline because
the sysfolder cuts it of. By using a mountpoint later, you complete
this missing rootline.

AFAIK it's just vice versa: The mountpoint doesn't complete anything and the
rootline is missing due to the fact that the pages are not located within
the same page tree.
With no rootline available at all, the automatic expansion of sublevels
won't work, because it is using "entryLevel" internally.
This is necessary to change the default behaviour of "special" HMENU types,
that are usually not supporting automatic expansion at all, and it will work
for "directory" only.

HTH

Joey

[Xavier Perseguers]

Hi,

Post by JoH asenau

Post by Andreas Burg
perhaps it's because every webpage needs a rootline, and if you
create a pagetree within a sysfolder, there is no rootline because
the sysfolder cuts it of. By using a mountpoint later, you complete
this missing rootline.

AFAIK it's just vice versa: The mountpoint doesn't complete anything and the
rootline is missing due to the fact that the pages are not located within
the same page tree.
With no rootline available at all, the automatic expansion of sublevels
won't work, because it is using "entryLevel" internally.
This is necessary to change the default behaviour of "special" HMENU types,
that are usually not supporting automatic expansion at all, and it will work
for "directory" only.

special HMENU work really great with automatic expansion, I explained it
in my bug report. Only the combination of mount point and sysfolder make
it fail.

[JoH asenau]

Post by Xavier Perseguers
special HMENU work really great with automatic expansion, I explained
it in my bug report. Only the combination of mount point and
sysfolder make it fail.

According to the comments in core only special=directory does.
Maybe I have been missing something , but AFAIK this has not been changed
recently.

And to explain it more detailed:
If you are using a sysfolder that is not part of the page tree of a certain
domain/root, there is no way to activate automatic expansion regardless if
you are using a mount point or not.

Example:
Create a sysfolder and a rootpage on the same level.
Create trees for both, the sysfolder and the rootpage.
Now setup a TS menu that i using
special=directory
special.value = 123
with 123 being the uid of the sysfolder.

If you use this menu on one of the pages located in your rootpage-tree, it
simply can't expand automatically, because it is not part of the page tree
and thus can't "know"
a) about the domain used by this particular page tree
b) the root page used by this particular domain
c) the "level" (based on the original root page) of the page currently shown

You don't need to use a mount point to trigger this behaviour, since by
design it should be enough to just place the sysfolder outside of the
rootline.

But maybe I am still missing something.

Joey