Jump to content

Recommended Posts

Allan,

A couple of things:

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

Share this post


Link to post
Share on other sites

@ kongondo

Thanks for the quick reply.

I did use Blog 2.0

Both sites use style 1

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

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

Thanks again

Allan

PS

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

Share this post


Link to post
Share on other sites

Quick update:

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

  • Like 1

Share this post


Link to post
Share on other sites

I'm embarrassed but I need your help.

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

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

Thanks in advance,

Bernard 

(pw 2.5.3 - Module-blog 2.0.2)

Share this post


Link to post
Share on other sites

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

  • Like 2

Share this post


Link to post
Share on other sites

Update:

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

  • Like 2

Share this post


Link to post
Share on other sites

@Creativejay,

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

Share this post


Link to post
Share on other sites

Fantastic work. I'am now testing 2.02.

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

Share this post


Link to post
Share on other sites

@toothpaste,

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

Share this post


Link to post
Share on other sites

@ Kongondo

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

the code I used for this is:

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

euh so simple to get going .. 

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

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

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

Many thanks,

Bernard 

Share this post


Link to post
Share on other sites

@Bernard,

You can change this line:

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

to this:

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

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

  • Like 1

Share this post


Link to post
Share on other sites

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

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

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

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

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

Share this post


Link to post
Share on other sites

@Bwakad,

Thanks for using Blog.

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

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

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

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

Also had some issues with back end markup...

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

Share this post


Link to post
Share on other sites

Hi thanks for the reply.

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

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

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

<div id='main'>

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

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

    </div>

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

Share this post


Link to post
Share on other sites

Aah I see..

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

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

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

Share this post


Link to post
Share on other sites

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

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

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

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

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

Share this post


Link to post
Share on other sites

@Toothpaste

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

Please read the documentation here

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

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

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

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

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

Read here about ProcessWire OR selectors.

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

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

  • Like 1

Share this post


Link to post
Share on other sites

Reading instructions wrong I guess.

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

Share this post


Link to post
Share on other sites

@Bwakad,

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

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

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

Share this post


Link to post
Share on other sites

Please read the documentation here

Great tutorial. Very helpful, thank you! 

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

Share this post


Link to post
Share on other sites

Great! you was right, needed some sleep. lol

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

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

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

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

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

Share this post


Link to post
Share on other sites

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

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

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

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

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

Share this post


Link to post
Share on other sites

Hi Kongondo

Any plans to pull in a users Gravatar based on their email address? Just like these forums do?

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 jploch
      Hey folks,
      for a module (a pagebuilder based on PageTable) I need to save some settings as JSON. The values are saved for each page table item (a pw page). It's working well, but I am looking for ways to improve the structure I have. As I'm not that experienced with JSON, maybe someone more experienced can take a look and tell me if my approach is good practice. 

      My goal is to make all the items accessible by page id, without looping over them (using objects instead of arrays):
      // access from template with pw page var $jsonObject->items->{$page}->cssClass; Her is an example of my JSON structure:
      { "items": { "3252": { "id": "3252", "cssClass": "pgrid-main", "breakpoints": { "base": { "css": { "grid-column-end": "auto", "grid-row-end": "auto", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "60px", "padding-right": "60px", "padding-top": "60px", "padding-bottom": "60px", "background-color": "rgb(255, 255, 255)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3686": { "id": "3686", "cssClass": "test_global", "breakpoints": { "base": { "css": { "grid-column-end": "-1", "grid-row-end": "span 1", "grid-column-start": "1", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3687": { "id": "3687", "cssClass": "block_editor-3687", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3696": { "id": "3696", "cssClass": "block_editor-3696", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } } }, "breakpointActive": "base", "breakpointActiveSize": "@media (min-width: 576px)" }  
    • By jploch
      Fieldtype Page Table Grid
      This is a sneak preview of a side project I've been working on for quite some time now. A lot of work and thought has gone into this, so I will most likely release this as a commercial module at some point in the near future. 

      As a designer (and developer) I get the appeal of a WYSIWYG editor. After playing around with some WYSIWYG page builder tools, I always felt something was wrong about them. So I decided to build my own PW version based on PageTable.

      Here is a small demo (using AdminThemeCanvas, but its working with other admin themes as well) :
      There is also a complete website that I built for a friend of mine using this module and some custom blocks.
      Concept
      This fieldtype shares a lot of features with PageTableExtended: it's also an extension of PageTable and renders the block templates in the backend and frontend (native PW templates and fields). You can also add your own css via module settings.
      The difference is, this fieldtype also gives you the ability to rearrange and resize elements in a visual way as well as enable inline editing for text, ckeditor and file fields. Similar (and promising) attempts have been made, but I wanted something based on native CSS grid instead of a CSS framework...so I built my own version. Most CSS frameworks are based on flexbox, which is great for layouting elements horizontally. With CSS grid, you can place elements horizontally and vertically, allowing for layouts that were not previously possible with CSS. Similar to webflow, this fieldtype uses javascript (in the backend) to let you manipulate CSS grid in a visual way to design fully responsive websites (or parts of them). It should still be possible to include a CSS framework if you like (just add the classes to your block markup and include the CSS via module settings).
      The CSS grid layout manipulations are saved in a single field as a JSON array and used to generate a dynamic stylesheet that you simply include in your main template (no inline styles). The styles are saved within the breakpoint you select and cascade down to smaller breakpoints. That means you can specify just the basic breakpoint and adjust other breakpoints if needed. The exception is the mobile breakpoint which will display everything in one column as a default (you can change the layout here too).
      The fieldtype also comes with an optional style panel to manipulate some additional CSS properties directly on the page. You can customize the panel or disable it completely from the module settings (and just use a CSS file that you include via module settings). The style panel is based on inputfields (nothing is saved to the database). This means that you just have to install the module and all fields are available to all blocks automatically (this can be customized). It also has the benefit that your installation is not flooded with fields; this module only installs one field.
      Don't want to give your customer all that power? Design features can be disabled for certain roles. The grid editor role can just edit the content and use the inline editing feature to edit content quickly. You can then also grant access individually to the style panel, resize or drag functionality.
      Features
      Blocks are just pages Blocks are defined by native PW templates and fields Manipulate CSS grid in a visual way to design fully responsive websites (or parts of them) Design features can be disabled for certain roles Inline editing of text, ckeditor and file fields The layout is 100% CSS grid (very small css file size) Simply drag and resize to manipulate grid items directly inside the backend Manipulate grid columns and rows directly on the page (use any number of columns you want) All style manipulations are saved as JSON and used to generate a dynamic stylesheet that you just include in your main template (no inline styles) Nested groups/grids (child pages of nested blocks are created under group parent) Global blocks work with page reference field (changes on one page, changes all blocks on all pages) Manual and auto placement of grid items Define custom icons for your blocks via native template settings (template -> advanced -> icon) Option to load lazysizes in the backend to enable lazy loading of assets with class lazyload Works with all default and ui-kit based admin themes If you have any questions or feedback, let me know.
    • By bernhard
      I built this module because I needed a versatile solution to replace tags and simple if-blocks in some E-Mails and PDF documents.
      If you only need to replace static tags (no if-conditions), then you can use default PW api and need no module:
      $str = "My favourite color is {color}."; $texttools = $sanitizer->getTextTools(); echo $texttools->populatePlaceholders($str, ['color' => 'red']); // output: My favourite color is red. Usage:
      See the two example Files in the folder /replacements

       
      Methods:
      replacementsTable()
      Renders an overview of all available replacements (see the example in the Module's config file:
       
      Create new Replacements:
      Simply copy the sample file and adopt to your needs.
       
      Download:
      https://gitlab.com/baumrock/RockReplacer
    • By bernhard
      DEPRECATED
      I'm using this module in several projects, but it will likely not see any updates in the future. I'm not happy with it and I'm looking for ways to develop better solutions. RockTabulator was my first try, but I'm also not 100% happy with that. The tabulator library is great, but my module implementation is not. I hope to get a good solution soon, but it will be a lot of work...
      ---
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support (please contact me via PM).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Paul Greinke
      Hi there. I wrote a custom module for one of my projects. In fact I maybe want to use my module in other projects too. In order to be variable and customizable  I need to implement some custom hooks into my module. So I can afterwards hook into the my functions in order to modify them to match the needs of the new project.
      I tried simply defining functions with the '__' prefix. But that did not work. I'm imagining something like the following:
      <?php class MyClass { public function ___someFunction() { // Do something } } // ready.php $this->addHookBefore('MyClass::someFunction', function($event) { // some customization }); Is there a way to accomplish that? 
×
×
  • Create New...