List Posts by Demand with Categories outside of Blogpage
izaquieltome opened this issue · comments
Feature Request
Currently, it is not possible to use the "list of posts by demand configuration" on Pages that are not configured as "Blog Page".
In some cases (as I learn by now) it would be great to have the possibility to use the plugins without the need of changing the Page Type because sometimes they just should direct a user from a content page into the blog - but not BE the Blog.
Currently, I cannot select a Blog-Category as long it's a normal Page. So I am really limited in flexibility. Like I cannot put a List-Plugin on a content page to show a content-related list of blogposts.
WOuld be great if plugins would not be limited to page type configuration.
by the way: same with Tags: I could not use Tags outside of Blog-Pages as a demand configuration.
We had the same problem a while ago when I wanted to add a category list plugin on a normal page.
It would be great if that would work!
+1
Both plugin types ("list of posts by demand configuration" and "list of posts by category") work with TYPO3 10.4.27 and blog 11.0.2 on standard pages with doktype 1. As far as i can remember it didn't work with blog 10. Make sure you included the static blog-typoscript in your template.
For "list of posts by demand configuration" i found out that you need to add this to TCEFORM in order to get the categories and tags listed in the plugin, which is true for every page type:
TCEFORM.tt_content.pi_flexform.blog_demandedposts.sDEF.settings\.demand\.authors.PAGE_TSCONFIG_ID = ID_of_Page_Data
TCEFORM.tt_content.pi_flexform.blog_demandedposts.sDEF.settings\.demand\.tags.PAGE_TSCONFIG_ID = ID_of_Page_Data
TCEFORM.tt_content.pi_flexform.blog_demandedposts.sDEF.settings\.demand\.categories.PAGE_TSCONFIG_ID = ID_of_Page_Data
The documentation only says
TCEFORM.pages.tags.PAGE_TSCONFIG_ID = ID_of_Page_Data
TCEFORM.pages.authors.PAGE_TSCONFIG_ID = ID_of_Page_Data
TCEFORM.pages.categories.PAGE_TSCONFIG_ID = ID_of_Page_Data
which is not enough.
@benjaminkott: This is missing in the docs or is there another approach to make it work?