Module: Blog

[Karinne Cyphers]

Thank you @kongondo This works great!

[Troost]

Thanks Kongondo for this great offer! 

I'm currently experimenting with it, I came to the point where I want to change a little bit in the positioning of the blog.
Like placing the Date underneath the post instead of above. But I can't find where I can change those settings? 

Also, the option to show like 200 words and than the text 'view more'. I want to translate this to dutch, but I can neither find this one hehehe.
Can u help me out?

(Dont know what about this, but when i go to PW admin > blog > settings > I can change whatever I want, but it won't safe. It keeps saying the same text which comes by the installation)
I've tested this in Chrome and Safari, same problem. I' on ProcessWire 3.0.132 © 2019

[kongondo]

On 6/4/2019 at 12:37 PM, Troost said:

Thanks Kongondo for this great offer! 

Glad you like it! :-).

On 6/4/2019 at 12:37 PM, Troost said:

Like placing the Date underneath the post instead of above. But I can't find where I can change those settings? 

You do that by passing $options to renderPosts(). I can only apologise that I've never completed the documentation for this module. Please have a look at the options here, in the method processPostsOptions(). All the options that can be passed to renderPosts() are there. For instance, 'post_date' => 1,// display post's date: 0=off,1=top(below post-headline),2=bottom(in post-foot)

On 6/4/2019 at 12:37 PM, Troost said:

Also, the option to show like 200 words and than the text 'view more'. I want to translate this to dutch, but I can neither find this one hehehe.
Can u help me out?

The string is on this line. Is it not appearing in the translation screen? I've never done translation myself so, I wouldn't know how to help beyond this. If you are still experiencing issues, maybe one of your multilingual members could help out.

On 6/4/2019 at 12:37 PM, Troost said:

(Dont know what about this, but when i go to PW admin > blog > settings > I can change whatever I want, but it won't safe. It keeps saying the same text which comes by the installation)

You caught a bug! Thanks for reporting. I've fixed it in the latest version (2.4.4). I've updated the module in the modules' directory.

[kongondo]

Update: Blog 2.4.4

Changelog

1. Fixed bug that caused blog settings not to save in blog admin. Thanks @Troost for reporting.

Module has been updated in the modules directory.

[Troost]

@kongondo

Thanks for your response! You've really helped me out with the string on that line, when my project is finished, I will show it over here!
And I'm glad I found a bug so I could help a bit with this module!

[jilf]

Hi,

New to PW, do anyone use the Blog Module templated as .twig instead of .php?

[BenSlayers]

Hi @kongondo, I'm having an issue with Jumplinks and I haven't had any luck on that support forum so I thought I would try here since I think the issue might be related to the blog plugin. Can you check my posts here and let me know if you've experienced this behavior?

https://processwire.com/talk/topic/8697-jumplinks/?do=findComment&comment=192151

[kongondo]

On 10/17/2019 at 11:56 PM, Ben Sayers said:

Hi @kongondo, I'm having an issue with Jumplinks and I haven't had any luck on that support forum so I thought I would try here since I think the issue might be related to the blog plugin. Can you check my posts here and let me know if you've experienced this behavior?

https://processwire.com/talk/topic/8697-jumplinks/?do=findComment&comment=192151

Hi @Ben Sayers,

Sorry for the late response. I have never used Jumplinks before. I have read the posts you link to but cannot think of any reason why the blog module would be the cause of the issue. In addition, @wbmnfktr seems to have successfully tested blog and Jumplinks, so it must be something else in your install. However, in your post you say:

Quote

removed a bunch of old posts, I wanted to redirect them to the main blog page (domain.com/blog/)

What do you mean by removed? Secondly, what 'blog style' did you use on install?

[BenSlayers]

On 10/22/2019 at 2:18 AM, kongondo said:

What do you mean by removed? Secondly, what 'blog style' did you use on install?

No worries, thanks for getting back to me! To remove the posts, I went to the Blog --> Posts tab in PW, checked the boxes for the posts I wanted to remove, then went to Actions -> Delete. I'm using Blog Style 1. I'm able to redirect any page in the website using Jumplinks unless it has "blog/" in it. 

Edited October 26, 2019 by Ben Sayers
Additional question for kongondo

[kongondo]

On 10/24/2019 at 3:06 PM, Ben Sayers said:

using Blog Style 1

Please confirm this. According to your post here:

it seems your posts are structured as: (domain.com/blog/some-post/). This would make it a Blog Style 2 and not Blog Style 1 which would be structured as: /domain.com/blog/posts/some-post/

[BenSlayers]

On 10/27/2019 at 5:31 AM, kongondo said:

Please confirm this. According to your post... it seems your posts are structured as: (domain.com/blog/some-post/). This would make it a Blog Style 2 and not Blog Style 1 which would be structured as: /domain.com/blog/posts/some-post/

Sorry, my post on the forum should have said domain.com/blog/posts/some-post/ - I am using blog style #1. 

[brdje]

Hi @kongondo, I'm loving the work you've done with the blog module allready and am using it to set up a multi language blog. I do have a problem with rendering the blog in the secondary language.

The blog categories and tags are not rendered, I assume this is because they aren't translated yet? 

The blog posts themselves don't appear in the secondary language but still output the content from the primary language.

Do you have any idea what i could change to get the blog to work in my secondary language?

 

Dutch version:

French version:

[kongondo]

On 12/11/2019 at 7:56 PM, brdje said:

I'm loving the work you've done with the blog module allready

Hi @brdje. First, welcome to the forums! I am glad you are finding the blog module useful.

 

On 12/11/2019 at 7:56 PM, brdje said:

I assume this is because they aren't translated yet? 

You are right. A massive oversight on my part! I will work on this as soon as I get a bit of time, which might not be soon, I am afraid.

 

On 12/11/2019 at 7:56 PM, brdje said:

Do you have any idea what i could change to get the blog to work in my secondary language?

Since posts are just pages, you could just use PW API directly to access each blog field and let PW deal with the fetching of the value in the current language. For instance (rough example):

 

$posts = $pages->find("template=blog-post,limit=20");

$out = "";
foreach($posts as $post) {
    $out .= "<h2>{$post->title}</h2>";
    $out .=  $post->blog_body;
    $thumb = $post->blog_images->first()->width(250);
    $out .= "<img src='{$thumb->url}'>";
    $out .= '<hr>';
}

echo $out;

It's not ideal, but it should get you started, meanwhile.

[montero4]

Hello,

I'm using the blog template by @kongondo (thank you!) and I've been going through and creating my website. I've been trying to work this issue out for a day and I haven't gotten far.

I can't figure out how I can sort the months in descending order as these are not pw pages. The years and the posts are shown in descending order, and I want to have the months in descending order too (June, May, April, etc) . How do I do that? I looked at the function for renderarchives and it's unfortunately beyond me at the moment. Thanks for any help on this! 

Regards,

Jonah

Archives

2019

April
    Post #4
    Post #3
    Post #2
    Post #1
May
    Post #4
    Post #3
    Post #2
    Post #1
June
    Post #4
    Post #3
    Post #2
    Post #1

 

[teppo]

Hey @montero4!

Just to confirm: are you using the Blog module (https://modules.processwire.com/modules/process-blog/), or perhaps something else?

[montero4]

Hi @teppo

Yes, that's what I'm using. Thanks.

[BitPoet]

Have a look here:

 

[kongondo]

Hi @montero4,

Welcome to the forums and ProcessWire. This seemed like a nice feature to add so I have gone ahead and added it as an option to getArchives(). I'll release over the weekend.

 

PS: I have moved your thread to the blog support forum.

[kongondo]

Update: Blog 2.4.5

Changelog

1. Added new option (see example use below) to MarkupBlog::getArchives() that allows to specify if archive months should be sorted descending (Dec - Jan). Default is ascending (Jan - Dec), thanks to question by @montero4
2. Fixed bug in template blog-archives.php that caused illegal offset warnings.

Module has been updated in the modules directory.

 

Example usage of new getArchives() option

 

getArchives() now accepts a third parameter as an $options array. If you want archive months to be sorted and rendered in descending order (December - January), you will need to pass this as an option in the $options array and set the value 'descending' to they key 'archives_month_sort_order'. Since this is the third parameter for the method, you will need to pass options for the first and second parameters as well. If you want the default ascending order of months, you don't have to change anything in your code. Just call getArchives() as usual without any parameters.  Otherwise, read on for descending order of months.

 

<?php
$blog = $modules->get("MarkupBlog");
// options: if we want to sort archive months in descending order
$archiveOptions = array('archives_month_sort_order'=>'descending');
// get archives: order months descending
$archives = $blog->getArchives(0, 1, $archiveOptions);
// if you want to render the archives
$content = $blog->renderArchives($archives);// order months descending

Please test and let me know.

Thanks.

 

 

[ottogal]

Hi  @kongondo ,

it's quite a while I'm planning to use your Blog Module. Now I started my first try, installing version 2.4.5 in PW 3.0.148.
I chose Blog style 3 and installed the demo template files.

When in the Blog dashboard I open the Authors page, I get the Error
"Call to a member function size() on boolean"  in ProcessBlog.module:1686.
Line 1686 is this one:

'<img src ="' . $author->blog_images->first->size(75, 75)->url .'" class="blog_author_image">'  :

What's going wrong?
Thank you
ottogal

 

[kongondo]

Hi @ottogal,

Thanks for catching this. I have a feeling there are other similar gotchas! I'll search for and resolve (if need be) these at a later date. For now, please change line #1685 from:

$authorPhoto = !empty($author->blog_images) ?

to:

$authorPhoto = $author->blog_images->count ?

Thanks.

[lele_ballack]

Hi @kongondo

I've just installed your module (version 2.4.5 in PW 3.0.148). Upon installing I did select blog style 1 or 2, and in both cases I keep getting this warnings above the dashboard:

"Warning: Illegal offset type in ..\site\modules\MarkupBlog\ProcessBlog.module on line 916"
"Warning: Illegal offset type in ..\site\modules\MarkupBlog\ProcessBlog.module on line 917"

that refer to these two lines:

$posts->title => array('published' => $qn['blog-post'], 'unpublished' => $qn['unpublished'] ),
$comments->title => array('approved' =>  $numApproved, 'pending' => $numPending, 'spam' => $numSpam ),

How can I remove those warnings? Is there a quick way to fix it?

Thanks.

[kongondo]

21 hours ago, lele_ballack said:

How can I remove those warnings? Is there a quick way to fix it?

I am not seeing those errors in my test site. But I do see some code that could be refactored. Please try the following for now:

Replace this (starting from line # 915)

$list = array(
    $posts->title => array('published' => $qn['blog-post'], 'unpublished' => $qn['unpublished'] ),
    $comments->title => array('approved' =>  $numApproved, 'pending' => $numPending, 'spam' => $numSpam ),
    $categories->title . ' & ' . $tags->title => array('categories' => $qn['blog-category'], 'tags' => $qn['blog-tag'] ),
);

 

With this:

$postsTitle = !empty($posts->title) ? $posts->title : "Posts";
$commentsTitle = !empty($comments->title) ? $comments->title : "Comments";
$categoriesTitle = !empty($categories->title) ? $categories->title : "Categories";
$tagsTitle = !empty($tags->title) ? $tags->title : "Tags";

$list = array(
    $postsTitle => array('published' => $qn['blog-post'], 'unpublished' => $qn['unpublished'] ),
    $commentsTitle => array('approved' =>  $numApproved, 'pending' => $numPending, 'spam' => $numSpam ),
    "{$categoriesTitle} & {$tagsTitle}" => array('categories' => $qn['blog-category'], 'tags' => $qn['blog-tag'] ),
);

Please let me know if it helps.

Thanks.

[lele_ballack]

Thanks @kongondo for your quick reply! 

That worked really well and the warnings disappeared! 

Just noted that there is small bug though after implementing the new code: the comments counter appears now in the dashboard (title and icons only, without any real counting)  even though I chose a blog installation with no comments. 

[kongondo]

On 6/26/2020 at 9:22 AM, lele_ballack said:

Just noted that there is small bug though after implementing the new code: the comments counter appears now in the dashboard (title and icons only, without any real counting)  even though I chose a blog installation with no comments. 

Hmm. That's very strange. I'll have a look. Thanks for reporting.