Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS (I didn't try, but I guess so)
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

When creating a new post via Extbase, the page doktype is set to 0.

Steps to Reproduce

1. Run the following code from your action/command:

        $post = $this->objectManager->get(Post::class);
        $post->setPid(1);
        $post->setTitle('foo bar');

        $this->postRepository->add($post);

        $this->persistenceManager->persistAll();

2. Look for a page titled "foo bar" in the TYPO3 backend.

Expected behavior: A new page with the doktype set to 137 is created.

Actual behavior: A new page with an invalid doktype (0) is created.

Versions

t3g/blog: 9.1.1
typo3: 9.5.5

On the detail page of a blog post I used to place the 'authors' frontend plugin which does show the author as expected in the main language. Unfortunately it does not show the author in the translated language anymore. It worked fine in TYPO3 7.x. But now there is just an empty <div> tag.

worked in (last tested):
T3 7.6.32 with blog 7.6.1

doesn't work anymore in (tested):
T3 9.5.4 and blog 9.0.0
T3 9.5.3 and blog 9.0.1
T3 9.5.3 and blog 9.0.1
T3 8.7.22 and blog 8.7.2

I am thinking, it might even be a good idea to have the authors as a translatable object?

(done all upgrade-wizzard-thingies, cleared all caches, deactivated custom templating overrides, deleted and recreated the plugin-content-object on the detail pages)

Feature Request

It would be great if new blog posts could be posted automatically on social media channels like Twitter or Facebook.
Therefor it should be possible to make the publication dependent on one or more selected catagories, tags or authors. For example if a certain author has published a new blog post in TYPO3 then only this blog post should be published on a certain social media channel. (For example Max Mustermann is a sport reporter and Maxim Mustermann is responsible for plants. If Max writes a new blog post this should automatically be published on the sport Twitter account and if Maxim publishes a new blog post, this should be published on another Twitter account.)

So, it must be possible to create different social media configurations and it has to be possible to create something like an "e-mail" filter. If a certain filter (author, tag, categorie) is set, publish the blog post on a certain social media channel. Furthermore I think it would be good to have an extra field for the text which should be shown on the social media post.

The category and tag plugin should allow the editor to apply a filter. That way, the editor can create pages which list blog posts by a concrete category or tag.

The same would be cool for authors too.

Reporter: Björn Jacob

Created: 14.02.18 09:13
Updated: 6 days ago

Service-Desk: TE-68
Development: EXTBLOG-110

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

With plugin.tx_blog.settings.notifications.CommentAddedNotification.admin = 1 i get the following error if i comment in FE:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Return value of T3G\AgencyPack\Blog\Notification\CommentAddedNotification::getLanguageService() must be an instance of TYPO3\CMS\Core\Localization\LanguageService, null returned | TypeError thrown in file /usr/www/users/user/t3blog/typo3conf/ext/blog/Classes/Notification/CommentAddedNotification.php in line 57. Requested URL: https://domain.tld/site.html?tx_blog_commentform%%5Baction%%5D=addComment&tx_blog_commentform%%5Bcontroller%%5D=Comment&cHash=1e0dc52d56ef537fecdbb7e5d194b284

Changing function getLanguageService in blog/Classes/Notification/CommentAddedNotification.php from:

protected function getLanguageService(): LanguageService
{
    return $GLOBALS['LANG'];
}

to:

protected function getLanguageService(): LanguageService
{
    if ($GLOBALS['LANG'] === null) {
        $GLOBALS['LANG'] = GeneralUtility::makeInstance(LanguageService::class);
    }
    return $GLOBALS['LANG'];
}

solved that problem.

Best regards,
Oliver

Versions

PHP 7.2
T3 9.5.5
blog 9.1.1

Hi there,

I have a strange bug and maybe someone can confirm this behaviour:

Bug Report

I wanted to rename a category from a news article (EXT:news) and everytime the category was deleted from every news article where the category was used. So I have over 100 news articles and this category I wanted to rename was deleted from every article...

I deactivated almost every extension and finally, with EXT:blog deactivated, the renaming worked.
The workaround is now, everytime I want to rename a category which is used in a news article I have to deactivate the blog extension first. Rename the category and then activate the blog again.
This is not very practical...Also editors don't have permissions to activate/deactivate extensions.

Renaming categories which I use inside a blog post works without deleting anything... So I wonder what causes this problem?

Prerequisites

• [x ] Can you reproduce the problem on TYPO3 v8.7.25 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Steps to Reproduce

Install EXT:news and EXT:blog and try to rename a category used in a news article. Would be nice if someone can confirm this issue...

Expected behavior:
I would like that the categories I use inside the news extension are not deleted when I rename them and EXT:blog is activated.

Actual behavior:

The category I want to rename is deleted from every news article where this category is used.

Versions

TER version TYPO3 8.7.25
news 7.2
blog: 8.7.4

Reporter: Benjamin Kott

Created: 7 hours ago
Updated: 7 hours ago

Development: EXTBLOG-158

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

HTML Templates contain fluid namespace definitions on unsupported elements.

<div 
    xmlns:f="http://www.w3.org/1999/html" 
    xmlns:blog="http://typo3.org/ns/T3G/AgencyPack/Blog/ViewHelpers"
>
    ...
</div>

Steps to Reproduce

1. Install Blog Extension
2. Include Tempalte
3. Insert "Blog: List of posts" plugin
4. Check frontend markup

Expected behavior: [What you expected to happen]

Namespaces for fluid viewhelper resolving should not be rendered in frontend

Actual behavior: [What actually happened]

Invalid namespaces are rendered in the frontend.

Versions

All versions

Code example from a 3rd party plugin:

    <f:for each="{tags}" as="tag">
        <blog:link.tag tag="{tag}" class="blog-tag">
            {tag.title}
        </blog:link.tag>
    </f:for>

This would create a url with a wrong plugin prefix:

/de/tags/?tx_blogextender_tags%5Baction%5D=listPostsByTag&tx_blogextender_tags%5Bcontroller%5D=Post&tx_blog_tag%5Btag%5D=1&cHash=xxx

To display posts by tag correctly, it should always look like:

/de/tags/?tx_blog_tag%5Baction%5D=listPostsByTag&tx_blog_tag%5Bcontroller%5D=Post&tx_blog_tag%5Btag%5D=1&cHash=xxx

The problem is that a call UriBuilder misses $extensionName parameter.

Hi Everybody,
using Typo3 7.6.31 at the moment and the according blog extension working with this Typo version.

Trying to make some own templates for the extension.
I want to show an image which is specified under the blog page Resource Tab.
In my template "Post.html" I want to show this image.
Debugging of {post.media} shows the follwing:

I could show the image when typing manually <f:image src="525" treatIdAsReference="1" />, but I do not know how to get the uid out of {post.media}.

Does somebody know this and can help me?

Regards,
Chequille

Bug Report

The comments are enabled for a specific blog post.
I noticed that when I open this blog post that an instant connection to the Google-Server is established. I think that is not GDPR compliant.

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS

Description

A connection to the Google server is established, once I active the comment option for a blog post.

Steps to Reproduce

1. open blog post and look at the console

Expected behavior:
I don't want a connection to the Google server.

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

Plugins are not listed in the new content element wizard, and are only available through the dropdown selector for the list_type. This makes it for new users hard to discover the elements.

Steps to Reproduce

1. Open New Content Element Wizard
2. Blog Plugins are missing

Expected behavior: [What you expected to happen]

New Content Element wizard shows plugins.

Actual behavior: [What actually happened]

New Content Element Wizard does not show plugins.

If comments are globally disabled, there is no need to show "0 comments" for every single post. So I suggest adding a condition to the Partial Post/Meta.html, line 25:

<f:if condition="

{settings.comments.active}
">
<f:alias map="{commentCount: '<f:count subject='

{post.activeComments}
' />'}">
...

Frank Nägler added a comment - 22.09.17 09:53

In this case you can override your template and remove the part from template / partial.
I am not a big fan of a lot conditions, I prefer clean and small templates.

Sven Teuber added a comment - 26.09.17 11:59

Overriding templates means checking them for changes with each update of the extension.

That may seem like a small task, but with 300+ downloads of your extension, that's a potential of 300+ "small tasks" which are, in sum, a rather large task.

I think it may be more efficient to provide meaningful defaults in the "core" product than to have each user "in the field" do the same override individually. Especially since, if there is a "global switch" to turn off comments, it's expected behaviour that all comment-related output will be switched off, too, isn't it?

Reporter: Sven Teuber

Created: 21.09.17 14:10
Updated: 26.09.17 11:59

Service-Desk: TE-59

With the current configuration it is not possible to create a URL like https://www.example.de/blog/category/typo3-ist-toll from a title like "TYPO3 ist toll", but only https://www.example.de/blog/category/TYPO3 ist toll. This is because there is no speaking url path segment for categories, tags and authors.

Enclosed is already a working example of categories.

René Gast added a comment - 19.11.18 14:54

blog.zip

Frank Nägler added a comment - 20.11.18 08:51

Hi Rene,
Thank you for the patch, can you provide a pull request with this changes?
It would also be nice to have this not only for categories, but also for tags and authors.
I checked the ZIP file, this contains only the changes for the categories, right?

René Gast added a comment - 20.11.18 10:38

Hi Frank,

you're right!

And I would like to do that, but it does not quite work. Currently I can use the path segment for the tags, but not the path generation with the type "slug" (here I get the error "Language -1 does not exist on site website.").

René Gast added a comment - 20.11.18 18:24

Hi Frank,

I've also created path segments for the tags and authors. The commented out details (languageField, transOrigPointerField, transOrigDiffSourceField as well as eval) caused me problems. The path generation for the authors is not working properly, at least the automatically generated path is strange (default-c6935384e0). In the appendix I attached the current changes, at the same time created a pull request.

blog_2.zip

Hi Frank,

I've also created path segments for the tags and authors. The commented out details (languageField, transOrigPointerField, transOrigDiffSourceField as well as eval) caused me problems. The path generation for the authors is not working properly, at least the automatically generated path is strange (default-c6935384e0). In the appendix I attached the current changes, at the same time created a pull request.

Frank Nägler added a comment - 22.11.18 11:52

Hi Rene,
thanks, but I can't see any pull request, where do you created the pull request?

René Gast added a comment - 22.11.18 18:36

Hi Frank, maybe I can't create a pull request, because I can't fork the repository. I gave the patch anyway to my developer, because there are still some bugs. Alternatively, he can do the pull request.

René Gast added a comment - 26.11.18 17:38

My developer also worried about where the fork can be created. Therefore, I hereby send the new version. Please push it into the git by yourself. The path segments work for tags, categories and authors.

blog_final.zip

Reporter: René Gast

Created: 19.11.18 14:54
Updated: 26.11.18 17:38

Service-Desk: TE-102

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

#27

This issue might be fixed for 9.x but still occurs in v8.7 branch.
Details are in link.

Versions

8.7.3
8.7.4-dev

Hi,
I wanted to ask if this is already possible or not.
I do want to use the content element "Blog List by Category" as content element on a Blog Page.
Of course, this is working but I do want to have a different template for it because it should be rendered differently.
With other content elements, I can define in TCFORM layouts which can be selected under appearance -> content layout.
In the fluid template I can read this value and can decide which rendering should be done.
Is this possible as well with the blog extension?
If yes, how can I get the value in the fluid template?

Currently, I solved this with setting a new path for the fluid templates via Typoscript for the Blog Page, but this is not very user friendly.

I hope there is some solution for this and I am looking forward to hearing from you.
Best regards,
Jürgen

There is a PHP exception when calling PostRepository::findRelatedPosts():

TypeError
Argument 1 passed to T3G\AgencyPack\Blog\Domain\Repository\PostRepository::findRelatedPosts() must be of the type integer, string given, called in /home/***/web/typo3conf/ext/blog/Classes/Controller/PostController.php on line 355

Stack trace:

in /home/***/web/typo3conf/ext/blog/Classes/Domain/Repository/PostRepository.php line 300

at T3G\AgencyPack\Blog\Domain\Repository\PostRepository->findRelatedPosts('1', '1', '5')
in /home/***/web/typo3conf/ext/blog/Classes/Controller/PostController.php line 355

Bug Report

Prerequisites

• [? ] Can you reproduce the problem on TYPO3 v8.7 LTS
• [x ] Can you reproduce the problem on TYPO3 v9.5 LTS
• [x ] Did you perform a cursory search to see if your bug or feature is already reported?

Description

When calling the site withe the blog_archive is on (blog/archive/), unfinite redirects are performed.
/blog/archive/2018/ is working well

[Description of the bug]

Steps to Reproduce

1. Insert the archive plugin
2. call the site (previews or via url)
3. wait until browser stops with error

Expected behavior: [What you expected to happen]

Should list all years (like in the sitebar widget)

Actual behavior: [What actually happened]

Versions

9.1.0

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

Since 8.6 FlashMessages do not contain css classes anymore when custom markup is provided.
See:

• https://review.typo3.org/c/Packages/TYPO3.CMS/+/50285
• https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/fluid/Classes/ViewHelpers/FlashMessagesViewHelper.php#L124-L128

Steps to Reproduce

1. Add a comment
2. Inspect code and look for alert alert-success class

Expected behavior: [What you expected to happen]

Markup provided <div class="alert alert-[severity]">...</div>

Actual behavior: [What actually happened]

Markup provided <div class="alert alert-">...</div>

Versions

• master
• 9.1
• 9.0
• 8.7

The web blog module has a select box for blog instances and should check the backend user permissions (ACL) for pages. If a backend user can not read or edit a pagetree (db mount), the blog instance should not be visible in the select box.

Relevant for multiple blog instances and non admin backend user.

Reporter: Jörg Bösche

Created: 13.04.18 12:53
Updated: 13.04.18 12:53

Development: EXTBLOG-120

The category widget should show the number of blog posts and the parent categories the sum of the subcategories.

Category (n = Sub A and Sub B)
– Subcategory A ( n )
– Subcategory B ( n )

Hint: If a blogpost has multiple categories, the blogcount of the main-/parentcategory has to check the unique id of a blogpost. Otherwise, the number of blog posts is wrong calculated.

Reporter: Jörg Bösche

Created: 13.04.18 12:48
Updated: 13.04.18 12:48

Development: EXTBLOG-119

In the documentation you ask for feedback about the included routes setup, so here we go:

Using the mentioned import in a sites config.yaml works great, as long as you do not save the site configuration with the sites module. As soon as you save the site configuration with the sites module, the include gets overwritten by the content of the included yaml file so you end up having all includes merged into the sites config.yaml and there is no import any more.

Think about a TYPO3 website having hundreds of subdomains / site configs, which all should use the same route setup for the blog extension. Currently, this is only possible, when you do not use the sites module to save something to the sites config.yaml.

There is already a forge issue about this topic, but I think, that not many multi site websites already migrated to TYPO3 9.5, so the missing/non working feature of sharing route enhancers across multiple sites may not get the needed attention right now. Therefore I'm creating this issue here.

Hi,

I'm not sure if that is a bug but some language labels for the German language are not translated, for example:

The discussion on slack: https://typo3.slack.com/conversation/C1XLMLRM1/p1549458020157500

TYPO3 Version: 8.7.24
Blog: 8.7.3

Best regards :)

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

Previewing a blog page in draft workspace with plugin blog_authors throws an exeption.
Doctrine\DBAL\Exception\InvalidFieldNameException
Unknown column 'uid_local' in 'field list' ...

Steps to Reproduce

1. Create a blogpage with an author
2. Insert plugin blog_authors
3. Preview the page in any draft workspace

Expected behavior: Show the blogpage

Actual behavior: Exception is thrown

Versions

TYPO3 9.5.5
t3g/blog 9.1.1
PHP 7.2
MySQL 5.7

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

When creating a new blog post the publish date is set to 1/1/1970 instead of the current date- This is due to the fact TYPO3 is not differencitating between NULL and 0 on datetime fields.

Steps to Reproduce

1. Create a new page/blog post
2. Check publish_date, crdate_month and crdate_year

Expected behavior: [What you expected to happen]

Date is set to today

Actual behavior: [What actually happened]

Date is set to 1/1/1970

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

Sometimes when editing a tag an exceptions happens. Condition for the exception is that the page with the same uid as the tag uid does not exist.

Exception message: #1534710048 TYPO3\CMS\Core\Exception\SiteNotFoundException. No pseudo-site found in root line of page 255

Stack trace:
in /home/app/web/typo3/sysext/core/Classes/Site/PseudoSiteFinder.php line 179
at TYPO3\CMS\Core\Site\PseudoSiteFinder->getSiteByPageId(255, array())
in /home/app/web/typo3/sysext/core/Classes/Routing/SiteMatcher.php line 210
at TYPO3\CMS\Core\Routing\SiteMatcher->matchByPageId(255)
in /home/app/web/typo3/sysext/core/Classes/Compatibility/PseudoSiteTcaDisplayCondition.php line 79
at TYPO3\CMS\Core\Compatibility\PseudoSiteTcaDisplayCondition->isInPseudoSite(...)

The reason for this is that PseudoSiteTcaDisplayCondition is for pages table only. It cannot be used for any other types of record. It is quite clear from the comment at the top of the class:

A display condition that returns true if the page we are dealing with is in a page tree that is represented by a PseudoSite object.

This is used to suppress the 'slug' field in pseudo site page trees when editing page records and to show the alias field.

Steps to Reproduce

1. Make sure that a tag has uid and there is no page with such uid in the installation
2. Try to edit the tag

Expected behavior: Tag can be edited

Actual behavior: Exception as described above

Versions

TYPO3 9.5.5
blog: 9.1.1

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

The avatar image provider does not respect the configured size via plugin.tx_blog.settings.authors.avatar.provider.size.

Steps to Reproduce

1. Add Author
2. Select ImageProvider
3. Add Image
4. Open SingleView with Author Plugin

Expected behavior: [What you expected to happen]

Cropped and Resized image is returned.

Actual behavior: [What actually happened]

Original image is returned.

Versions

• master
• 9.1
• 9.0
• 8.7

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

Blog RSS feed channel link is not set correctly. The link generation drops the PageType parameter.

Versions

Master, 9.1, 9.0

https://www.pexels.com/api/

would be sick!

Reporter: Jörg Ems

Created: 25.07.17 17:06
Updated: 23.07.18 07:55

Development: EXTBLOG-91

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1341397869: Segment lists of path lists.posts.maximumDisplayedItems does not exist in array | TYPO3\CMS\Core\Utility\Exception\MissingArrayPathException thrown in file /var/www/html/public/typo3/sysext/core/Classes/Utility/ArrayUtility.php in line 200. Requested URL: http://mydomain.com/blog

Steps to Reproduce

1. Install blog extension
2. Do not include typoscript template
3. Add "Blog: List of posts" plugin to the page
4. Open the page

Expected behavior: [What you expected to happen]

Defaults kick in. No Exception.

Actual behavior: [What actually happened]

Exception is thrown.

Versions

All versions.

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

Slug field is missing for:

• Authors
• Tags
• Categories

Expected behavior: [What you expected to happen]

• I would like to use the frontend route enhancers of TYPO3 to configure my urls
• I am able to optimize the slugs used for the url resolving
• I can upgrade my current realurl configuration and convert the current titles via an upgrade wizard
• I expect that the default configuration respects the slug fields

Actual behavior: [What actually happened]

There are no slugs.

Versions

master, 9.1, 9.0

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

The method that is responsible to find the current post is always checking if the blog entry is in the storage pids. This query is obsolete since the only relevant constraints we need to check if that the page is of type blog. All methods making use of finding the current post rely already on that these are executed within the context of a page.

Steps to Reproduce

1. Create a blog page outside the configured storage pids
2. Add a metadata plugin to this page
3. Check if the current page is resolved

Expected behavior: [What you expected to happen]

Current page is returned.

Actual behavior: [What actually happened]

The page is not resolved and null is returned.

The blog extension enforces setting PAGE_TSCONFIG_ID for categories to be found in page properties. This must be added to the documentation.

Reporter: Mathias Brodala

Created: 11.04.18 12:54
Updated: 12.04.18 08:49

Service Desk: TE-83
Development: EXTBLOG-117

The extension repair_translation fixes an issue in core v8 which could be helpful for EXT:blog as well.
Read up the discussion in slack:
https://typo3.slack.com/archives/C1XLMLRM1/p1550571695097400

If it makes sense we could suggest or require the extension for v8 branch.

[Moved from TGT-1667]

A user reported an issue in slack:

Raphael Weber [01:33 Uhr]
Lately I have a bug (I guess?) with TYPO3 9.5.4 and blog 9.1.0 (same with T3 9.5.3 and blog 9.0.1 too):
On the detail page of a blog I used to place the “authors” frontend plugin which does show the author as it should in the main language. Unfortunately it does not show the author in the translated language anymore. It worked fine in TYPO3 7.x. But now there is a <div> tag with the corresponding id and a child element <a>-tag with the origin language content uid but it is empty. I am guessing it has something to do with the authors not being translateabel objects? Did anyone experience this behaviour before? Anything I could to to narrow it down further?
(done all upgrade-wizzard-thingies, cleared all caches, deactivated custom templating overrides, deleted and recreated the plugin-content-object on the detail pages)

I can reproduce the problem and debugged the SQL query.

The findCurrentPost method in the PostRepository return null in case of a translated page / post. Further investigations are required.

blocked by TGT-1505 we decided to wait until this issue is solved, before we try to find and fix the issue in extbase.

Reporter: Frank Nägler

Created: 5 days ago
Updated: Yesterday

Development: EXTBLOG-153

The tag widget does not respect the TypoScript storage pid settings in the doctrine query. Currently all available tags are displayed.

If you have multiple blog instances in the T3 project, you want to focus on the tags of the current blog instance (storage pid).

Reporter: Jörg Bösche

Created: 13.04.18 12:16
Updated: 13.04.18 12:16

Development: EXTBLOG-118

Add badges for travis, test coverage, downloads, ... e.g. https://github.com/FriendsOfTYPO3/tt_address

Hi,

Using Typo3 8.7.24
Blog 8.7.4 and
RealURL 2.5.0

I found some configuration examples for RealURL and the Blog extension, but none of them worked.
Does somebody have a working config to get good looking URLS for the combination listetd above?

Would be great.

Best regards,
Jürgen

we accidental backported : void in CommentController.
We need to remove the return types and release a new version.

Reporter: Frank Nägler

Created: Yesterday
Updated: Yesterday

Development: EXTBLOG-156

Sven Schweizer [14:51 Uhr]
Hi there, I just wanted to report a mistake in the docs that costed me quite some time... :leichtes_lächeln:
it must be lists.posts instead of list.post for setting e. g. maximumDisplayedItems

Reporter: Frank Nägler

Created: 2 days ago
Updated: 2 days ago

Development: EXTBLOG-155

Feature Request

It would be great if new blog posts could be posted automatically on social media channels like Twitter or Facebook.
Therefor it should be possible to make the publication dependent on one or more selected catagories, tags or authors. For example if a certain author has published a new blog post in TYPO3 then only this blog post should be published on a certain social media channel. (For example Max Mustermann is a sport reporter and Maxim Mustermann is responsible for plants. If Max writes a new blog post this should automatically be published on the sport Twitter account and if Maxim publishes a new blog post, this should be published on another Twitter account.)

So, it must be possible to create different social media configurations and it has to be possible to create something like an "e-mail" filter. If a certain filter (author, tag, categorie) is set, publish the blog post on a certain social media channel. Furthermore I think it would be good to have an extra field for the text which should be shown on the social media post.

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

It is currently not possible to create a crop for the image of an author (when not choosing for gravatar). This is due to a wrong configuration introduced in version 9 of the extension.

Steps to Reproduce

1. Install v9.0.0+ of the extension
2. Create an author
3. Set avatar provider to image
4. Select an image
5. Try to set a crop

Expected behavior: [What you expected to happen]
That you have the possibility to set a crop

Actual behavior: [What actually happened]
The fields are missing to set a crop, link etc. The palette imageoverlayPalette is missing.

Versions

9.0.0+

In 8.7.0, if there are no comments/categories/tags, the headline of the sidebar widget is shown regardless.

What about including an if-statement to check if the widget contains any data?

Old:

<f:section name="content">
<h3 class="widget-title">Categories</h3>
<ul class="categories list-inline">
<f:for each="{categories}" as="category">
<li class="list-item category-item category-item-{category.uid}"><blog:link.category category="{category}" /> <blog:link.category rss="true" category="{category}"><i class="fa fa-rss-square"></i></blog:link.category></li>
</f:for>
</ul>
</f:section>

New:

<f:section name="content">
<f:if condition="{categories}">
...old code here...
</f:if>
</f:section>

Frank Nägler added a comment - 22.09.17 09:51

you could also disable the widget in case you don't have categories or tags..
remove the complete output makes debugging harder. so from my side, if you don't use tags or categories, simple disable the widget.

Sven Teuber added a comment - 26.09.17 11:47

That may be true for categories and tags, but not regarding the comments: There is a certain period of time between the blog going "live" and the first comment appearing. That period may be pretty long, since new blogs will not have heavy traffic and many users commenting.

"Remove the comment widget until the first comment comes in, than inform the programmer to insert the widget again" seems much more complicated than including an if-statement in the template.

Reporter: Sven Teuber

Created: 21.09.17 12:32
Updated: 26.09.17 11:47

Service-Desk: TE-58

From a SEO point of view, additional rel attributes in link tags in the header make sense, in order to deliver the connection of paginated pages in the blog for Google.

Example (taken from news by Georg Ringer):
Inside :
First page:

Second page:

Third page:

Last page:

Reporter: René Gast

Created: 28.03.18 10:11
Updated: 23.07.18 07:55

Service Desk: TE-71
Development: EXTBLOG-111

In \T3G\AgencyPack\Blog\Controller\PostController::relatedPostsAction(), \T3G\AgencyPack\Blog\Domain\Repository\PostRepository::findRelatedPosts() hits me up with a TypeError, because its (actually int) arguments are passed as strings from typoscript ( $this->settings['relatedPosts']['categoryMultiplier']).

Frank Nägler added a comment - 28.01.19 08:39

As already mentioned in slack, I would prefer a (int) cast in front of each argument instead of the solution in your branch (https://bitbucket.org/awooooo/blog/commits/b57bc095ee0e11d98ddb8e5754b2f0f8179fc36f?at=bugfix/TE-111). Anyway many thanks for your contribution.

Cookie added a comment - 29.01.19 19:38

Copied from Slack, just for completeness:

Maybe you missed that on a quick glance, but there is indeed an (int) cast before the settings access. However, if the value happened to not be set, then "" would be cast to 0, which is a bad default. Therefore, I looked up and applied the defaults from the TS constants.

This all is not because of my personal preference, but to fit in with the code style of the project - access to $this->settings is rare in this project, but it is solved exactly as I re-created in my branch in the pre-existing https://bitbucket.typo3.com/projects/EXT/repos/blog/browse/Classes/Controller/WidgetController.php#121-123,159,177-178 .

If the (int)$this->settings['relatedPosts']['limit'] ?: 5 bothers your, then it might make sense to change it in WidgetController as well, in order to keep a consistent code style.

Reporter: Cookie

Created: 27.01.19 16:40
Updated: 29.01.19 19:38

Service-Desk: TE-111

RSS

After searching the extension manual, various articles and this repos Issues, I was unable to find a way to have all posts of a blog in ONE RSS feed. I would assume there is a link for that already, because there is one for every category, author and specific time frames (e.g. a certain month) which I was able to find in the template itself.

If thats the case, that's missing from the extension manual as well.

Thanks in advance, and for that pretty cool extension,

Phillip

Bug Report

Description

The update wizard for AvatarProviderUpdate can be clicked in the update wizard section of the install tool, after updating an 8.7 instance to 9.5. The wizard crashes with a RuntimeException telling, that the given identifier is invalid. This may have its cause in how the wizard is registered in the ext_localconf.. because the array key does not match the classes namespace (T3G\AgencyPack\Blog\Install\Updates\AvatarProviderUpdate instead of T3G\AgencyPack\Blog\Updates\AvatarProviderUpdate).
https://github.com/TYPO3GmbH/blog/blob/master/ext_localconf.php#L170

Steps to Reproduce

Update an instance from 8.7 to 9.5 and try executing the update wizards afterwards.

Expected behavior:
The update wizard should be executable

Actual behavior:
The wizard crashes with a Runtime Exception

Versions

TYPO3 9.5.4
PHP7.2
Blog 9.1.1

Index: Configuration/TCA/Overrides/pages.php
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
--- Configuration/TCA/Overrides/pages.php	(date 1549379289000)
+++ Configuration/TCA/Overrides/pages.php	(date 1549379342275)
@@ -158,6 +158,7 @@
                     'multiple' => 1,
                     'foreign_table' => 'tx_blog_domain_model_author',
                     'MM' => 'tx_blog_post_author_mm',
+					'foreign_table_where' => ' AND tx_blog_domain_model_author.pid = ###PAGE_TSCONFIG_ID### ORDER BY tx_blog_domain_model_author.name',
                     'minitems' => 0,
                     'maxitems' => 99999,
                 ],

Reporter: Andreas Sommer

Created: 9 hours ago
Updated: 9 hours ago

Service Desk: TE-117
Development: EXTBLOG-157

Bug Report

Prerequisites

• Can you reproduce the problem on TYPO3 v8.7 LTS
• Can you reproduce the problem on TYPO3 v9.5 LTS
• Did you perform a cursory search to see if your bug or feature is already reported?

Description

If the storage pid is set to a non existing storage, the comment widget builds a storage pid constraint that tries to find a value in an empty resultset.

The IN operator needs a non-empty value list to compare against. The given value list is empty.

Steps to Reproduce

1. Set storage pid to a non existing/deleted page
2. Add sidebar widget to blog a page

Expected behavior: [What you expected to happen]

No comments returned

Actual behavior: [What actually happened]

Exception is thrown.

Currently it is not possible for an editor to place a content element only showing the x latest blog posts. For example, on the homepage they want to show the latest 3 blog posts. On another page it the full list of blog posts. It is possible to do this with TypoScript and a developer can create his own element taking care of this, but IMO this is a quite basic feature.

My idea would be to add another plugin showing the latest blog posts just like the normal list of posts, but with an option to set the maximum number of posts to be shown.

As we have created those element before in our projects, we are more than willing to add this to the original extension by submitting a PR.