kongondo

Module: Blog

Recommended Posts

I guess you are using ProcessWire 3.x? Make sure you have the Comments field module installed. Try refreshing (recompiling) modules. 

Share this post


Link to post
Share on other sites

Unfortunately this did not help. FieldtypeComments is installed and Comments are also installed. This is not a problem. I'm looking for the Disqus comments for my ProcessWire website. You can not change that later. Therefore, use a commentary System.

Share this post


Link to post
Share on other sites

OK. Would have loved to get to the bottom of this though. Comments seem to work for some but not for others...

Share this post


Link to post
Share on other sites

Hello,

What version of ProcessWire and what admin theme (Default, Reno, new UIkit 3 one...) are you using?

Isn't there a View tab/link that enables you to (pre)view the post/page even when it's unpublished?
You normally have options on how to open the "view".

Edited by Christophe

Share this post


Link to post
Share on other sites

I'm facing another problem. Posts don't show up on the front-end, but when I login to the admin, I can see them on the fornt-end. Any idea what could be causing this behaviour?

Share this post


Link to post
Share on other sites

 

Some more avanced users will certainly help you.

I've never used it. I've just installed it once (perhaps?) to try/test it.

Just for information:

On 25/05/2014 at 0:13 AM, kongondo said:

Role and Permission

Note that Blog installs the role 'blog-author' and permission 'blog'. These are available to you to control access as you wish. They are not automatically applied to any user. With these, you can can control the finer details of your blog. 

And you perhaps have to give the good permission(s) for guest in the Access tab of the relevant template used by posts (and perhaps also of the template of their parent page).

And/or give a permission(s) related to the blog for the guest role (in the guest role page).

Sorry I'm not able to help more.

NB: in the new Regular profile (module) there is also an example of a blog instance.

  • Like 2

Share this post


Link to post
Share on other sites

I've set the permissions to give access to blog to users and guest. Post show up on front-end only when I'm logged in as Admin.

Share this post


Link to post
Share on other sites

Hi all,

Is anyone using the super ProcessBlog module with PWs multi-language support? I have five languages setup and all pages are running correctly in all languages / falling back to default (English) when no other language is available etc.

That is apart from the main blog page and it's children (the posts). I'm using the standard gateway method for urls (e.g. http://www.mysite.com/fr/blog) and standard language switch code as described here

I should also note I am only running manual input of translated content, no auto translation.

All pages are present in my main menu (no matter what language is selected) apart from 'Blog' which disappears when any language that isn't the default (English) is selected. Also, if you visit the blog page in English the language selector (which shows all languages on all other pages) only shows 'English' as being available. I'm guessing this has something to do with the way the blog is rewriting URLs (in my case to mysite.com/blog/post-title, i.e. the posts are not children of a category) but I am only guessing!

Versions in use are:

PW 3.0.42

ProcessBlog 2.4.0

I've looked at the title field in use for the blog page which is set to 'PageTitleLanguage' as are all other pages.

Anyone have any ideas as this is driving my nuts today! :-)

Thanks in advance,

Geoff.

Share this post


Link to post
Share on other sites
17 hours ago, MaryMatlow said:

I'm facing another problem. Posts don't show up on the front-end, but when I login to the admin, I can see them on the fornt-end. Any idea what could be causing this behaviour?

Okay, this is sorted out. It was the "access" issue with the "blog-post" template. I removed "view and edit" access restriction and it works.

Thanks for your help @christophe

  • Like 1

Share this post


Link to post
Share on other sites
On 08/04/2017 at 11:05 AM, prestoav said:

Hi all,

Is anyone using the super ProcessBlog module with PWs multi-language support? I have five languages setup and all pages are running correctly in all languages / falling back to default (English) when no other language is available etc.

That is apart from the main blog page and it's children (the posts). I'm using the standard gateway method for urls (e.g. http://www.mysite.com/fr/blog) and standard language switch code as described here

I should also note I am only running manual input of translated content, no auto translation.

All pages are present in my main menu (no matter what language is selected) apart from 'Blog' which disappears when any language that isn't the default (English) is selected. Also, if you visit the blog page in English the language selector (which shows all languages on all other pages) only shows 'English' as being available. I'm guessing this has something to do with the way the blog is rewriting URLs (in my case to mysite.com/blog/post-title, i.e. the posts are not children of a category) but I am only guessing!

Versions in use are:

PW 3.0.42

ProcessBlog 2.4.0

I've looked at the title field in use for the blog page which is set to 'PageTitleLanguage' as are all other pages.

Anyone have any ideas as this is driving my nuts today! :-)

Thanks in advance,

Geoff.

 

Just confirmed this behavior is the same with a fresh install of PW (Minimal Profile) and ProcessBlog. Is there likely to ever be a fix to make ProcessBlog compatible with multi-lingual or is there an architectural problem?

Thanks.

Share this post


Link to post
Share on other sites

    I know this is probably embarrassingly simple, but I can't change the CSS for this blog for the life of me.  I'm trying to get the blog to match the look of the default PW templates so I've added:

<link href='//fonts.googleapis.com/css?family=Lusitana:400,700|Quattrocento:400,700' rel='stylesheet' type='text/css' />

to blog-main.inc and I've also changed the navigation section in blog.css as follows:

/* Navigation */
ul#navbar {
    font-size: 2.85em;
    list-style: none;
    padding: 0 0 15px 0;
/*     font-family: 'Shadows Into Light', cursive; */
    font-family: Quattrocento;
}

    Unfortuantely, nothing changes when I reload the page.  When I view the source code, I don't see the changes I've made - it looks like the CSS has been cached somewhere and it's still pulling the old version.  I also see that the CSS has been minified (on the fly?) and I don't know where that's happening, either.

    I just installed everything the other day, so I have the latest versions.
    
    What do I need to do to get my changes to take?
        
Thanks,
Frank

Share this post


Link to post
Share on other sites

Hi @SSC,

Welcome aboard!

I don't use it so I have to ask, Is blog-main.inc the file that contains the HTML <head> section?

Try a force reload (chrome browser) or whichever browser you are using.

Share this post


Link to post
Share on other sites
6 minutes ago, rick said:

I don't use it so I have to ask, Is blog-main.inc the file that contains the HTML <head> section?

Yes it is.

Quote

Try a force reload (chrome browser) or whichever browser you are using.

I've not only tried that, but I've used multiple browsers, so I don't think it's a browser issue.

 

Thanks,

Frank

Share this post


Link to post
Share on other sites

Okay, that eliminates one possible issue.

Next, Have you looked at the network console (dev tools) to see if the google font is loading or gives an error?

Since the font isn't appearing, it sounds like it's not loaded, so the browser reverts to its default font. 

Share this post


Link to post
Share on other sites

The font is loading.  Here's the head section:

<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Blog</title>
<link href='https://fonts.googleapis.com/css?family=Lusitana:400,700|Quattrocento:400,700' rel='stylesheet' type='text/css'/>
<link href='https://fonts.googleapis.com/css?family=Archivo+Narrow:400,400italic,700,700italic' rel='stylesheet' type='text/css'>
<link rel="stylesheet" href="/blog/site/templates/css/pocketgrid.css"/>
<link rel="stylesheet" href="/blog/site/templates/css/blog.css"/>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.0/jquery.min.js"></script>
<script src="/blog/site/templates/scripts/blog.js"></script>
</head>

However, when I view /blog/site/templates/css/blog.css, I still see 

... font-family:'Shadows Into Light',cursive; ...

For some reason, the changed CSS file isn't being grabbed.

I've also deleted all cache and session files, but that didn't help.

Thanks,

Frank

Share this post


Link to post
Share on other sites

I just noticed something.  When I view the cached file /blog/site/assets/cache/FileCompiler/site/modules/MarkupBlog/template-files/blog-main.inc, it does not contain the changes I've made to blog-main.inc, but it should, correct?

Share this post


Link to post
Share on other sites

Yes it should. You can delete the cache and ProcessWire will regenerate it.

  • Like 1

Share this post


Link to post
Share on other sites

Dev tools will show you other issues that may affect what you are seeing. For example, this image shows a css file not loading, which may indicate a typo in the path.

devtools.jpg.a9336a9876d658c6d2789f43b6968216.jpg

While this image shows bootstrap loaded 'after' the google font, which will overwrite the google font definition.

devtools2.jpg.721b8a66a0625a1b4f37e1e659a7053f.jpg

 

  • Like 1

Share this post


Link to post
Share on other sites

Well this is embarrassing.  Turns out the problem was being caused by CloudFlare's cache.  Since I rarely do stuff like this, I never remember to turn that off before I start changing things.  All I can say is that I'm glad it's Friday. >:(

Thanks for your help, Rick.

  • Like 1

Share this post


Link to post
Share on other sites
On 2017-4-13 at 8:48 AM, prestoav said:

Is there likely to ever be a fix to make ProcessBlog compatible with multi-lingual or is there an architectural problem?

I have previously tested Blog in a multi-lingual environment in ProcessWire 2.7 and it worked just fine. I don't know much about multi-lingual environments though. I am also not sure whether this is specific to ProcessWire 3.x. Unfortunately I do not have time to invest in looking into this particular issue. If anyone can come up with a PR I'll gladly consider it.

Share this post


Link to post
Share on other sites

Hi @kongondo,

I'm having a problem with pagination for the blog. The pagination links appear alright, but when I click on page 2 it brings me back to the top of the first page? What could be wrong? Appreciate your help. Thanks.

I'm using ProcessWire 3.0.61 and ProcessBlog 2.4.0

Share this post


Link to post
Share on other sites
On 5/12/2017 at 8:12 PM, MaryMatlow said:

Hi @kongondo,

I'm having a problem with pagination for the blog. The pagination links appear alright, but when I click on page 2 it brings me back to the top of the first page? What could be wrong? Appreciate your help. Thanks.

I'm using ProcessWire 3.0.61 and ProcessBlog 2.4.0

Off the top of my head ...

1. Is pagination enabled on that template?

2.

 

  • Like 3

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 thomasaull
      Some time ago I created a site profile for creation of a REST API with ProcessWire. Since I kept struggeling with updating stuff between different projects which use this, I decided to convert it into a module. It is now ready for testing: https://github.com/thomasaull/RestApi
      Additionally I added a few small features:
      automatic creation of JWT Secret at module install routes can be flagged as auth: false, which makes them publicly accessible even though JWT Auth is activated in module settings To check things out, download and install the module and check the folder /site/api for examples.
      If you find any bugs or can think of improvements, please let me know!
    • By kongondo
      Sites Manager
       
      16 September 2018:
      FOR NOW, PLEASE DO NOT USE THIS MODULE IN A PRODUCTION SITE. A  RECENT ProcessWire UPDATE HAS BROKEN THE MODULE. I AM WORKING ON A FIX.
       
      ################
       
      Sites Manager is a module for ProcessWire that allows Superusers to easily create/install ProcessWire sites on the same serverspace the module is running in. Only Superusers can use the module. You can create both stand-alone and multi-sites.
       
      Single/Stand-alone Sites
      Stand-alone or single-sites are sites that will run in their own document root/directory with their own wire and site folders, .htaccess, index.php, etc. In other words, a normal ProcessWire site.
      Multiple Sites
      Multi-sites are sites that will run off one wire folder (shared amongst two or more sites) each having their own site folder and database. In this regard, it is important to note that Sites Manager is not in itself a multiple sites solution! Rather, it is a utility that helps you create multi-sites to be run using the ProcessWire core multiple sites feature. For more on this core feature, see the official ProcessWire documentation, specifically the solution referred to as Option #1.
      Option #1 approach requires the site admin to initially install ProcessWire in a temporary directory for each new site. The directory then needs to be renamed as site-xxx, where ‘xxx’ is any name you want to use to differentiate the installation from other sites, before it is moved to the webroot. For instance, site-mysite, site-another, site-whatever. In addition, the /wire/index.config.php file must be copied/moved to the webroot. Each time a site is added, the index.config.php has to be edited to add ‘domain’ => ‘site-directory’ key=>value pairs for the site. This process can become a bit tedious. This module aims to automate the whole multi-site site creation process.
      The module is based off the official ProcessWire installer. Creating a site is as simple as completing and submitting a single form! You also have the option to type and paste values or reuse a pre-defined install configuration.
       
      The module will:
      Install a ProcessWire site in your named directory, applying chmod values as specified
      Move the directory to your webroot
      Update/Create a Superuser account as per the submitted form, including setting the desired admin theme and colour
      For multi sites, update sites.json (used by index.config.php to get array of installed sites)
       
      For multi sites, the only difference in relation to the core multi-sites index.config.php is that this file is slightly different from the one that ships with ProcessWire.
      Download from GitHub: Sites Manager (Beta Release)
      Features
      Install unlimited number of sites in one (multi-sites) or independent (single-site) ProcessWire installs. Install by completing a Form, Typing or pasting in configurations or using pre-created install configurations. Choose an Admin Theme to auto-install along with the site installation. For single-sites installation, download, save and reuse ProcessWire versions of your choice. Install and maintain site profiles for reuse to create other sites. Create install configurations to speed up installation tasks. Client and server-side validation of site creation values. Edit uploaded profiles (e.g., replace profile file). Lock installed sites, configurations and profiles to prevent editing. Bulk delete items such as site profiles, installed site directories and/or databases (confirmation required for latter two). View important site details (admin login, chmod, etc). Links to installed sites home and admin pages. Timezones auto-complete/-suggest. Pre-requisites, Installation & Usage
      Please see the documentation.
      Technicalities/Issues
      Only Superusers can use the module.
      ProcessWire 2.7 - 3.x compatible
      Currently using ProcessWire 2.7 installer (install.php)
      For multi-sites, potential race condition when sites.json is being updated on a new site install vs. index.config.php accessing the json file?
      Not tested with sub-directory installs (for instance localhost/pw/my-site-here/)
      Currently not doing the extra/experimental database stuff (database charset and engine)
      Future Possibilities
      Install specified modules along with the ProcessWire install
      Profile previews?
      Credits
      @ryan: for the ProcessWire installer
      @abdus: for the index.config.php reading from JSON idea
      @swampmusic: for the challenge
      Video Demo
      Demo  showing how quick module works on a remote server [YMMV!]. Video shows downloading and processing two versions of ProcessWire (~takes 7 seconds) and installing a single/stand-alone ProcessWire 3 site using the new Admin Theme UI Kit (~2 seconds) on a remote server.
       
      Screens
      1

      2

       
       
    • By Robin S
      Breadcrumb Dropdowns
      Adds dropdown menus of page edit links to the breadcrumbs in Page Edit.

      Installation
      Install the Breadcrumb Dropdowns module. The module requires ProcessWire >= v3.0.83 and AdminThemeUikit.
      There is a checkbox option in the module config that determines if the breadcrumb dropdowns will include pages that the user does not have permission to edit.
      Features/details
      The module adds an additional breadcrumb item at the end for the currently edited page. That's because I think it's more intuitive for the dropdown under each breadcrumb item to show the item's sibling pages rather than the item's child pages. In the dropdown menus the current page and the current page's parents are highlighted in a crimson colour to make it easier to quickly locate them in case you want to edit the next or previous sibling page. Unpublished and hidden pages are indicated in the dropdowns with similar styling to that used in Page List. If the option to include uneditable pages is selected then those pages are indicated by italics with a reduced text opacity and the "not-allowed" cursor is shown on hover. There is a limit of 25 pages per dropdown for performance reasons and to avoid the dropdown becoming unwieldy. If the current user is allowed to add new pages under the parent page an "Add New" link is shown at the bottom of the breadcrumb dropdown. If the currently edited page has children or the user may add children, a caret at the end of the breadcrumbs reveals a dropdown of up to the first 25 children and/or an "Add New" link. Overriding the listed siblings for a page
      If you want to override the siblings that are listed in the dropdowns you can hook the BreadcrumbDropdowns::getSiblingsmethod and change the returned PageArray. For most use cases this won't be necessary.
      Incompatibilities
      This module replaces the AdminThemeUikit::renderBreadcrumbs method so will potentially be incompatible with other modules that hook the same method.
       
      https://modules.processwire.com/modules/breadcrumb-dropdowns/
      https://github.com/Toutouwai/BreadcrumbDropdowns
    • By bernhard
      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
      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 for 60€ per hour (excl vat).
       
      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 Ken Muldrew
      I'm trying to get a short routine to run once per day that will look at some pages and send a reminder email when that customer's subscription (yearly) is about to expire. When I run the code in a template then it works without issue, but inside my lazycron service routine, I get an "Error: Uncaught Error: Call to a member function get() on null" as if the database cannot be found. My autoload module is just the sample HelloWorld module included with ProcessWire, editted to perform this task. The whole of it is included below (I've stripped out the code that generates the email because it never gets past $pages->find):
       
      <?php namespace ProcessWire;
      /**
       * ProcessWire 'LazyCronLoad'  module
       *
       */
      class LazyCronLoad extends WireData implements Module {
          public static function getModuleInfo() {
              return array(
                  'title' => 'LazyCronLoad', 
                  'version' => 1, 
                  'summary' => 'Just loads a lazy cron callback.',
                  'singular' => true, 
                  'autoload' => true, 
                  );
          }
          public function init() {
              // initialize the hook in the AutoLoad module
              $this->addHook('LazyCron::everyDay', $this, 'myHook');
              
          }
          public function myHook(HookEvent $e) {
              // called once per day
              wire('log')->save('user_activities',' lazy cron service routine');
                  $transport_pages = $pages->find("template=aggregate-entry, aggregate_type.title='Transport'");
                  foreach ($transport_pages as $page) {
                      if (($page->purchase_date + 30325800 < time()) && ($page->purchase_date + 30412600 > time())) { // between 351 and 352 days
                          wire('log')->save('user_activities', $page->id . ' email reminder sent');
                          // send email
                  }
              }
          }        
          
      }
      The first wire('log') shows up but the second one doesn't (the purchase_date condition is met (as demonstrated by running the code in a template close in time to when the lazycron routine executes)). The error log gives the Uncaught Error shown above. 
      I think this is a beginner's mistake with something obvious being missed and would be grateful for any assistance in fixing it.