Jump to content

Recommended Posts

Allan,

A couple of things:

  1. What version of Blog did you install? I don't know if you are aware there are two version 1.3 and 2.0. I speak about the latter in a couple of posts above. It will soon become the main version.
  2. If you installed version 2.0, which 'blog structure/style' did you install?
  3. You want to use the blank profile to test Blog. As for the 'double' rendering issue read this post. You probably did not install the blank profile? What you should see, after also copying the /css/ and /js/ that come with Blog to your templates folder is something like this. I repeat here that what you see is only a demo. It is up to you to design Blog to look just the way you want. If you need something that is (almost) ready out of the box (design-wise), then you are better of with the Blog Profile. If you want to design the look of your Blog from scratch plus get some additional features, then use Blog (module) :-)
  4. If using Blog 2.0, read up on install instructions above
  5. If you want to make best use of Blog, read the docs/tutorials here

Share this post


Link to post
Share on other sites

@ kongondo

Thanks for the quick reply.

I did use Blog 2.0

Both sites use style 1

I will follow your advice I will re-read  4 & 5 above.

May-be should learn to 'swim' better before tackling Modules.

Thanks again

Allan

PS

I will try other styles and see the difference it makes. Is easy on http://lightning.pw

Share this post


Link to post
Share on other sites

Quick update:

Over the weekend or early next week merging Blog 2 to master and changing status to stable in the modules directory.

  • Like 1

Share this post


Link to post
Share on other sites

I'm embarrassed but I need your help.

I'm willing to go back to another option but I installed option #4 but every quickpost (add) blog post writes itselve in the root of the 'home' directory. How/where do I tell the system to write each blogpost automatically as a child of say 'Home/blog' ?

For sure it's dead simple (and I'll have a red face when I'll read the reply) but I cannot see the tree from the wood right now ..

Thanks in advance,

Bernard 

(pw 2.5.3 - Module-blog 2.0.2)

Share this post


Link to post
Share on other sites

That's why you have the 4 options :D ...to suit the structure you want....Use option 2 if you want posts as children of Blog. That will give you /home/blog/mypost/

  • Like 2

Share this post


Link to post
Share on other sites

Update:

Blog version 2.0.2 committed to master branch and PW modules directory and changed status to stable.

  • Like 2

Share this post


Link to post
Share on other sites

@Creativejay,

Did you try my option 2 suggestion above? I tried it and it works brilliantly (tested on lightning.pw so can give you access before the test site expires) .

Share this post


Link to post
Share on other sites

Fantastic work. I'am now testing 2.02.

I'am not going to use Tags and Authors. Is it possible to hide them in Admin so users can't see them?

Share this post


Link to post
Share on other sites

@toothpaste,

Yes it is possible using PW access settings (permissions and roles). However, by removing Authors and Tags, is it really still a Blog? :P. Also, when you render posts in the frontend you won't be able to hide author names attached posts.

Share this post


Link to post
Share on other sites

@ Kongondo

Firstly, a big thank you for your help! I switched to option #2 and I feel far more confortable with it. Even though I'm far from finished at least I'm really striding foreward as each Soccer team (They all have the same template) now has a different personal blog-category on it's page where the title of the page = the title of the blog-category and obviously ... a single post can appear in several teampages (blog-categories)

the code I used for this is:

<? $blog = $modules->get("MarkupBlog");
$category = $pages->get("/blog/categorieen/")->children->find("title=$page->title");
$posts = $pages->find("blog_categories=$category");
echo $blog->renderPosts($posts,true); ?>

euh so simple to get going .. 

Now .. before I start digging further and get the blog fully functional (comments, css, etc etc) I first would like to translate all EN words to NL -

Q. 1° Is there a specific place where I can do this?

Q. 2° If so, in case there is an update, will it affect the translated terms?

Many thanks,

Bernard 

Share this post


Link to post
Share on other sites

@Bernard,

You can change this line:

$category = $pages->get("/blog/categorieen/")->children->find("title=$page->title");

to this:

$category = $pages->get("/blog/categorieen/")->child("title=$page->title");

Refer to $page->child($selector) in the cheatsheet

  • Like 1

Share this post


Link to post
Share on other sites

Just installed Kongondo blog module in PW multilanguage. Great concept!

I Just have a small question regarding empty template files. If I would like to display posts under a current category (blog_category) I could go with this:

$posts = $pages->find("template=blog-post, blog_categories={$page}");
$blog = $modules->get("MarkupBlog");
//if Blog Posts found, we render them out
if ($posts) {
echo $blog->renderPosts($posts);
}

else {
echo '<p>No posts found</p>';
}

But the haeder and footer are displayed UNDER the post. How do I get posts to be between this?

Share this post


Link to post
Share on other sites

@Bwakad,

Thanks for using Blog.

I moved your thread here since this is the support board for the Blog module. Please note it is not the Blog module profile  :P. OK, back to business.

I Just have a small question regarding empty template files. ......But the haeder and footer are displayed UNDER the post. How do I get posts to be between this?

I honestly do not understand the question :-). If you installed with empty template files, there is no header or footer there at all. Are you talking about your custom header and footer? You render the posts where you want them. Please clarify so I can give you a more definitive answer.

As for your code to display posts under a current category (blog_category) your code will only work if you are rendering those posts in a 'category' page similar to what is discussed a few posts above yours (#161 and #163). There is a related solution here if you want to limit posts of only a certain category but rendering the posts on other pages.

Also had some issues with back end markup...

That is very strange. I have never seen that. Maybe because I have never used the PW multi language site profile. Is that the one you are using? Are you using the stable (2.5.x) or dev version of PW? 

Share this post


Link to post
Share on other sites

Hi thanks for the reply.

1A. I installed the latest stable PW and choose multi-language. This is were the header/footer come from (_main / _init).

1B. I then installed your blog module which gave me the empty template files. The blog templates give me blog posts or categories (whatever I put there) and under it: header - content / sidebar - footer.

I have seen native PW currently prepend and append the _init / _main to ALL templates - which is fine. But I am not sure how to proceed. _main works with this part, should I add $posts in there?

<div id='main'>

        <!-- main content -->
        <div id='content'>
            <h1><?php echo $title; ?></h1>
            <?php echo $content; ?>
        </div>

        <!-- sidebar content -->
        <?php if($sidebar): ?>
        <div id='sidebar'>
            <?php echo $sidebar; ?>
        </div>
        <?php endif; ?>

    </div>

2. The image with the back end issue is in the blog dashboard (posts/categories/tags). It does no damage, but it's just strange. Must be a comma or something in the admin tempate files somewere.

Share this post


Link to post
Share on other sites

Aah I see..

1B: Blog will actually not give you anything unless you selected it yourself/or let the default stay :-). For template files, I don't know if you realise you could have installed demo template files or none at all?

As for the _main / _init stuff, I think you will have to append renderPosts($posts) to $content. Have a read here where Ryan explains how the various site-profiles work. This other tutorial on structuring your template files is also useful. 

2B. Yes, I understood that bit. I just don't know why you are seeing that and others, including myself are not. I will have to test on a multi-language profile install to see if I get the same problem.

Share this post


Link to post
Share on other sites

I  can't get the code to work and hope you can help me.., beginner you know.

On the home page I would like to have the 3 latest posts, only title and the first part of the post. hiding post-byline works fine.

I used the code you advised. Is it possible to get latest posts and not only from a certain category. I have tried to put in my three categories (1042, 1043, 1044) ID's but that doesn't work.

$blog = $modules->get('MarkupBlog');
$category = $pages->get(1043);//This is ID of category'Fanions'. Can also get by other selector, e.g. name, title, etc.
$posts = $pages->find("template=blog-post, blog_categories=$category, limit=3");
echo $blog->renderPosts($posts);

Is it possible to truncate the post length? For example a function from a other post by Ryan.

Share this post


Link to post
Share on other sites

@Toothpaste

I used the code you advised. Is it possible to get latest posts and not only from a certain category. I have tried to put in my three categories (1042, 1043, 1044) ID's but that doesn't work.

Please read the documentation here

Posts are always returned sorted by date, latest first if you pass first parameter of renderPosts($posts) as a string

I used the code you advised. Is it possible to get latest posts and not only from a certain category. I have tried to put in my three categories (1042, 1043, 1044) ID's but that doesn't work.

I am not getting you clearly. Are you saying you want posts from ALL categories or from only THREE (1042, 1043 and 1044). If from only three, you can do the following:

$categories = $pages->find('id=1042|1043|1044');
$blog = $modules->get("MarkupBlog");
$posts = $pages->find("template=blog-post, blog_categories={$categories}, limit=10");

if ($posts) {
    
    echo $blog->renderPosts($posts, true);//the 'true' truncates posts' length
}

Read here about ProcessWire OR selectors.

Is it possible to truncate the post length? For example a function from a other post by Ryan.

Yes. This is all documented in the Blog tutorials. The default truncate length is 450 characters. You can set a custom length in your Blog settings page.

  • Like 1

Share this post


Link to post
Share on other sites

Reading instructions wrong I guess.

Did a new install. Placed the Blog Master folder in modules and installed with demo template files. But this time css and js is off - I can't see css and js under /site/templates/, I CAN find them under /modules/Blog-master/. Am I installing wrong? or should I disgard multi language?

Share this post


Link to post
Share on other sites

@Bwakad,

What you should do is get some sleep then read the instructions again  :lol:  :P  ;) .

The instructions are very clear. You need to read the ReadMe first in its entirety. The reason you don't see the css and js? Here's a quote from the ReadMe 'How to Install':

If you chose to install the demo Template Files, also manually copy over the /css/ and /js/ folders present in Blog module's folder to your /site/templates/ folder.

Share this post


Link to post
Share on other sites

Please read the documentation here

Great tutorial. Very helpful, thank you! 

Is it possible to exclude pagination only on the homepage render posts? For example to set  MarkupPagerNav to false.

Share this post


Link to post
Share on other sites

Great! you was right, needed some sleep. lol

After the copy css/js it's good. I then disabled all append and prepend for blog templates. Because:

PW latest use _main to output header/body/footer;

and blog uses blog-main.inc to output header/body/footer.

Kongondo, can you tell me which file is used in back end for the /blog/posts/ - /blog/categories/ - /blog/tags/ ???

It seems in the Edit part is this code displayed as text (image I showed earlier).

Share this post


Link to post
Share on other sites

Is it possible to exclude pagination only on the homepage render posts? For example to set  MarkupPagerNav to false.

At the moment no. You would have to use CSS to hide the page navs I am afraid..

Kongondo, can you tell me which file is used in back end for the /blog/posts/ - /blog/categories/ - /blog/tags/ ???

It seems in the Edit part is this code displayed as text (image I showed earlier).

I tested in the multi-language site profile and saw something similar. I will raise the issue with Ryan to try resolve this. I don't know what is causing the problem but it is definitely only happening on the multi-language site profile and not the others.

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...