Jump to content

Recommended Posts

@kongondo - to update, what are the necessary steps? I have this running on a big site at the moment. 

I have moved the site to a local environment for testing of the blog updated files you just added. 

Thanks. 

Share this post


Link to post
Share on other sites

@kongondo - Never mind I'm sorry, very tired. We did a big redesign a couple days ago and just launched the new website, with your blog as a module as well! Any hoot, I just replaced your updated files from Github and everything seems to be working great! 

Any other steps besides replacing the files you updated 2 hours ago? 

Share this post


Link to post
Share on other sites

@quickjeff, nope. That should do it. If the version is not showing as 2.3.5 in the modules page on your site, just hit the module's refresh button. Would love to hear about how the site performs if possible, ta.

Edited by kongondo

Share this post


Link to post
Share on other sites

@kongondo - Quick Question, in regards to spam comments, I installed Akismet module and added an API key because I was getting tons of spams however, spam comments I am getting, if I market these as spam and hit save on the post, what happens to the comment? Should I just delete them instead?

Thanks. .

Share this post


Link to post
Share on other sites

Going by the setting in the 'Detail's tab in a comments field, under 'Number of days after which to delete spam' (default = 3), I am guessing the spam will be deleted after those number of days. If you want to delete them yourself that's also OK. In the Blog itself, spam comments on the frontend will only be visible to superusers or logged in users who can edit that page. Try it out and see what happens -)

Just to clarify: 

The comments module  is actually not part of the Blog module, but a core ProcessWire module, hence my 'guessing'.  ;)

Edited by kongondo

Share this post


Link to post
Share on other sites

good evening gentlemen,

so I have recently set up a Vagrant LAMP stack with the your Blog Module to, well, develop a blog.

Unfortunately though, I seem to be unable to reach your website on which you so beautifully used to explain the ins and outs of the API to the module. Apparently the domain got deleted according to the notification on the site.

So, is this a permanent state, did you stop the further development of the module or can we expect to see your site up and running again in a few days?

I really liked the tutorials you offered there, since I don't know that much about web development and it offered a great starting point to get stuff going.

Best wishes, 

DeM

  • Like 1

Share this post


Link to post
Share on other sites

Hi DeM (cool name!)...

Busted!

Yes...the site is currently unreachable...I am moving things around, got caught up in a lot of work and didn't have time to set up the new server with an 'under maintenance' message, blah, blah  :P. Domain hasn't been deleted; it's just not pointing to any IP at the moment...I know, I know, it doesn't look nice but nothing I can do about it, and am not worried about it either ;) . But I appreciate that they tuts were important to you. Glad you found them useful. Hope you can wait a bit longer for me to finish moving stuff. I've got some nice stuff planned...  :-X

Share this post


Link to post
Share on other sites

Phew, nice to hear that. I was beginning to worry whether the documentation would be gone forever. 

but in that case.... This project of mine doesn't have a schedule so I'm going to wait until you've got your documentation up and running again because w/o it I'm lost.

I'm excited to see the new stuff you've got planned, so good luck on your coding, for now :)....

Greetings from Germany,

DeM

Share this post


Link to post
Share on other sites

Oh yea, one other thing..... I tried rendering truncated posts on my front page, which worked fine. When I click on "Show more" on the truncated posts, I would expect the module to show me the full post and render the comments section etc.

Well.... the rendering of the comments etc. works but the post remains truncated, though. It also outputs the "show more" link but when I click that, nothing happens. I use the "blog post" template to show individual posts, but I was unable to find a function that shows me the post in full..... 

Back when your blog was online I remembered that there was an argument that could be passed to renderPosts; something like renderPosts(truncate=false) or something like that. I tried that but when I do so, php throws an error. What was the exact argument / the correct way to enable have a single post including comments rendered in full?

Best wishes, DeM

Share this post


Link to post
Share on other sites

Just remembered that the internet is well, the internet and nothing gets erased (OK, not always) so a snapshot of my old site is on the Wayback Machine. Here you go:

https://web.archive.org/web/20141114094607/http://www.kongondo.com/tutorials/specific-features/creating-a-blog-in-processwire/render-posts

echo $blog->renderPosts($posts);//the default is to show non-truncated posts. So, unless you want them truncated, you don't need the 2nd argument
  • Like 1

Share this post


Link to post
Share on other sites

AAAAAWWW YEEEEA!. Thx... Don't know why I didn't think about that possibility myself. I only tried google cache but something was borked there.

Anyways, thanks again and good luck getting your website stuff going ;-)

Greetings DeM

Share this post


Link to post
Share on other sites

Hi 

I tried, but can't completely delete it.

I figured out the problem I had, so there is no need anymore for it.

All it takes is a lot of concentration and staring at the the screen until a solution pops up.

Thanks for the blog module Kongondo!

Share this post


Link to post
Share on other sites

Hi 

I deleted the Navigation and the sidebars, beacause I don't need them.

Example:

http://jakubdegler.ch/user3/nojs/

BUT!

The paginantion on the bottom does not work, and it also didn't before I deleted the other objects.

Is the pagination-code in blog-main.inc?

Thanks a lot

kuba

FOUND SOMETHING:

The Pagination doesn't work anymore, when I integrate the code below in my template....

In the Blog Demo it works fine.

What am I missing?

Thanks

I included this Blog-Markup on my ownTemplate:

<?php

/**
 * Blog Home template
 * Demo template file populated with MarkupBlog output and additional custom code for the Blog Home Page
 *
 */

    //CALL THE MODULE - MarkupBlog
    $blog = $modules->get("MarkupBlog"); 
    
    //subnav
    //we expect only one such page. we do it this way in this demo to accomodate different blog styles
    $categories = $pages->get('template=blog-categories');
    $subNav = $blog->renderNav($categories->title, $categories->children);

    //main content

    //number of posts to show on Blog Home Page (pagination kicks in if more posts than limit)
    $settings = $pages->get('template=blog-settings');//we get this from the settings page. In your own install you can use a more specific selector
    $limit = $settings->blog_quantity;
    $content = '';

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

   //include the main/common markup
    require_once("blog-main.inc");

?>
Edited by kuba2
code formatting

Share this post


Link to post
Share on other sites

If by pagination you mean the next/prev links, that is rendered by renderNextPrevPosts(). E.g., see the second to last line with $blog->renderNextPrevPosts($page); in blog-post.php demo file

Blog has documentation that covers most of its method. Unfortunately it is currently offline as I shift servers. See the link a couple of posts up for an internet-archived version.

Edited by kongondo

Share this post


Link to post
Share on other sites

Hi Kongondo

I mean the thing in the image

( pagination, right? )

pagination.png

Thanks again

Share this post


Link to post
Share on other sites

That is rendered automatically by the method renderPosts() depending on whether there are more posts than the specified limit. For instance, if you have 20 posts in total, and your requested 5 (i.e. 5 will be shown per page), then the remainder (15) will be spread over the next 3 pages (5 per page).

Share this post


Link to post
Share on other sites

Great thanks...

Now I know where to look.

Thank You again for this module! Can't imagine how much time You put into this.

  • Like 1

Share this post


Link to post
Share on other sites

Hi Kongondo

I solved it - render posts works.

I had the blog.php code pasted in my own template, and everything from the blog worked except renderposts ( it didn't show the prev posts ).

Now I have pasted my html into blog.php and taken blog.php as the template for this specific site. Now it works.

Could You tell me what exactly i managed to do wrong in the beginning? I don't quite understand why it works this way round and not the other.

Probably something very basic, but I am an almost total php novice.

Thanks again

Kuba

Share this post


Link to post
Share on other sites

If pagination wasn't working it is most likely because in your own template's settings, you did not tell it to allow pagination. When editing a template, this is set in the URLs tab -> Allow Page Numbers

  • Like 1

Share this post


Link to post
Share on other sites

For some reason I'm not getting any css styles on my output pages? It's just raw html.

Share this post


Link to post
Share on other sites

I had to move the CSS folder into the template folder. It's in the Markupblog folder in the Modules folder.

  • Like 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 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-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 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 Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...