How can I dynamically link all other Pages on all Sites in a Navbar in Typo3(11.5.12)?

user_19340572 0
Viewed 116

I am using Typo3 version 11.5.12 with a sitepackage generated on the sitepackage builder by Benjamin Kott.

I made a Navbar in the partials folder, that I use on every Page on every Site. It contains links to all Subpages that are on the same Site, however I also want to link all Subpages from all other Sites. Currently it only shows the children of the Site I am on.

I tried fixing this by making a parent Site where I store all other Sites, however that defeats the purpose of splitting those sites at all.

Is there a way to dynamically link all other Sites?

I made my Navbar using this code:

<a href="#" class="open_menu bg-light">
    <f:for each="{mainnavigation}" as="navPoint" iteration="i">
        <div><a href="{navPoint.link}" class="f-heading f-22 link color-white mb-20">{navPoint.title}</a> </div>
    </f:for>
</a>

Edit: Image of the page tree

Edit 2: Snippet from setup.typoscript:

page = PAGE
page {
    typeNum = 0
    shortcutIcon = EXT:erstes_template/Resources/Public/Icons/favicon.ico

    10 = FLUIDTEMPLATE
    10 {
        # Template names will be generated automatically by converting the applied
        # backend_layout, there is no explicit mapping necessary anymore.
        #
        # BackendLayout Key
        # subnavigation_right_2_columns -> SubnavigationRight2Columns.html
        #
        # Backend Record
        # uid: 1 -> 1.html
        #
        # Database Entry
        # value: -1 -> None.html
        # value: pagets__subnavigation_right_2_columns -> SubnavigationRight2Columns.html
        templateName = TEXT
        templateName {
            cObject = TEXT
            cObject {
                data = pagelayout
                required = 1
                case = uppercamelcase
                split {
                    token = pagets__
                    cObjNum = 1
                    1.current = 1
                }
            }
            ifEmpty = Default
        }
        templateRootPaths {
            0 = EXT:erstes_template/Resources/Private/Templates/Page/
            1 = {$page.fluidtemplate.templateRootPath}
        }
        partialRootPaths {
            0 = EXT:erstes_template/Resources/Private/Partials/Page/
            1 = {$page.fluidtemplate.partialRootPath}
        }
        layoutRootPaths {
            0 = EXT:erstes_template/Resources/Private/Layouts/Page/
            1 = {$page.fluidtemplate.layoutRootPath}
        }
        dataProcessing {
            10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
            10 {
                references.fieldName = media
            }
            20 = TYPO3\CMS\Frontend\DataProcessing\MenuProcessor
            20 {
                levels = 2
                includeSpacer = 1
                as = mainnavigation
            }
            #
            #I tried to implement the new code here!
            #
        }
    }

    meta {
        viewport = {$page.meta.viewport}
        robots = {$page.meta.robots}
        apple-mobile-web-app-capable = {$page.meta.apple-mobile-web-app-capable}
        description = {$page.meta.description}
        description {
            override.field = description
        }
        author = {$page.meta.author}
        author {
            override.field = author
        }
        keywords = {$page.meta.keywords}
        keywords {
            override.field = keywords
        }
        X-UA-Compatible = {$page.meta.compatible}
        X-UA-Compatible {
            attribute = http-equiv
        }

        # OpenGraph Tags
        og:title {
            attribute = property
            field = title
        }
        og:site_name {
            attribute = property
            data = TSFE:tmpl|setup|sitetitle
        }
        og:description = {$page.meta.description}
        og:description {
            attribute = property
            field = description
        }
        og:image {
            attribute = property
            stdWrap.cObject = FILES
            stdWrap.cObject {
                references {
                    data = levelfield:-1, media, slide
                }
                maxItems = 1
                renderObj = COA
                renderObj {
                    10 = IMG_RESOURCE
                    10 {
                        file {
                            import.data = file:current:uid
                            treatIdAsReference = 1
                            width = 1280c
                            height = 720c
                        }
                        stdWrap {
                            typolink {
                                parameter.data = TSFE:lastImgResourceInfo|3
                                returnLast = url
                                forceAbsoluteUrl = 1
                            }
                        }
                    }
                }
            }
        }
    }

    includeCSSLibs {

    }

    includeCSS {
        erstes_template_layout = EXT:erstes_template/Resources/Public/Css/bootstrap.min.css
    }

    includeJSLibs {

    }

    includeJS {

    }

    includeJSFooterlibs {

    }

    includeJSFooter {
        erstes_template_scripts = EXT:erstes_template/Resources/Public/JavaScript/Dist/bootstrap.bundle.min.js
    }
}

Edit3: Pagetree vs link output

typo3-11.x typo3
2 Answers

In general you can build your menus with typoscript, where you need to select which kind of links should be generated. A typical menu would be: show subpages from page with id (or in your case: show subpages from pages with ids from list), recursion level is optional.

The old way: use a HMENU object and define the complete mark-up in typoscript.
Or the new way with a dataprocessor/ menuprocessor

In the first way you only need to assign the output to a fluid variable to include in your page template, or you call it with the f:cObject viewhelper.

With the menuprocessor you get a fluid variable which contains an array with the links you can display with fluid (e.g. in a partial)

if you use further extensions (like ext:vhs) you may get viewhelpers which generate menus or at least the fluid variables with the menu data.

ADD:

page.10.dataProcessing {
   30 = TYPO3\CMS\Frontend\DataProcessing\MenuProcessor
   30 {
      levels = 2
      as = headerMenu
      expandAll = 1
      includeSpacer = 1
      special = directory
      special.value = 12,23,34
   }
}

you might oversee the small hint in the documentation to MenuProcessor just before the Example:

Important
Additionally all HMENU options are available.

in the HMENU options you can find additional options to configure your menu. In this case I consider it a menu of the pages 12,23 and 34 with their subpages.
The important option is special with special.value where you control the kind of menu and which base pages are used.

user_67963540
user_23337540
Related