Jump to content

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 using ProcessWire 3.0.58 and Blog 2.4.0

I see the "view" tab for regular pages but not for the posts.

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 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...