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 bernhard
      --- Please use RockFinder3 ---
    • 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 (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...