Jump to content

Recommended Posts

We are talking about two different things here then. You said templates (blog-post) but it seems you mean template files (blog-post.php)? What do you mean by layout? Do you mean the HTML markup or the layout of fields in the template? If HTML, Blog will not get in your way. You can use whatever template file you like but you need to associate your blog posts with the template blog-post. I don't know how much you've read up on the separation of these two concepts but you can have your posts use the template blog-post with a totally differently named template file or none at all. In a nutshell, Blog doesn't care about template files - just the templates. Btw, a couple of posts up I have provided a Gist of the method renderPosts() whose markup you can modify to suit your needs (if you are referring to the markup renderPosts() generates) and use that instead of Blog's renderPosts(). That will not stop you from using Blog's other methods, e.g. renderTags().

Share this post


Link to post
Share on other sites

@Peter Knight I can confirm that Kongondo's example gist works no problem. Can easily add mark up to the necessary parts of the function. In my case I've added divs to suit bootstrap. No problem. And if you wanted to create separate markup for a single post you could either do it with a separate function or with a conditional statement within the renderPosts() function.

  • Like 2

Share this post


Link to post
Share on other sites

@Kongondo 

Can confirm I meant blog-post.php. IE The template files. Best thing for me to to is grab some time and actually try it :)

Share this post


Link to post
Share on other sites

Peter, I've added a lot of custom fields to my blog-post template, so my template file for the blog post itself is going to have a lot of calls to the fields listed for the template so that I can't rely on the module to output everything I want in the way that I want. It should be totally possible, and the module has a lot of other features that make it worth my while (multiple authors, the dashboard, etc). Unless you're stripping even more off the blog than just the template output for the individual posts, I think I'd stick with using it. My 2¢!

  • Like 2

Share this post


Link to post
Share on other sites

@kongondo is the total blog-post count for the user stored anywhere?

I'm trying to list my authors (in a custom admin page) in order of post count (greatest to least). Anything you can think of that would do it? Thanks again!

I see "$authorPublishedCnt = count(wire('pages')->find("template=blog-post, created_users_id={$author->id}"));" in ProcessBlog.module line 1840, which seems about what I'm looking for... though I'd like to subtract unpublished posts (which I can do with math in a later line if necessary). Is there a way for me to access created_users_id in admin? I tried that and createdUser but they both threw errors.

I love how typing out a question to you almost always helps me think through it. Sometimes I'm lucky enough to be inspired to try something before I post the question. Other times, not so much.

So the call I ended up using was:

$points = count(wire('pages')->find("template=blog-post, created_users_id=$mobster->id"));

The trouble I was having was that I was comparing the user id to the page name. Doink!

Edited by creativejay

Share this post


Link to post
Share on other sites

Cool. But that will just show the number of posts they have but not (necessarily) sorted according to their individual posts count. For that you would need something like this...

$posts = $pages->find("template=blog-post, sort=created_users_id.count");//you might want to limit results depending on use case

//test it....it should output the list in DESC order...
foreach ($posts as $post) {

  echo $post->createdUser->title . ' - ' . $post->title . '<br>';
  
}

Count selectors – finding matches by quantity

http://processwire.com/api/selectors/#count

  • Like 1

Share this post


Link to post
Share on other sites

Hey, look at that! I stepped away before tackling the sort order and you did the work for me!

I have to add some posts for the other users to test this, since for now post count order is the same as the default. I'll report back in a few minutes. Just wanted to say my thanks!

Share this post


Link to post
Share on other sites

Btw, unrelated, note that it is possible to change the author of a post. When editing the post, just go to its settings tab and under 'Created by User' you can change the user.

  • Like 1

Share this post


Link to post
Share on other sites

Okay, I see your query was looking at blog-post, so the created_users_id.count applies to the field created_users_id which is part of a blog-post page.

What I'm actually looking to do is sort the user list by the total (published) posts attributed to the user.. so I need to build that attribution somehow (before the query).

What would you do? My brain keeps telling me I should create a new field for template user called user_post_count, and write a hook for each post save that would assign the value of created_users_id.count to that field. Is that too convoluted?

Share this post


Link to post
Share on other sites

That's exactly what that code does :-). Did you try it? Or am I missing something here? What do you want your list to show? Authors only? Or authors + their count of posts? e.g. John - 35, Mary 23, Simpson 5?

Edited by kongondo

Share this post


Link to post
Share on other sites

It didn't quite work as-is. The list it output was the top user and the title of a post, one line for each post. Then it sorted the next user's single post.

So it did sort correctly, but it didn't display the number of posts for that user and I only wanted one result per user.

So I attempted to use the sort filter but of course since I was still searching users, not posts, it wouldn't work.

In the screen below you see the table with the correct information but the wrong order. Beneath that is the order and information from your code.

admin-custom-page-user-list-by-published

Share this post


Link to post
Share on other sites

I see. The following should do it. It could probably be made simpler but can't think straight this late hour :D

//find blog authors
$authors = $users->find('roles=blog-author|superuser, sort=title');
//array to hold author TITLES and their posts' count
$authorsList = array();

foreach ($authors as $author) {
    //count number of posts by this author
    $authorPublishedCnt = count($pages->find("template=blog-post, created_users_id={$author->id}"));

    //we assume no two authors with identical TITLES, otherwise older will be overwritten
    //author title is $key and their post count $value
    $authorsList[$author->title] = $authorPublishedCnt;

}

//sort the associative array $authorsList by posts count ($value), DESC
arsort($authorsList,1);

//rest of your code here to loop through the sorted array above

Share this post


Link to post
Share on other sites

As written, that only indexes the post count: Array ( [0] => 6 [1] => 1 [2] => 0 )

Not sure why it won't let me assign my variable as a key. Will tackle it more tomorrow.

Edited by creativejay

Share this post


Link to post
Share on other sites

You have the author title in the array keys...But you have to first make sure that you have entered the 'titles' of your authors in their user pages, i.e. the 'Display name (first and last name) field that Blog adds to user pages otherwise the array keys will be empty :-). Again, we are using their 'titles' not their 'names'. However, if you want to use their names instead, just modify the code above like so...(but I prefer title :-))

//find blog authors
$authors = $users->find('roles=blog-author|superuser, sort=title');//sort doesn't matter here, so can remove
//array to hold author NAMES and their posts' count
$authorsList = array();

foreach ($authors as $author) {
    //count number of posts by this author
    $authorPublishedCnt = count($pages->find("template=blog-post, created_users_id={$author->id}"));

    //we assume no two authors with identical NAMES, otherwise older will be overwritten
    //author NAME is $key and their post count $value
    $authorsList[$author->name] = $authorPublishedCnt;

}

//sort the associative array $authorsList by posts count ($value), DESC
arsort($authorsList,1);

//output the author list and post counts
foreach ($authorsList as $key => $value) {
    #this is just for testing. Use your own markup of course
    echo 'Author Title: ' . $key . ' - Author Post Count: ' . $value . '<br>';
}
  • Like 2

Share this post


Link to post
Share on other sites

Thank you kongondo! As usual I can go to sleep trusting that the ProcessBlog Fairy will leave working PHP code underneath my pillow...

This seems to be the line that made the difference "foreach ($authorsList as $key => $value) {"

Got that working now! I'm sure I'll be back with something else soon! ;) Thanks again!

Share this post


Link to post
Share on other sites

Great Module! Thanks!

I miss one litte functionality - display related posts (or did I miss something?).

Maybe someone else needs this, so here is the code (I use this in a TemplateDataProvider):

  public function populate() {
    $limit = 3;
    $selector = array(
      'template' => 'template=blog-post',
      'id' => 'id!=' . $this->post->id,
      'categories' => 'blog_categories=' . $this->post->blog_categories,
      'tags' => 'blog_tags=' . $this->post->blog_tags
    );

    // find posts same tag AND category
    $related = wire('pages')->find(implode(', ', $selector));

    if ($related->getTotal() < $limit) {
      // find posts same category
      $related = $this->getRelated($related, $selector, 'tags');

      if ($related->getTotal() < $limit) {
        // find posts same tag
        $related = $this->getRelated($related, $selector, 'categories');
      }
    }

    $this->related = $related;
  }

  private function getRelated($related, $selector, $remove) {
    $selector['id'] .= '|' . (string)$related;
    unset($selector[$remove]);
    $rel = wire('pages')->find(implode(', ', $selector));

    return $related->import($rel);
  }

  • Like 5

Share this post


Link to post
Share on other sites

Thanks for this justb3a. We currently don't have this functionality. It looks like something I should add. I'll consider it.

  • Like 1

Share this post


Link to post
Share on other sites

Regarding "related posts", I also think that it's a pretty important for any blog out there. As a blogger you want readers to stay as long as possible and visit as many posts as possible. A feed of related posts is a great way to achieve that.

Not sure if it's still up-to-date, but I've used this Gist by Soma in some projects a while ago, mainly for the scoring part :)

  • Like 2

Share this post


Link to post
Share on other sites

I just noticed that a superuser who created 9 pages that are unpublished OUTSIDE of the blog in the tree has a listing of 9 pages as pending in the Blog / Author dashboard. Not sure why, as the module seems to limit it to the blog-post template. I thought I'd mention it.

Share this post


Link to post
Share on other sites

I just noticed that a superuser who created 9 pages that are unpublished OUTSIDE of the blog in the tree has a listing of 9 pages as pending in the Blog / Author dashboard. Not sure why, as the module seems to limit it to the blog-post template. I thought I'd mention it.

Well that's just plain impossible unless you changed something :D. Just to be sure, I've just tested it...

  • Like 1

Share this post


Link to post
Share on other sites

Regarding "related posts", I also think that it's a pretty important for any blog out there. As a blogger you want readers to stay as long as possible and visit as many posts as possible. A feed of related posts is a great way to achieve that.

Not sure if it's still up-to-date, but I've used this Gist by Soma in some projects a while ago, mainly for the scoring part :)

Thanks for reminding me about this one (I actually forked it a long time ago and forgot about it!! Never thought to use it). Interesting approach Soma uses  - raw MySQL (although I don't think I'll have to hook into anything if I adopt this). I'll compare it more closely to justb3a's plus any other ideas I might have and make a decision...

Share this post


Link to post
Share on other sites

Also wondering whether to define a 'related post' as only one that has this matching 'tag' AND this matching 'category' to the exclusion of also has either this matching 'tag' OR has this matching 'category'...Hmm, maybe let the dev decide...

Edit:

Also wondering if can/should use or-groups here? Just my loud musings here in case I forget...ignore me :-)

Edited by kongondo

Share this post


Link to post
Share on other sites

Well that's just plain impossible unless you changed something :D. Just to be sure, I've just tested it...

I agree, I'm looking at line 1841 in my (untouched) ProcessBlog.module. I see no reason that pages with template 'form-builder', 'blog', 'blog-widgets', 'swmb_error', or 'admin' should show up in that list. However, when I add 'parent=/blog-posts/' to the filter, the pending count returns to 0.

I'm just the black child fluke-finder. ;)

Share this post


Link to post
Share on other sites

I'm searching back through this discussion and not finding if anyone ever came up with a solution that prevented blog-author from editing other users' posts (other than their own).

Was anything ever worked up or around to limit people to editing just their own content?

EDITED TO ADD: Okay, I found this which blocks the users from editing other people's content:

https://processwire.com/talk/topic/3875-module-to-add-userid-to-pages-and-control-edit-permissions/?p=37915

I'm getting there!

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