Jump to content

Module: Blog


kongondo

Recommended Posts

Clicking 'Like' is not enough. V2 is brilliant - being able to choose the url structure is an absolute killer, and (for me, anyway) being able to not have comments at all from the install process (when/if I get round to migrating my own blog (very neglected) from WP, I intend to use Disqus).

Thank you Kongondo!

  • Like 1
Link to comment
Share on other sites

Yes, I was aware. My main problem is not being able to settle on a way of implementing the site. I had this daft idea of using no JS at all (no jquery or anything) for the front end, just CSS, but there are a few problems that rear up as a result. And then really interesting stuff like http://labs.ft.com/2014/09/polyfills-as-a-service/ (don't know if it has been mentioned hereabouts before) come along and really beg to be used...

Link to comment
Share on other sites

@kongondo

Hello Kongondo

Firstly, Thank you for showing me the way as to how to upgrade. I did so successfully and even learned as to how to 'Cleanup' and then successfully re-install from within the module page one of the 4 options.

I'm sorry to be a pain but I'm simply not finding my way as to render a post on the homepage without things like: 

Posts 1 to 1 of 1  
0 (referring to comments)
and also e.g. Posted by bernard, 23 SEPTEMBER 2014 3:24 PM
 
I tried just about everything but I'm not doing it right so after struggling for the whole day could you please show me how to get ONLY the title, blog_body and an image out of a situation like:
				<? $blog = $modules->get("MarkupBlog");
					$category = $pages->get(1452);
					$posts = $pages->find("blog_categories=$category");
					echo $blog->renderPosts($posts,true); ?>

I really looked everywhere but I simply don't understand how to put 1+1 together. Silly hé

Thank you in advance  :-[

Bernard

 
Link to comment
Share on other sites

@Bernard,

Currently there is no way to do that via the Blog API. Simply use CSS to hide them. E.g. to hide the 'Posted by Bernard, 23 September 2014 3.24 PM' add this to your style sheet:

.post-byline {
    display: none;
}

:-)

As for image, where is that image coming from? Is it one uploaded via the images field in a blog post or it is embedded in blog_body? If the former, access it normally using PW images API. If the latter, then it should be output with blog_body...

Link to comment
Share on other sites

@ Kongondo 

Pffiew   wow, now I think I'm starting to see clearer, Kongondo. So I guess the same for: 

.num-comments-icon {
     display: none;
} 

=> in your tutorial I see no class for 'Posts 1 to 1 of 17' - Can this be hidden too? (actually this is the most disturbing one ... imho)

Concerning the image(s),  I want to pull one image out of the images field of the blog post and render it above the blogpost and the rest of the images, a little deeper in the page where you see 'Hoogtepunten van de laatste match'

Thank you, Kongondo for stopping me to look in the wrong direction!

EDIT:

- Hiding 'num-comments-icon' and 'post-byline' works perfectly (newbees will love me reading this) yet for the <h3 >e.g. ''Posts 1 to 1 of 17" I'm still in the dark as how to make it disappear too.

- Images: The intro to the blog-post resides in the middle of the home-page with lots of content from different sources around it. Just like I tried to get 'title' and 'blog_body' without success, how do I tell the PW images API not to look in $page->etc but in the post being generated by the MarkupBlog? I'm feeling so close to the answer yet I'm still flopping around generating tons of Error Notifications in my mailbox. Am I dreaming for the impossible or should I just forget about this?

It was my plan that every time a new post gets added to the blog in a specific category (in my case: a soccergame of the main team + pictures) THEN  the center piece my home page would automatically change as well (small intro to the blog + lots of pictures)

Link to comment
Share on other sites

I have added a posts-count class to the <h3>

Concerning the image(s),  I want to pull one image out of the images field of the blog post and render it above the blogpost and the rest of the images, a little deeper in the page where you see 'Hoogtepunten van de laatste match'

This is a bit vague. I am not sure exactly where you want that image above the blogpost. Do you mean above post title ('Fanions - K.F.C. Heist - Nieuwpoort') or just below it? If you want it above, that means you want the image before the post is rendered ($small post from what I can see). That means, you have to call that image in your template file. That is tricky because you need to programmatically  fetch one image from the post that you have rendered. It is not impossible though but I need to know your situation better.

  1. How many posts will you be outputting at a time in that 'middle' area of the home page
  2. How will you be calling that post? The latest added post? A specific one?
  3. You said there will be multiple images per post, which image are you interested in? The first one? The last one? A random one? A specific one?

Assuming you will be calling only 1 post, the latest published one, and outputting its first image...

/*find the latest post and pass that as a Page or even a string to renderPosts(). You could even just call renderPosts("limit=1, true") but we want to use the Page later to grab the image*/
$post = $pages->get('template=blog-post, sort=-blog_date');

#get and output your first image
$image = $post->blog_images->first();
if($image) echo "<img src='$image->url'>";

#render your 'small' post
$blog = $modules->get("MarkupBlog");
echo $blog->renderPosts($post, true);
  • Like 1
Link to comment
Share on other sites

Updated Blog to version 2.0.1 on dev branch.

Main changes

  • Corrected an oversight whereby comments whose post pages were set to not show comments, i.e. 'disable comments', were still visible when viewed in 'comments' page and 'recent comments' widget. Now, only admin users will be able to see such comments in the 'comments' page and 'recent comments' widget
  • In respect of the above comments, when viewed on the 'comments' page, similar to those tagged 'SPAM' or 'PENDING', they are now tagged as 'HIDDEN'. As stated, these are only visible to admin users. Of course if a post's comments are subsequently set to be shown, these will be visible to all users and the HIDDEN tag will be removed since they are no longer hidden :-)
Link to comment
Share on other sites

Hi Kongondo,

If you check back now you'll see the first fruit of how you really helped me. OH yes, the road will be long for me to really grasp the basic simplicity of the PW API, selectors, etc etc &co but at least I managed to render content and pictures from a blogpost on 2 separate locations in the middle of my homepage     >:D AMAZING !!

Sure, I will keep going through trial and error but at least you (once more) showed me the path to follow ..  

For 'Fanions - K.F.C. Heist - Nieuwpoort' I put the following:

<!-- Column -->
<div class="col-1-4">
<h3>Heet van de naald</h3>
<div class="mosaic-block circle">
<? $blog = $modules->get("MarkupBlog");
$category = $pages->get(1452);
$posts = $pages->find("blog_categories=$category");
$post = $pages->get('template=blog-post, sort=blog_date');
$image = $post->blog_images->first();?>
<div class="mosaic-backdrop">
<img src="<?php if($image) echo $image->url; ?>" alt="Mock" /></div>
</div>
<? echo $blog->renderPosts($posts,true); ?>
</div>

=>> AND FOR "Hoogtepunten van de laatste match" I changed the $variableNames as I intend to eventually pull random pictures out of many posts and limit them to 8 or 12 or so 

<ul class="col-1-1 thumb-gallery super-list variable-sizes clearfix" id="thumb-gallery">
<!-- Start Thumbnail -->
<? $postimgblog = $pages->get('template=blog-post, sort=blog_date');
$imageblog = $postimgblog->blog_images; 
foreach ($imageblog as $image) { ?>
<div class="col-1-5 element cat-1">
<li><div class="mosaic-block circle"><a href="<?php if($image) echo $image->url; ?>" class="mosaic-overlay fancybox" data-fancybox-group="gallery" title="plock"></a>
<div class="mosaic-backdrop"><img src="<?php if($image) echo $image->url; ?>" alt="plock" /></div></div>
</div></li>
<? } ?>	
</ul> 

=> selectors & co will help me to filter things in time and there is plenty of playing room I guess to fill ALT and TITLE with who knows ... blogtitles, category-names, dates or whatever combination, not so? 

Even though I'm an primate in PW I've got hope everything will work out in time and sweat - THANK YOU AGAIN!

Bernard

ps. how do I make Post x to x of xy post dissapear? And where do I translate things to dutch?

Link to comment
Share on other sites

Glad you got it sorted. I notice in your code you are retrieving the FIRST post published (sort=blog_date) rather than the LATEST one (sort=-blog_date). Notice the hyphen. Is that intentional? Also, you may want to limit the amount of posts you retrieve in $postimgblog  in case you will have many posts...

As for making Post x of xx disappear, didn't you read my post properly? :-) In the latest Blog 2 update the <h3> now has a class <h3 class=posts-count>

Link to comment
Share on other sites

Hi Kongondo,

- The omit of the Hyphen was intentional indeed as there only are 2 posts: Yours (when I installed V2) and mine which I postdated to 30/8 or so  :rolleyes: 

I saw your new post appearing but I was writing my previous post to you (and thinking a lot) so .. you solved the post-count problem too hein? For sure this will in future help many noobies to walk a clean road. So happy that even a non-coder like me can be useful for the greater purpose .. 

fyi on my phone the css display: none; didn't catch on but that's my problem to go digging deeper as to which css-file dictates what. Maybe I should just put it in the html (which in the old books is not good practice but .. who cares)

Tomorrow, I will install your new version and also start working towards my final goal (read:dream) for your Blog-system:

For each team under the menu tab 2014-2015 I intend to

  1. Move the trainers from the Info tab to a Trainer tab because:
     
  2. I want to render a Blog category per team under the Info tab (starting with the Fanions as they are the only team with an independent template file (better to experiment where it disturbs on a limited scale)) (Even though the site is not 'officially' open there already are >150++ pageviews/day .. so I have to hurry to get things right - got no choice )
     
  3. If I'm thinking right, blog-post is a landing page only from the home page and the menu on the left of that particular page will lead people to the 'team' pages where the 'info' landing-tab will be  the 'Team category blog page'.
    The other tabs (calendar, trainers, players) should co-exist I hope  --even on a smartphone-- like they do now. 
    Even more so  --IF I understand PW right-- blog-post.php has the ability to act as an invisible filter to render(echo) whatever content elsewhere -if need be-.

     
  4. Next I want to get comments, pagination etc etc working while the 'tab' eco-system stays 'alive' per team within each 'team page'.
     
  5. Only then If that mechanic works, in principle I can start learning as to how to add a script to every member-page of the club (which already has a hidden info page with many fields) and give them the ability to log into their own profile -> which can be extended for those who have  to become an author in blog-posts, manager, etc etc

​Even though I'm standing on a sandcastle only 200m from the sea while looking at my first PW site as if I where standing on a mountain, --One thing for sure-- The little things I'm doing now would never have been possible without PW and it's people. 

Bernard

Link to comment
Share on other sites

@kongondo I'm testing the dev branch (URL scheme 3 and comments not installed, per my earlier comments here) and a few problems appear, which seem to be coming mainly or entirely from the markup module and the included template files. Am I better posting here or on GitHub?

Link to comment
Share on other sites

Github please, thanks. If it turns out they are not bugs, we'll return here :-). Also, let me know which version you installed. There were markup issues involved in the version attached in my post above (I'll delete that now) so you should really be using the Github version (2.0.1).

Link to comment
Share on other sites

@kongondo thank you so much for this module, it's exactly what I need for a site I've been wanting to get around to for two years. Now I'm glad I never got the chance before! Your documentation for it is beautiful, as well. I appreciate the time and effort that went into it!

// removed question because I found my answer. ;)

  • Like 1
Link to comment
Share on other sites

Okay, I think I have a question worthy of typing now...

In my particular case, there are three types of templates for my blog's content, depending on which of four categories it is posted in. Because I'd like to require some of these fields only in certain categories, I don't want to just add the fields and only render them for certain pages because if I require them for posts that won't show them that might annoy my authors. If I don't require them my authors may not include them when I actually need them.

Example:

Category A - Uses Template A with Field Group A (blog posts with lots of extra fields)

Category B - Uses Template B with Field Group B (standard blog post, pretty much what you created as default)

Category C - Uses Template C with Field Group C (no description area, one image with caption and tags, plus title)

Category D - Uses Template B with Field Group B(standard blog post, pretty much what you created as default)

I was hoping that under the settings for each individual category I could pick what type of template their children could use. When I added my Template_A_post to the allowed children for Category A, I was able to edit an existing post from that category and change the template to Template_A_post, but when the blog posts list refreshed, it disappeared. So this is more problematic than just allowing different templates, it seems. Template_A_post is a clone of the blog-post template with a couple extra fields added so far.

Can you suggest a way to do this within the ProcessBlog module without fiddling with the module files themselves? I'm running ProcessBlog 1.3 in PWire 2.5.

As I mentioned before, I have been planning this blog for a while. My original plan (as of early 2013) was to use a different form in FormBuilder to create pages in each category, using specific templates, on form submit.

Update: I can combine my original plan with the new blog module, by creating FormBuilder forms with the information I want and passing it to blog post, which has all custom fields as optional. This might actually work out well, as I could create a whole 'front-end-back-end' for my contributors so I can avoid customizing the admin as much as I thought I might need. Do let me know if you see a way to create custom blog templates directly, though!

Link to comment
Share on other sites

@Creativejay,

I don't see any easy way to do this out of the box. If I get you correctly, you have two options one of which I doubt will work well.

Option 1.

Similar to what you attempted, change the template 'blog-posts' to allow children that use your other extra 'blog-post' templates, e.g. 'blog-post-a', etc. This will work fine with renderPosts() [a MarkupBlog method] since you can pass it a PageArray of your posts irrespective of their templates. The only problem for you is that renderPosts() will not render your other custom fields since it doesn't know about them. So, this option is pretty much dead in the water unless you customise MarkupBlog's code OR separately echo out those fields in your template file. In addition, your posts that use other custom templates will not be visible in the Blog dashboard (ProcessBlog).

Option 2.

Add your custom fields to the template 'blog-post' and use the module 'Page Edit Field Permission' to hide your custom fields as relevant to your Posts types A - D. In your template files, you will need to echo your custom fields separately from renderPosts(). I think I would go for this option since it requires the least work and you only have 1 template to deal with..In your template file you would only echo out your custom fields if they were not empty.

Both options will survive an upgrade since Blog doesn't recreate fields, templates, etc when you update the module.

Update:

I have just seen your update. Don't know much about FormBuilder so can't comment if your method will work...

Link to comment
Share on other sites

Hi kongondo

I have just uploaded your module to two sites on lightning.pw

The first was loaded on a default-site profile http://fermium-z0t.lightningpw.com/

Is this what you would expect to see???

If you click on blog in nav again is this what I should get?

The second site was loaded onto a blank profile http://gold-03z.lightningpw.com/

Again is this what you would expect to see???

If I then add /blog to the url http://gold-03z.lightningpw.com/blog/

This is more like what I would expect.

​As a newbie I find it very difficult to continue development with either of these sites.

I found it much easier with the older blog site profile.

I realise that the improvements are worth the extra effort on my part.

Did I possibly not install correctly?

Regards

Allan

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Similar Content

    • By MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.
      https://github.com/techcnet/ProcessFileManager

      Warning
      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      Dragscroll
      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
       
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

       
    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      Links
      ProcessWire module directory
      github.com
    • By Robin S
      Repeater Easy Sort
      Adds a compact "easy-sort" mode to Repeater and Repeater Matrix, making those fields easier to sort when there are a large number of items.
      The module also enhances Repeater Matrix by allowing a colour to be set for each matrix type. This colour is used in the item headers and in the "add new" links, to help visually distinguish different matrix types in the inputfield.
      Screencasts
      A Repeater field

      A Repeater Matrix field with custom header colours

      Easy-sort mode
      Each Repeater/Matrix item gets an double-arrow icon in the item header. Click this icon to enter easy-sort mode.
      While in easy-sort mode:
      The items will reduce in width so that more items can be shown on the screen at once. The minimum width is configurable in the field settings. Any items that were in an open state are collapsed, but when you exit easy-sort mode the previously open items will be reopened. You can drag an item left/right/up/down to sort it within the items. The item that you clicked the icon for is shown with a black background. This makes it easier to find the item you want to move in easy-sort mode. You can click an item header to open the item. An "Exit easy-sort mode" button appears at the bottom of the inputfield. Configuration
      In the field settings for Repeater and Repeater Matrix fields you can define a minimum width in pixels for items in easy-sort mode. While in easy-sort mode the items will be sized to neatly fill the available width on any screen size but will never be narrower than the width you set here.
      In the field settings for Repeater Matrix you can define a custom header colour for each matrix type using an HTML "color" type input. The default colour for this type of input is black, so when black is selected in the input it means that no custom colour will be applied to the header.
      Exclusions
      The easy-sort mode is only possible on Repeater/Matrix fields that do not use the "item depth" option.
       
      https://github.com/Toutouwai/RepeaterEasySort
      https://processwire.com/modules/repeater-easy-sort/
×
×
  • Create New...