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 teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...