Module: Blog

[kongondo]

In that case there is something else wrong with your setup. It is difficult to tell without seeing/testing on the actual site Any other changes you have made to your template files? Some other modules possibly interfering? What about testing comments + form apart outside of the Blog (non-blog pages)?

[creativejay]

My template files are very different from the default. I haven't touched the module itself, though. I'd be happy to give you access to my admin if you have the time to take a look. I can post any templates here that you think may be causing the issues.

Form Builder works outside of the blog pages. I don't have comments for non-blog pages, though.

[kongondo]

I'd say to first test with a 'normal' PW comments setup outside Blog pages.

https://processwire.com/api/fieldtypes/comments/

[creativejay]

Yeah, comments on a non-blog page aren't working, either. Same result. I'll move my questioning to that fieldtype discussion. Thanks kongondo!

[justb3a]

I got another little issue. If someone uses the quickpost function and fills out quickpost_body all line breaks will be removed.

I don't think that is it necessary to use a rich text area here but maybe you can wrap it in a simple nl2br function?

        //@todo - SHOULD THIS BE A RICH TEXT AREA?
-       $p->blog_body = $this->sanitizer->textarea($this->input->post->quickpost_body);
+       $p->blog_body = nl2br($this->sanitizer->textarea($this->input->post->quickpost_body

[kongondo]

Yeah, this has been brought up before but wasn't really sure how to deal with it. Thanks for reminding me .

For now, I have decided to convert and store the line breaks in 'quickpost' to paragraphs (instead of <br>) since I believe that is the intended action by the user when they use a line break in 'quickpost' to space out their text. Besides, that is what CKEditor is going to do when the full post is edited. Using nl2br will result in lots of <br> all of which CKEditor will wrap in one paragraph. But thanks to your idea, I am now using a pre_replace to do the job. It works fine.

Committed to dev for now.

[justb3a]

Thanks a lot for this quick fix  

I checked out the dev branch, reset my deployment script and everything works fine (and all post authors are happy now  ).

[creativejay]

For the Categories / Tags and other Page-type fields, the parent of those pages gives blog-author the right to Add Children, and the field has "Allow new pages to be created from field" checked. Anything else I need to check for? I'm able to create new pages as a superuser but my blog-author role users get a little achtung triangle in the AsmSelect field when they type, and nothing is saved. In Select cases, there's no option to add another for blog-author roles. What I glean from this is that there's another permissions setting somewhere, other than the per-template "Add Children" setting for blog-author.

I already started this over once in a new install and ran into the same comments issue before I got very far (managed to reverse the problem by restoring the default templates, so the problem is either with my call to the comments form, or some other module that I call in my template files).

Edited February 10, 2015 by creativejay

[kongondo]

Have you given the role 'blog-author' the right site-level permissions? In ProcessWire access is controlled at both site- and template- levels. 

Admin > Access > Roles > blog-author. The permission page-edit is needed...

[creativejay]

Yes, the blog-author role has page-edit permissions.

There are sub-permissions from page-edit that I do not have checked off:

page-delete

page-edit-recent

page-lister

page-lock

page-move

page-sort

page-template

[kongondo]

Then the problem is in your blog-tag and blog-category templates. You have two choices:

1. Set up access to the pages using these templates, i.e. an individual 'tag' and 'category' respectively by setting up access in their respective parents' templates, i.e. 'blog-tags' and 'blog-categories' AND making sure the two child templates 'blog-tag' and 'blog-category' have No checked for their respective 'manage view and edit access for pages using this template?' setting. In that case, pages using 'blog-tag' and 'blog-category' will inherit their parents' access. Then, in 'blog-tags' and 'blog-categories' you will need to check for the role 'blog-author' View Pages, Edit Pages, Create Pages and Add Children. Alternatively:
2. Set up access on the child templates themselves, i.e. in 'blog-tag' and 'blog-category' templates. In this case, in their parents' templates, 'blog-tags' and 'blog-categories' you would only need to add the access Add Children. In 'blog-tag' and 'blog-category' you would need to grant access to View Pages, Edit Pages and Create Pages. 

If the above don't work, there could be some access inheritance issues going on...Access issues are of course controlled by ProcessWire itself and not Blog

[creativejay]

Thanks Kongondo, that confirms what I'd been doing was correct.

I got clarification from the blog-author role user that spotted the problem with creating new pages from fields: she had never been able to do this.  On a hunch I disabled PagesCreatedEdit and sure enough that allowed the user to create their new tags, categories, etc. Unfortunately now blog-author can edit blog posts other than their own created posts. I may make a custom Module based on PagesCreatedEdit to try and make a special exception to the rule for certain templates.

[kongondo]

There's a number of posts here in the forums about restricting users to only be able to edit the pages they created...

Here's some modules that you could look at/customise to help you get started

http://modules.processwire.com/modules/custom-page-roles/

http://modules.processwire.com/modules/page-edit-per-user/

[kongondo]

Update: Blog Version 2.3.4

Blog now preserves all line breaks as paragraphs for posts created via ProcessBlog's quickpost, thanks to idea by @justb3a

[creativejay]

Hey Kongondo,

I noticed that when I first installed Blog, probably about 4 months ago, the module was called in my templates as

    $blogOut = $modules->get("MarkupBlog");

And now $blogOut seems to be $blog in your more recent documentation. Is there something in the modules themselves that should compel me to go back to the default templates as a new starting point? (Yes, I'm still struggling with comments and I have narrowed it down to being caused by my template file code...)

[kongondo]

Nope..you can call it anything you want (as long as it is a valid PHP variable name) - $b, $myBlog, $thoughts, $blahBlah....

RE comments, maybe paste your template code in pastebin and I'll have a look if I can find some time....

[creativejay]

Thanks Kongondo, I'd appreciate it when you have a chance.

http://pastebin.com/0zWfGXxN

[ridgedale]

Hi,

I am just getting started with PW. I've successfully installed but not yet confirgured the ProcessBlog module and would like to know before I delve further whether or not a single instance of the module can be used to deliver multiple blogs. What I have in mind for the website I am currently working on is both a separate News section and a separate Testimonials section.

Is it actually necessary to completely split the two sections/blogs in terms of the backend? If not, how should I go about setting this up? Can categories be set up to split the data for News and Testimonials? Effectively both pages could be built around the same underlying data structure, for example:

$post-date-time             ( - would like the date|time to appear as yyyymmdd - hh:mm:ss, though)
                                         - do I actually need this field or can this data be retrieved from a built-in PW source??

$post-title

$post-summary

$post-author

$post-category              ( - needed or not?)

In addition, what are the advantages / disadvantages of the different blog styles? Purely from the path name perspective it appears that Blog style 3: /mysite/posts/example-post/ might be the most appropriate.

Otherwise, would Joss's Simple News System be a better place to start?

Any guidance would be greatly appreciated.

Edited February 22, 2015 by kongondo
Moved to Blog's support forum

[kongondo]

@ridgedale,

Welcome to PW and the forums.

Multiple Blogs:

This issue has been raised a couple of times but I haven't yet resolved how to best implement such a feature:

 

https://processwire.com/talk/topic/7403-module-blog/?p=63775

https://processwire.com/talk/topic/7403-module-blog/?p=63878

https://processwire.com/talk/topic/7403-module-blog/?p=66524

https://processwire.com/talk/topic/7403-module-blog/?p=66528

 

Is it actually necessary to completely split the two sections/blogs in terms of the backend? If not, how should I go about setting this up? Can categories be set up to split the data for News and Testimonials?

At the moment it is not possible to have such a split. I am wondering whether this can be achieved by simply adding some field on a post's template to assign it to a particular field...hmm...

 

$post-date-time

Change your date's input/output format in the field 'blog_date'

 

$post-summary

You can have a post summary by using renderPosts($posts, true) - see the Blog documentation. Alternatively, you can create your own summary field and use that.

 

Blog Styles

In addition, what are the advantages / disadvantages of the different blog styles?

Purely user preferences...

[ridgedale]

@kondongo

I am sorry for the delay in replying, I thought I'd raised a new topic (Evidently not! ) and therefore wasn't looking in the right place for any replies.
Thank you for your very speedy reply and the links.

I had an issue with links between the pages which I appear now to have resolved using:

<a href="<?php echo $config->urls->root; ?>about"</a>

All of those below returned blank pages:

<a href="<?php echo $config->urls->templates; ?>about"</a>
<a href="/about"</a>
<a href="./about"</a>

I'll read through the links you have provided and see how I get on.

In the meantime I've tried working through the Simple News System guide so far without success.
I'm not sure if this is an issue related to the installation path of this instance of PW (in this instance while the site is under development: http://localhost:8888/rcl_pw252/ ) or the fact that I changed the name of the templates, fields and pages.
I'm pretty certain I've updated the news.php, news-index.php and inc/news-fnc.inc files have been updated correctly accordingly, but I still get blank pages being returned which might suggest that the inc/news-fnc.inc file needs to include paths in at least some instances as well.
Any thoughts would be appreciated.

Thanks again.
 

[creativejay]

Hey kongondo, I finally fixed my comments! As usual, it was something completely innocuous: I had a base href tag in my header that was redirecting the #comments to the root URL of the site installation. Deleted that line, and suddenly my comments worked.

I was taking a very methodical approach to figuring this out (finally sitting down tonight after weeks of not having time to focus), thankfully my method led to the answer in five steps.

Now that I can finally put in some example comments to play with:

1) If I wanted to notify the admin listed in the blog_comments/Details tab, PLUS the author of the post that received a comment, what would you suggest? I don't want to add every author to the list of those who receive comments as a global setting.

2) I have a custom admin tab that is the admin home of all authors. I'd like to identify any pending comments they should review and output a message such as "You have # comments pending review. Please visit the Comments Manager."  Would you suggest I start with the code from  "public function findComments($selector)" in MarkupBlog.module (line 541 in the latest release version)?

Edited March 4, 2015 by creativejay

[Qurus]

Hi,

Can anyone tell me whats wrong with my code here please. I am trying to blog page with images and small text. Small texts are ok but images showing only one. Any help, would be greatly appreciated.

<?php
//CALL THE MODULE - MarkupBlog
$blog = $modules->get("MarkupBlog");
$limit = 10;
$post = $pages->get('template=blog-post, sort=blog_date');
$image = $post->blog_images->first();
?>

<div class="jumbotron">
    <h3><?php echo $page->title ?></h3>
</div>
<!-- /.Header_End -->
<div class="main-content container">
    <div class="row">

        <!-- Blog -->
        <div class="blog-list">
            <div class="row">
                <div class="col-md-6 post-list">

                    <div class="ih-item square effect9 right_to_left"><a href="#">

                            <div class="img img-responsive"><img src="<?php echo $image->url; ?>" alt="img"></div>
                            <div class="info">
                                <div class="info-back">
                                    <h3></h3>
                                    <p></p>
                                </div>

                            </div></a>

                    </div>

                </div>
                <div class="col-md-6 post-list">
                    <?php
                    echo $blog->renderPosts("limit={$limit}", true);
                    ?>
                </div>

            </div><!-- row_end-->
        </div>
    </div>
</div> 

[kongondo]

@Qurus
 

Hi,
Can anyone tell me whats wrong with my code here please. I am trying to blog page with images and small text. Small texts are ok but images showing only one. Any help, would be greatly appreciated.

<?php
$image = $post->blog_images->first();
?>

 
On that line you are only calling one image....specifically the first one. If you want to output several images you would have to loop through them. Have a read here. something like

$out = '';
foreach($post->blog_images as $img) {

$out .= '<img src="' . $img->url . '" alt="img">';

}
//then output $out later on down...within your <div class="img".......

@creativejay...get back to you later.....

[kongondo]

1) If I wanted to notify the admin listed in the blog_comments/Details tab, PLUS the author of the post that received a comment, what would you suggest? I don't want to add every author to the list of those who receive comments as a global setting.

2) I have a custom admin tab that is the admin home of all authors. I'd like to identify any pending comments they should review and output a message such as "You have # comments pending review. Please visit the Comments Manager."  Would you suggest I start with the code from  "public function findComments($selector)" in MarkupBlog.module (line 541 in the latest release version)?

Sorry for the delay.

#1: Am not sure how to do that. It is really a Comments Module question. Maybe Ryan could help there

#2: Yes  

Seem you really have some cool setup there. Would like to see a screen if possible.

Cheers,

/k

[creativejay]

Thanks! I'm trying to make the site as fun as possible (it's a non-income-generating pet project), to make it emotionally rewarding for the authors that have volunteered to provide content.

I'm attaching a screen shot of the post-login home page for an author (non-superuser). Fair warning, the color scheme may hurt the eyes. I'm going for quirky here.

The challenge area is the 'ticket' system I was referring to.