Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Endless loop in CType menu_section #715

Closed
kitzberger opened this issue Apr 15, 2024 · 0 comments · Fixed by #719
Closed

Endless loop in CType menu_section #715

kitzberger opened this issue Apr 15, 2024 · 0 comments · Fixed by #719
Labels
bug Something isn't working

Comments

@kitzberger
Copy link
Contributor

Describe the bug

There seems to be a endless loop for CType menu_section when rendering itself.

To Reproduce
Steps to reproduce the behavior:

  1. Create a CType menu_section on any page
  2. Make sure it's got sectionIndex=1
  3. Try to render the frontend

Expected behavior
A clean section index being rendered.

Error
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 36864 bytes) in /var/www/vendor/typo3/cms-frontend/Classes/ContentObject/Menu/MenuContentObjectFactory.php on line 52

TYPO3 version and TYPO3 Headless version
TYPO3 12 / EXT:headless 4.x

Additional context

Problem is that the items of the section index are all being fetched via FriendsOfTYPO3\Headless\DataProcessing\DatabaseQueryProcessor and rendered as tt_content is defined. And that's the cause of the endless loop.

Suggestion

Only render those fields of the items that are really necessary: uid and header that is?

tt_content.menu_section.fields.content.fields.menu.dataProcessing.10.dataProcessing.20 {
        fields {
                  uid = TEXT
                  uid.field = uid
                  header = TEXT
                  header.field = header
        }
}
@kitzberger kitzberger added the bug Something isn't working label Apr 15, 2024
twoldanski added a commit that referenced this issue Apr 23, 2024
- restore behavior to output whole record if rendering definition is not set for query processor (solves #718)
- align menus to render less data (only uid, header & processed image if set) to match core fluid-style-content behavior & solve performance issues (solves #715)
- code cleanup
lukaszuznanski pushed a commit that referenced this issue May 8, 2024
- restore behavior to output whole record if rendering definition is not set for query processor (solves #718)
- align menus to render less data (only uid, header & processed image if set) to match core fluid-style-content behavior & solve performance issues (solves #715)
- code cleanup
lukaszuznanski pushed a commit that referenced this issue May 8, 2024
- restore behavior to output whole record if rendering definition is not set for query processor (solves #718)
- align menus to render less data (only uid, header & processed image if set) to match core fluid-style-content behavior & solve performance issues (solves #715)
- code cleanup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant