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

Frontend Crash When Loading News with Main Category and Sub-Categories in TYPO3 V13 [news_pi1] #2597

Open
HimanshuRamavat07 opened this issue Dec 19, 2024 · 3 comments

Comments

@HimanshuRamavat07
Copy link

Bug Report

Current Behavior
I've encountered an issue with the news listing on my site (Plugin -> News article list (incl. detail view) [news_pi1]).

The problem arises when I try to load a main category that contains numerous sub-categories. The frontend is crashing and fails to load. Here's a screenshot for the reference: https://i.imgur.com/4AbPVH9.png.

Below is the current configuration of the plugin:
categoryConjunction: or
includeSubCategories: true
All other settings are at their default values.

You can find the plugin settings screenshot here: https://i.imgur.com/WCVkYwm.png.

Environment

  • TYPO3 version: 13.4.2
  • news version: 12.2.0
  • Is your TYPO3 installation set up with Composer (Composer Mode): yes
  • OS: OSX 15.1.1

Additional context
With the same database and same news extension listing news is working fine In TYPO3 V12 .

@georgringer
Copy link
Owner

what if you start limitting the catagories - either by changing it directly in the repository or by limiting in the plugin or e.g. deleting for testing categories?

i am pretty sure this is sadly a core issue and not a news issue

@HimanshuRamavat07
Copy link
Author

If I select all categories (parent and child) and disable the includeSubCategories option (screenshot: https://i.imgur.com/vgOoS78.png), it works. I could reconfigure the plugin by manually selecting categories, but unfortunately, it’s used in 95 places.

PS: I have not extended the news extension.

@georgringer
Copy link
Owner

thanks for your feedback. there needs to be kind of an error or maybe just a slowlog entry of the DB if logging is enabled but I fear I can't really do anything within the extension. A possible solution could be to use additional custom queries doing the heavy queries before and modify the original query to avoid the tons of joins

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants