Jump to content

Recommended Posts

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

  • Like 1

Share this post


Link to post
Share on other sites
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.

  • Thanks 1

Share this post


Link to post
Share on other sites

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.
  • Like 1

Share this post


Link to post
Share on other sites

@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!

  • Like 3

Share this post


Link to post
Share on other sites

Hi,

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites
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 by Ben Sayers
Additional question for kongondo

Share this post


Link to post
Share on other sites
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/

Share this post


Link to post
Share on other sites
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. 

blog-style-1.jpg

Share this post


Link to post
Share on other sites

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:

image.thumb.png.9f44f871f5a35e9f0bcfe80f3776469d.png

French version:

image.thumb.png.cf4db587b15eac37347e5ba7dcb043f4.png

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites

Have a look here:

 

  • Like 1

Share this post


Link to post
Share on other sites

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.

  • Like 1

Share this post


Link to post
Share on other sites

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.

 
 
  • Like 4
  • Thanks 1

Share this post


Link to post
Share on other sites

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

 

  • Like 1

Share this post


Link to post
Share on other sites

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.

  • Thanks 1

Share this post


Link to post
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 MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) TrelloWire in the modules directory Module configuration

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...