kongondo

Module: Blog

Recommended Posts

1 hour ago, tooth-paste said:

1. Image summary page
My blog index page works but I would like to have the image on the right side. Can I do this with CSS (img.post-featured-image{float:right})?

Yes, that's CSS issue. Try and see if it works ^_^.

1 hour ago, tooth-paste said:

2. blog-post.php 

How can I output the post that is linked to. I mean the page with the full blog-item? I use this code but it does not work.

Are you using the demo template files that come with blog or did you create/or are using a blank blog-post.php? If the latter, then please have a look at the example demo file. It is a bit redundant to have the code you pasted (which is an example code I gave for some other context) within a blog-post page itself (i.e. redundant to use it in blog-post.php which is the template file for a single blog post).

  • Like 1

Share this post


Link to post
Share on other sites

Yes, I meant AND. Rewriting URL as you suggest is way beyond my capability. I guess I'd have to live with it. In any case it's no biggie.

About the categories, sorry about the confusion.  What I meant was the categories that are displayed at the end of each post. Ideally when you click on it it should take you to the pages with the "news" and "blog" template respectively rather than the page with "category" template.  I hope I'm makes sense.

Thanks for your help.

Share this post


Link to post
Share on other sites

Hi. I cannot edit the blog using the dashboard panel, every time I try to save a blog-post (or add a category or edit the blog setting etc) the page re-loads and nothing is saved. This is very strange because it used to work fine. I've tried with both 'blog-author' & 'superuser' roles, checked the logs in PW, check the developer tools on browser, tried with different browsers... I don't see any error message anywhere, I wish I could post more information. On my local machine the blog is still working, on the live server (same files) I have problems. Anyone had this problem before?

PW 2.8.35 - Blog 2.4.0

Share this post


Link to post
Share on other sites
On 17/02/2017 at 4:51 PM, MaryMatlow said:

What I meant was the categories that are displayed at the end of each post. Ideally when you click on it it should take you to the pages with the "news" and "blog" template respectively rather than the page with "category" template.  I hope I'm makes sense.

That's the expected behaviour. When you click on a category, you are taken to its page and are shown a list of all the posts that use that category, i.e. /category/my-category/. I can't remember how you set up, but if your "news" is a category, clicking on a post categorised under "news" should take you to /category/news/ with a list of all posts classified as news items. 

7 hours ago, palacios000 said:

This is very strange because it used to w

Seems something changed in your system? Some autoload module that is affecting save? I have tested and it works fine here. Does the same thing happen if you edit the post page normally? (i.e. not in the Dashboard modal).

Share this post


Link to post
Share on other sites

As you suggested I use our demo templates and alter them to my own needs. It works great. Thank you. Can you help me out with the topNav.

On the blog page with all post there is a topNav with selectable Categories. When you click on a single post, the topNav is replaced with a subNav 'See also' and 'Related categories'. Can I remove the subNav and replace it with the topNav? So I would like to always select Categories in stead of 'Related post'. 

In the template file 'blog-post' I removed the subnav. Is it possible to add the topNav(categories) on a single post?

Share this post


Link to post
Share on other sites

The method rendering those side menus is renderNav(). It takes as a second parameter an array or PageArray. In blog.post (the template file for a single post, which you wish to edit), around lines 20 - 22, you can see it takes the PageArray made up of the current post's categories (blog_categories) as follows:

if(count($page->blog_categories)) $subNav .= $blog->renderNav(__('Related Categories'), $page->blog_categories);

In the main blog page, i.e. the one that uses the template blog.php, around lines 14 - 15, we see the same function taking a different PageArray; one that is made up of ALL the categories as follows:

$categories = $pages->get('template=blog-categories');// this grabs the parent of all category pages
$subNav = $blog->renderNav($categories->title, $categories->children);// we pass its children, a PageArray made up of all categories

So, the latter code (the lines 14 - 15 in blog.php) is what you need to copy to your blog-post.php to achieve your desired result. Please note that in that demo code, there is no limit set to the number of categories that are returned. If you have lot's of categories you will want to place a limit on the children, e.g. $categories->children('limit=50');

Share this post


Link to post
Share on other sites

Preview of new Blog Dashboard UI coming in the next update...

Posts List

new-blog-ui-posts.thumb.png.becafecec27d3f5616477764c032b2ef.png

Quick Post (now in modal)

new-blog-ui-quick-post-with-rte.thumb.png.79f256ed52c307e3fb2fc328e78a1c1c.png

Thoughts? Opposition :)?

Edited by kongondo
  • Like 2

Share this post


Link to post
Share on other sites
On 18/02/2017 at 7:29 PM, kongondo said:

Seems something changed in your system? Some autoload module that is affecting save? I have tested and it works fine here. Does the same thing happen if you edit the post page normally? (i.e. not in the Dashboard modal).

Thanks for the quick reply! Update:

  • I can edit or add pages normally, I have role 'superuser'
  • From the dashboard I can only edit posts, I cannot add new ones.
  • I have re-installed the blog module, with same results
  • I have checked the user permissions, both on the role 'blog-author' & from the blog- templates
  • I've cleared PW cache in /assets/cache
  • probably on the live server, I was never able to add new posts from the dashborad

What else can I check? Thanks a lot for any hint

Share this post


Link to post
Share on other sites

Hello to all,

i'm new to processwire and started with an test installation (3.0.42) with multilanguage support and the blog modul. I have write a test post and if I call it at the frontend I get the following error message:

Recoverable Fatal Error: Argument 1 passed to MarkupBlog::renderComments() must be an instance of CommentArray, instance of ProcessWire\CommentArray given, called in C:\xampp\htdocs\pwire2\site\assets\cache\FileCompiler\site\templates\blog-post.php on line 54 and defined (line 1059 of C:\xampp\htdocs\pwire2\site\assets\cache\FileCompiler\site\modules\ProcessBlog\MarkupBlog.module) 

I've searched the forum but nothing found. Would it be better to use PW 2.8.35 for a new project?

Thanks for your help!

Alex

Share this post


Link to post
Share on other sites
On 20/02/2017 at 9:11 AM, palacios000 said:

What else can I check? Thanks a lot for any hint

Difficult to tell at this point. Could you confirm that the post (meaning the textarea, etc, inputs) are actually sent? JS errors? If it works on your local server but not the live one...that tells us there is some configuration in the live server affecting things. Other than these, I could have look if you are able to grant me temporary access.

On 20/02/2017 at 5:34 PM, al-ex23 said:

i'm new to processwire and started with an test installation (3.0.42) with multilanguage support and the blog modul. I have write a test post and if I call it at the frontend I get the following error message:

Welcome to the forums and ProcessWire @al-ex23. I am not sure whether that's a file-compiler related problem. Does refreshing several times help? 

Share this post


Link to post
Share on other sites

Happy to announce Blog 2.4.1 is now available for testing on the dev branch. Please test and let me know that it works OK, all the way from install to uninstall and everything in between, thanks.

This version is highly refactored, brings in a new cleaner UI (at least I think so), including better sorting of posts/categories/tags, author bios, category description (not sure many know that categories have a field for entering descriptions), etc and one new (frontend) option that enables the control of the 'edit' link that appears for logged in users when viewing a Blog Post. The link can now be placed at the top, bottom or switched off altogether (@thanks to antoiba86 idea).

Here are a couple of screens. I have tested in 2.7.2, 2.8.35 and 3.0.42 and everything seems to work fine. However, further tests are needed before I commit this to master. That's where you come in, thanks.

 

Blog 2.4.1 - 001.png

Blog 2.4.1 - 002.png

Blog 2.4.1 - 003.png

Blog 2.4.1 - 004.png

Blog 2.4.1 - 005.png

Blog 2.4.1 - 006.png

Blog 2.4.1 - 007.png

Blog 2.4.1 - 008.png

Blog 2.4.1 - 009.png

Blog 2.4.1 - 010.png

Blog 2.4.1 - 011.png

Blog 2.4.1 - 012.png

Edited by kongondo
  • Like 7

Share this post


Link to post
Share on other sites

@kongondo Seriously this is an awesome job, I use the blog alot and this looks really clean and 'lit'. Can't wait for the new UiKit however would there be a guide to other devs so their Modules looks clean with the new UI 

  • Like 2

Share this post


Link to post
Share on other sites

Hi @kongondo, I had to reinstall the Blog module as it was giving a problem (it was completely disabled, couldn't perform any action: post, delete etc.). Anyway ,I reinstalled and everything works fine but for the comments. It is giving me this error:

 

Recoverable Fatal Error: Argument 1 passed to MarkupBlog::renderComments() must be an 
instance of CommentArray, instance of ProcessWire\CommentArray given, called 
in /xxx/html/site/templates/blog-post.php on line 53 and 
defined (line 1059 of /xxx/html/site/modules/ProcessBlog/MarkupBlog.module) 

This is the code I'm using on blog_post.php:

 

	$blog = $modules->get("MarkupBlog");
    $blogConfigs = $modules->getModuleConfigData('ProcessBlog');
    $renderComments = $blogConfigs['commentsUse'] == 1 ? $blog->renderComments($page->blog_comments) : '';

    $options = array('post_date_text' => on, 'post_categories'=>0, 'post_comments' => 2, 
	'post_large_image' => 1, 'post_author' => 1);
    $content = $blog->renderPosts($page, false, $options) . $blog->postAuthor() .
	$renderComments . $blog->renderNextPrevPosts($page);//with post author widget
    
    //include the main/common markup
    require_once("blog-main.inc");

 

 

I'm using ProscessBlog 2.4 and Processwire 3.0.53

 

What could be the problem here? Thanks for your help.

 

Share this post


Link to post
Share on other sites

Just an update: This was resolved when I recompiled the modules. 

In trying to fix this I had uninstalled ProcessCommentsManager, but now I can't install it back. It doesn't seem to exist. Is there any other way to manage comments?

Share this post


Link to post
Share on other sites

Hi @MaryMatlow

Glad you got it sorted. That's a core module, so check under core/modules/ in the modules page, specifically a process module called 'Comments'.

  • Like 1

Share this post


Link to post
Share on other sites
On 2017-03-02 at 6:21 PM, kongondo said:

Hi @MaryMatlow

Glad you got it sorted. That's a core module, so check under core/modules/ in the modules page, specifically a process module called 'Comments'.

Done. Thank you.

Share this post


Link to post
Share on other sites

I've moved my site to a other server and getting a fatal error! Please help.

Notice: Undefined variable: class in /var/www/vhosts/website/httpdocs/site/assets/cache/FileCompiler/site/modules/Blog/MarkupBlog.module on line 1443

Fatal error: Class 'DOMDocument' not found in /var/www/vhosts/website/httpdocs/site/assets/cache/FileCompiler/site/modules/Blog/MarkupBlog.module on line 885

Error: Class 'DOMDocument' not found (line 885 of /var/www/vhosts/website/httpdocs/site/modules/Blog/MarkupBlog.module) 

 

Share this post


Link to post
Share on other sites
59 minutes ago, tooth-paste said:

I've moved my site to a other server and getting a fatal error!

 

59 minutes ago, tooth-paste said:

Error: Class 'DOMDocument' not found

Seems your new server does not have the PHP extension DOMDocument installed. Ask your host to install it for you.

  • Like 1

Share this post


Link to post
Share on other sites

Hello Community,

With the module ProcessBlog I have only problems and can not install it right now. Please check this under https://processwire.wpzweinull.ch/blog-9/. There is something missing CSS or the template is not properly installed.

What can it be what has led to this problem? I installed the modules ProcessBlog scratch. Downloaded from the database of the modules, installed, selected the style and then installed the blog with categories and settings.

But something is still quite wrong.

I would be grateful for any tip very.

Thanks in advance.

Share this post


Link to post
Share on other sites
You must assign a template to the page before setting custom field values (title__data) [pageClass=Page, template=]

This error is displayed after installing the blog component. So something really does not happen.

Share this post


Link to post
Share on other sites

@Alex L,

Welcome to the forums.

Please note that for modules that have their own support forums, we do not start other threads but rather post in those support threads. OK, to your question. 

If you want to use Blog's demo template files and styles, it is easiest if you install ProcessWire with a 'blank profile'. What is happening is that the profile you are using (I think it's called 'site-default') is conflicting with Blog's template files. I am in a bit of a rush so cannot explain further.

Share this post


Link to post
Share on other sites

Hello @kongondo

Oh, excuse me. I did not know it. I have now installed a blank page profile and the blog as well. At https://processwire.wpzweinull.ch/blog/ it is now. Unfortunately, there is always the error message "class comment not found". So I will then install Disqus comments.

Maybe you can see it at times, what is with this error. I had the last days from the beginning. Otherwise, the blog is installed correctly.

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
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public:
       
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
       
    • By Soma
      LogMaintenance
      A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large.
      LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis.
      Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime.
      Lines: keeps logs to a certain number of lines 
      Days: keeps the log to a certain number of days
      Bytes: keeps the log to a certain amount of bytes
      Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank.
      Per Log Settings
      There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is:
      logname:[archive]:[lines]:[days]:[bytes] 
      errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines  
      The module can be found on github for you to check out. It's still fresh and I'm currently testing.
      https://github.com/somatonic/LogMaintenance
    • By teppo
      Fieldtype Page IDs is a third party Fieldtype that, simply put, stores Page references as integers (Page IDs).
      This fieldtype was built as a quick and dirty workaround for Page Reference fields' inability handle self-references due to circular reference issues. A project I've been working on for a while now includes a combination of RepeaterMatrix content blocks and tagging/categorization system that would've resulted in a lot of duplicate pages (and plenty of unnecessary manual work for content editors) had I used built-in Page Reference fields, and thus a new Fieldtype felt like the most sensible approach.
      Fieldtype Page IDs was designed to be loosely compatible with Page References in order to make conversions between the two feasible, but it is quite limited feature wise:
      largely due to the fact that stored values are actually just integers with no connection to Pages whatsoever some advanced selectors and related features are not supported, and page values can't be directly accessed configuration settings are limited to the bare essentials (selector string and Inputfield class) only a handful of Inputfields (AsmSelect, Checkboxes, Text) are (currently) supported Anyway, in case you need to store Page IDs (and Page IDs only) and are happy with the limitations mentioned above, feel free to give this Fieldtype a try. It has been working fine for me in one particular project, but hasn't been tested that much, so please tread carefully – and let me know if you run into any issues.
      GitHub repository: https://github.com/teppokoivula/FieldtypePageIDs
      Modules directory: https://modules.processwire.com/modules/fieldtype-page-ids/
    • 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:
      I've updated the module to 0.0.4. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github 🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • By franciccio-ITALIANO
      Hi, in wordpress homepage we can put a list of LAST ARTICLES AND COMMENTS.
      Can I do same thing with processwire?
      If yes, how?
      There is a tutorial?

      Thanks!