Jump to content

Recommended Posts

Hi all,

When displaying the Archives by month I want to remove the comment count, author, and page count.

On the post pages I did this by passing an array of options:

$options = array('post_count' => 0, 'post_comments' => 0, 'post_author' => 0);

and then calling RenderPosts:

$blog->renderPosts("limit=$limit", true, $options);

This worked great, but if I try to pass the same set of options to RenderArchives, like so:

$blog->renderArchives($blog->getArchives(), $options);

nothing changes when the page renders. I get no errors, but those items I want removed are still there.

I looked at the code for RenderArchives in the MarkupBlog.module and it implies it does accept an array of options (see here). Is this the case?

Is there a way to stop these items from rendering on the page?

I could set them to display:none in the CSS, but that's not exactly an elegant solution :)

All the best,

Tony.

Share this post


Link to post
Share on other sites

Tony,

You are looking in the wrong place. renderArchives() is only responsible for all archives (e.g. /blog/archives/) and year archives (e.g. /blog/archives/2015/). For month archives (e.g. /blog/archives/1/) it is all about renderPosts(). Have a look at line # 33 in blog-archives.php. Just before that is where you need to pass your options. I am assuming you are using the blog-archives.php demo template file that ships with Blog. 

$options = array('post_count' => 0, 'post_comments' => 0, 'post_author' => 0);
$content .= $blog->renderPosts($posts, true, $options);
Edited by kongondo
  • Like 1

Share this post


Link to post
Share on other sites

Hello

I have installed the blog with the blank pages. Of course the wrong one....

I need the files with the blog-templates to get it working.

Now I am wondering if I can just copy the files with blog-templates from another server onto this one and just overwrite the blank-blog templates.

The blog is working on the older test-server ( http://jakubdegler.ch/user3/nojs/ ).

Can it be that simple ( hope so )

Thanks for any help

Jakob

____________________________________

IT WORKED! I WAS AFRAID SO I ASKED, BUT THEN I GATHERED SOME COURAGE...et voila

Thanks again for the great Module Kongondo!

  • Like 1

Share this post


Link to post
Share on other sites

Hello again

Nonetheless, there is one small thing. 

I am using Foundation 6 as framework and all was fine with two columns ( Main -left  and sidebar- right ).

Now I have put the blog into the main column and the sidebar isn't anymore on the right, but wandered off to the bottom.

I guess the solution is in the Blog.css...

What could that be?

Thanks a lot

Share this post


Link to post
Share on other sites

Definitely a CSS issue. (blog.css). Keep in mind thought that blog.css as well as the blog-xxxx.php template files that come with Blog are all demos just to get you started. In those demos I use pocketgrid.css which will apply a float:left to all divs with the class 'block'. If you wish to use the demo files, you will need to adjust your CSS to use whatever CSS framework you are using as well as check that all the code in the template files apply to your particular need..

  • Like 1

Share this post


Link to post
Share on other sites

Hi Kongondo

Thanks for all the help I got from You. I have the blog working, and everything is great.

I am not yet good with PHP...still lots to learn. 

The website I made is http://olikehrli.ch/. The titles of the individual posts are still links, like in Your Demo. I would like to undo that. I just need the titles with no linkage.

Could You please tell me how I can do that? I looked through all the Blog templates and still have no idea.

Thanks a lot

All the best

Jakob

Share this post


Link to post
Share on other sites

Hi Jakob,

That's not possible currently but you could do a pre_match on $blog->renderPosts($page) to remove the link...Sorry, short on time and can't give an example at the moment...

  • Like 1

Share this post


Link to post
Share on other sites

Here a small and simple trick to add an option like what asked Kuba2/Jakob. We are going to add a new option to renderPosts().

Steps are :

1) Open the file MarkupBlog.module located under site/modules/ProcessBlog/MarkupBlog.module

2) Add the option 'post_href_in_title'

Find the line :

//default options for various aspects of posts

and add the new following entry to the $defaultOptions array :

'post_href_in_title' => true, // if 'post_href_in_title' = true then post's title will contain a link. If false, only the post's title will be show

3) Find :

$out .= "<$h class='post-headline'><a href='{$page->url}'>{$page->title}</a></$h>";

replace to :

$out .= $options['post_href_in_title'] ? "<$h class='post-headline'><a href='{$page->url}'>{$page->title}</a></$h>" : "<$h class='post-headline'>{$page->title}</$h>";

We are done for the new option.

Then, to render the post without a link in post's title, use now the renderPosts() with the option 'post_href_in_title' set to false :

[...]

//Render limited number of posts on Blog Home Page
$content .= $blog->renderPosts("limit=$limit", false, array('post_href_in_title' => false));

[...]
  • Like 1

Share this post


Link to post
Share on other sites

Great stuff! Thanks

Could You maybe make a similar tutorial for removing the comments count number on the top right ( image )? It isn't needed in my case.

Thanks again!

comment-number.png

Share this post


Link to post
Share on other sites

An option already exist for that. Is "post_comments".

By default the option is set to 1 (it show the comments count on top). You can found further more options and their description/value in the file MarkupBlog.module, renderPosts() method.

Possible values for this option are, from the source code comment : 0=off, 1=comments count top, 2=comments count bottom, 3=comments count top & bottom

So given my previous exemple of renderPosts(), we add the option in the array :

[...]

//Render limited number of posts on Blog Home Page
$content .= $blog->renderPosts("limit=$limit", false, array('post_href_in_title' => false, 'posts_comments' => 0));

[...]
  • Like 2

Share this post


Link to post
Share on other sites

Thanks again. It works, when I change it in the markup-blog.

render Posts somehow didn't work...

Great stuff!

Love the forum

All the best

Jakob

  • Like 1

Share this post


Link to post
Share on other sites

Hi Kongondo,

Thanks for the great module.

I've been searching all day but been unable to find where I can change the labels of comments as I did for PW comments.

My labels within my Label array aren't working as I thought.

I also looked at for your documentation on your website but seems to be down for the moment.

http://kongondo.com/tutorials/specific-features/creating-a-blog-in-processwire/

What I used before which works for Generic PW commenting system were as followed:

'labels' => array(
        'cite' => '<label for="author">Name *</label>',
        'email' => '<label for="email">Email <small>(will not be published)</small> *</label>',
        'website' => '<label for="url">Website</label>',
        'stars'=> '<label>Rate this page:</label>',
        'submit' => 'Post Comment'
        


If you can provide any assistance it would be helpful, thanks.

Share this post


Link to post
Share on other sites

@jasonS,

This is currently not supported but I can add it. If you could please file a request here so that I don't forget, thanks.

Share this post


Link to post
Share on other sites

hi, 

When comments are disabled and I access Blog Dashboard, I receive the following error:
ProcessWire: ProcessBlog: SQLSTATE[42S02]: 
Base table or view not found: Table 'xxx.field_blog_comments' doesn't exist

I sent a little pull request which wraps the relevant part in a condition. 

I know, this module isn't flagged as ProcessWire 3.x ready, but I want to tell you anyway: JqueryFancybox isn't part of the Jquery core module anymore. I added this module manually and now the dashboard works as expected. Maybe you would suggest using JqueryMagnific instead in a 3.x ready release, which still is part of the core.

Share this post


Link to post
Share on other sites

@justb3a,

RE comments, thanks for that. Silly mistake on my part.

Now that I have gotten a little bit used to Magnific, I have been planning to replace use of Fancybox, even earlier than a 3.x release. Whichever way, it is going to happen, thanks.

Share this post


Link to post
Share on other sites

Is there more I need to know/do in order to get comment notification working, right now I have a PW site that can send emails AOK but no email is sent when comments are submitted. I have edited the field blog_comments in the admin and listed an email address under Details > Notification > Admin notification email.

If relevant, I submitted a test comment before I had added the email above. Since adding the email above I have retried several times and no emails sent yet.

I've Googled quite hard but no luck, sorry if the answer is simple and I missed it :/

PW 2.7.3

Blog Module 2.3.7

Thanks in advance for any ideas! Cheers, -Alan

Share this post


Link to post
Share on other sites

ugg... sorry to follow this up with ano Q :(

I've noticed that if I edit a users page e.g.

Admin > Access > Users> Elvis Presley

and use the Images field to add a bio photo, when visiting

http://example.test/blog/authors/elvis-presley/

all is good except the image that got stored was put in a folder called

/site/assets/files/-1041
i.e. the folder chosen when the image was uploaded is one that is prefixed with dash/minus.
 
I assume this is what is stopping the image being shown.
 
Really sorry if this is something I did somehow but any suggestions where I go to ensure users created stop having image fields that store their files in '-' prefixed folders?
 
Thanks in advance for any pointers, cheers, -Alan
 
Edit 1:
Perhaps the answer is that I have
$config->pagefileSecure = true;
in config.php? Testing to see...
 
Edit 2:
Confirmed, removing the above allows blog profile images to be seen.
 
Any pointers on how to have the benefits of $config->pagefileSecure (or some other mechanism for protecting files) while not breaking blog bio images? Thanks again for any clues :) Cheers, -Alan
Edited by alan

Share this post


Link to post
Share on other sites

Is there more I need to know/do in order to get comment notification working, right now I have a PW site that can send emails AOK but no email is sent when comments are submitted. I have edited the field blog_comments in the admin and listed an email address under Details > Notification > Admin notification email.

Works just fine for me. Have you confirmed email is working properly on your server? Tested with other applications?

...

 
Edit 2:
Confirmed, removing the above allows blog profile images to be seen.
 
Any pointers on how to have the benefits of $config->pagefileSecure (or some other mechanism for protecting files) while not breaking blog bio images? Thanks again for any clues :) Cheers, -Alan

No idea, sorry :-). Let's hear what others say

Share this post


Link to post
Share on other sites

Works just fine for me. Have you confirmed email is working properly on your server? Tested with other applications?

Yes, I have code to reset passwords for users, send info to users etc and that works AOK to send emails on the same site.

I hope I am remembering this correctly, but I think the sequence of events was:

  1. installed the blog
  2. test comment
  3. saw the comment listed in the blog control panel but no email
  4. dug around to see where one listed where an admin email ought to go (I should have done this 1st!)
  5. thought I didn't have the comments field type installed and so installed it (was its presence a pre-req' of installing the blog and I missed that step?)
  6. checked the field blog_comments and found it was the correct field type and listed a bunch of blank fields where I was able to list an admin email address etc
  7. did more comments, all worked AOK in all respects other than sending an email

Does that help at all?

Any pointers on how to have the benefits of $config->pagefileSecure (or some other mechanism for protecting files) while not breaking blog bio images? Thanks again for any clues :) Cheers, -Alan
No idea, sorry :-). Let's hear what others say

Fair enough! :) And no problem with this since I've taken an alternate route and am using the FieldtypeSecureFile module to side-step that :)

Share this post


Link to post
Share on other sites

Dumbfounded by this one. Are you able to start over (i.e. a fresh install)? Otherwise this really is a FieldtypeComments question (a core module) since that's what Blog uses. 

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By gebeer
      I am happy to present my new fieldtype FieldtypeImageFromPage. It is made up of 2 modules:
      Fieldtype Image Reference From Another Page is a Fieldtype that stores a reference to a single image from another page. The image can be selected with the associated Inputfield.
      Inputfield Select Image From Page is an Inputfield to select a single image from images on a predefined page and it's children.
      And there also is a helper module that takes care of cleanup tasks.
      This module evolved out of a discussion about my other Module FieldtypeImagePicker.  It caters for use cases where a set of images is being reused multiple times across a site. With this fieldtype these images can be administered through a chosen page. All images uploaded to that page will be available in the inputfield.
      When to use ?
      Let editors choose an image from a set of images that is being used site-wide. Ideal for images that are being re-used across the site.
      Suited for images that are used on multiple pages throughout the site (e.g. icons).
      Other than the native ProcessWire images field, the images here are not stored per page. Only references to images on another page are stored. This has several advantages:
      one central place to organize images when images change, you only have to update them in one place. All references will be updated, too. (Provided the name of the image that has changed stays the same) Features
      Images can be manipulated like native ProcessWire images (resizing, cropping etc.) Image names are fully searchable through the API Accidental image deletion is prevented. When you want to delete an image from one of the pages that hold your site-wide images, the module searches all pages that use that image. If any page contains a reference to the image you are trying to delete, deletion will be prevented. You will get an error message to help you edit those pages and remove references there before you can finally delete the image. How to install and setup
      Download and install this module like any other modules in ProcessWire Create a page in the page tree that will hold your images. This page's template must have an images field Upload some images to the page you created in step 2 Create a new field. As type choose 'Image Reference From Another Page'. Save the field. In 'Details' Tab of the field choose the page you created in step 2 Click Save button Choose the images field name for the field that holds your images (on page template from step 2) Click Save button again Choose whether you want to include child pages of page from step 2 to supply images Add the field to any template You are now ready to use the field View of the inputfield on the page edit screen:

      View of the field settings

      The module can be installed from this github repo. Some more info in the README there, too.
      In my tests it was fairly stable. After receiving your valued feedback, I will eventually add it to the modules directory.
      My ideas for further improvement:
      - add ajax loading of thumbnails
      Happy to hear your feedback!
       
    • By gebeer
      Although the PW backend is really intuitive, ever so often my clients need some assistance. Be it they are not so tech savvy or they are not working in the backend often.
      For those cases it is nice to make some help videos available to editors. This is what this module does.
      ProcessHelpVideos Module
      A Process module to display help videos for the ProcessWire CMS. It can be used to make help videos (screencasts) available to content editors.
      This module adds a 'Help Videos" section to the ProcessWire backend. The help videos are accessible through an automatically created page in the Admin page tree. You can add your help videos as pages in the page tree. The module adds a hidden page to the page tree that acts as parent page for the help video pages. All necessary fields and templates will be installed automatically. If there are already a CKEditor field and/or a file field for mp4 files installed in the system, the module will use those. Otherwise it will create the necessary fields. Also the necessary templates for the parent help videos page and it's children are created on module install. The module installs a permission process-helpvideos. Every user role that should have access to the help video section, needs this permission. I use the help video approach on quite a few production sites. It is stable so far and well received by site owners/editors. Up until now I installed required fields, templates and pages manually and then added the module. Now I added all this logic to the install method of the module and it should be ready to share.
      The module and further description on how to use it is available on github: https://github.com/gebeer/ProcessHelpVideos
      If you like to give it a try, I am happy to receive your comments/suggestions here.
    • By Robin S
      A module created in response to the topic here:
      Page List Select Multiple Quickly
      Modifies PageListSelectMultiple to allow you to select multiple pages without the tree closing every time you select a page.
      The screencast says it all:

       
      https://github.com/Toutouwai/PageListSelectMultipleQuickly
      https://modules.processwire.com/modules/page-list-select-multiple-quickly/
    • By gebeer
      Hello all,
      sharing my new module FieldtypeImagePicker. It provides a configurable input field for choosing any type of image from a predefined folder.
      The need for it came up because a client had a custom SVG icon set and I wanted the editors to be able to choose an icon in the page editor.
      It can also be used to offer a choice of images that are used site-wide without having to upload them to individual pages.
      There are no image manipulation methods like with the native PW image field.
      Module and full description can be found on github https://github.com/gebeer/FieldtypeImagePicker
      Kudos to @Martijn Geerts. I used his module FieldTypeSelectFile as a base to build upon.
      Here's how the input field looks like in the page editor:

      Hope it can be of use to someone.
      If you like to give it a try, I'm happy to hear your comments or suggestions for improvement. Eventually this will go in the module directory soon, too.
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://github.com/BernhardBaumrock/RockPDF
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
×
×
  • Create New...