Feature #37742
Optimize handling of blog PID
| Status: | Needs Feedback | Start date: | 2012-06-05 | |
|---|---|---|---|---|
| Priority: | Won't have this time | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 1 (View) |
Description
t3blog_div::getBlogPid is commented as "Returns the blog storage folder pid". Therefore I assume that it is intended to allow setups where you have the blog posts in a folder and a separate page for displaying the blog.
Is that correct?
Because it doesn't work correctly. If the blogPid is set by TypoScript or $GLOBALS['alternativeBlogPid'] (what would be the reason for setting it this way?), all links are generated with that blogPid as Typolink parameter. Therefore they would point to the storage folder and no link is generated.
So what is blogPid? Is it "blogStoragePid" or "blogViewPid"? Would it be OK for you to change it in a way that you can configure both values by TypoScript?
History
Updated by Dmitry Dulepov 11 months ago
- Priority changed from Should have to Won't have this time
t3blog always stores entries for the blog on the same page where the blog is displayed. So you can't store that in the sysfolder. The only exception is pi2: there you can have some widgets to show blog entries from another page.
Why was it made like that? Who knows...
Updated by Dmitry Dulepov 11 months ago
- Status changed from New to Needs Feedback
Updated by Lorenz Ulrich 11 months ago
T3BLOG would be interesting for corporate blogging if it could handle multiple sysfolders that can be configured.
I'm using pi2 and can tell you that the widgets are indeed working and displaying correct content, but when it comes to linking from the widgets (e.g. archive menu, latest posts) and the posts are not on the same page as the widgets, the links are not working.
That's why I'm asking to overwork the "blogPid" concept.
Updated by Felix Nagel 11 months ago
As Dmitry already said, some pi2 widget work on other pages, for example the latest posts widget. Including links to the blog page. Perhaps there something wrong with your configuration?
I agree that it would be nice to have t3blog records in a storage folder. This would help to improve the naming of the blog pages in t3blog modules.
Updated by Lorenz Ulrich 11 months ago
Let me make an example:
The widget latestPostNav generates a link to the blog post (a visible page containing the necessary widgets). The pid to link for is the field "blogUid". "blogUid" is set in class.latestPostNav.php:
'blogUid' => t3blog_div::getBlogPid(),
But the same method is getting all the blog posts from the same pid:
$list = t3blog_db::getPostByWhere('pid = '.t3blog_div::getBlogPid(),'date DESC', '0,'.$numberOfItems );
Therefore it is impossible (without manipulating TypoScript) to have
- one folder for the blog posts
- one page for displaying the blog
To make that possible, it would be nice to separate between "blogStoragePid" and "blogViewPid". For those who want to have posts and views on the same page, this can be the same pid. But for those who want to separate it, they could configure it to use different pids.
Updated by Lorenz Ulrich 11 months ago
BTW, don't get me wrong: I don't expect you to do all the changes necessary, I'm just asking your opinion. If you think it would be cool and you actually would merge it in the extension, I can invest some time to make it work like that.
But if you don't want this feature anyway, I will look out for other solutions.
Updated by Alexander Bigga 11 months ago
I would like this feature (for pi2) and I think it won't be too difficult.
Currently it's not nice to have the widgets and the page content and blog elements mixed on one page. Even if you have some houndreds blog posts, try finding the widget elements makes fun...
+1 from mea
Lorenz Ulrich wrote:
BTW, don't get me wrong: I don't expect you to do all the changes necessary, I'm just asking your opinion. If you think it would be cool and you actually would merge it in the extension, I can invest some time to make it work like that.
But if you don't want this feature anyway, I will look out for other solutions.