Jump to content

Recommended Posts

  • 3 weeks later...

Thanks Kongondo for this great offer! 

I'm currently experimenting with it, I came to the point where I want to change a little bit in the positioning of the blog.
Like placing the Date underneath the post instead of above. But I can't find where I can change those settings? 

Also, the option to show like 200 words and than the text 'view more'. I want to translate this to dutch, but I can neither find this one hehehe.
Can u help me out?

(Dont know what about this, but when i go to PW admin > blog > settings > I can change whatever I want, but it won't safe. It keeps saying the same text which comes by the installation)
I've tested this in Chrome and Safari, same problem. I' on ProcessWire 3.0.132 © 2019

  • Like 1
Link to post
Share on other sites
On 6/4/2019 at 12:37 PM, Troost said:

Thanks Kongondo for this great offer! 

Glad you like it! :-).

On 6/4/2019 at 12:37 PM, Troost said:

Like placing the Date underneath the post instead of above. But I can't find where I can change those settings? 

You do that by passing $options to renderPosts(). I can only apologise that I've never completed the documentation for this module. Please have a look at the options here, in the method processPostsOptions(). All the options that can be passed to renderPosts() are there. For instance, 'post_date' => 1,// display post's date: 0=off,1=top(below post-headline),2=bottom(in post-foot)

On 6/4/2019 at 12:37 PM, Troost said:

Also, the option to show like 200 words and than the text 'view more'. I want to translate this to dutch, but I can neither find this one hehehe.
Can u help me out?

The string is on this line. Is it not appearing in the translation screen? I've never done translation myself so, I wouldn't know how to help beyond this. If you are still experiencing issues, maybe one of your multilingual members could help out.

On 6/4/2019 at 12:37 PM, Troost said:

(Dont know what about this, but when i go to PW admin > blog > settings > I can change whatever I want, but it won't safe. It keeps saying the same text which comes by the installation)

You caught a bug! Thanks for reporting. I've fixed it in the latest version (2.4.4). I've updated the module in the modules' directory.

  • Thanks 1
Link to post
Share on other sites
  • 4 months later...

Hi @kongondo, I'm having an issue with Jumplinks and I haven't had any luck on that support forum so I thought I would try here since I think the issue might be related to the blog plugin. Can you check my posts here and let me know if you've experienced this behavior?

https://processwire.com/talk/topic/8697-jumplinks/?do=findComment&comment=192151

Link to post
Share on other sites
On 10/17/2019 at 11:56 PM, Ben Sayers said:

Hi @kongondo, I'm having an issue with Jumplinks and I haven't had any luck on that support forum so I thought I would try here since I think the issue might be related to the blog plugin. Can you check my posts here and let me know if you've experienced this behavior?

https://processwire.com/talk/topic/8697-jumplinks/?do=findComment&comment=192151

Hi @Ben Sayers,

Sorry for the late response. I have never used Jumplinks before. I have read the posts you link to but cannot think of any reason why the blog module would be the cause of the issue. In addition, @wbmnfktr seems to have successfully tested blog and Jumplinks, so it must be something else in your install. However, in your post you say:

Quote

removed a bunch of old posts, I wanted to redirect them to the main blog page (domain.com/blog/)

What do you mean by removed? Secondly, what 'blog style' did you use on install?

Link to post
Share on other sites
On 10/22/2019 at 2:18 AM, kongondo said:

What do you mean by removed? Secondly, what 'blog style' did you use on install?

No worries, thanks for getting back to me! To remove the posts, I went to the Blog --> Posts tab in PW, checked the boxes for the posts I wanted to remove, then went to Actions -> Delete. I'm using Blog Style 1. I'm able to redirect any page in the website using Jumplinks unless it has "blog/" in it. 

Edited by Ben Sayers
Additional question for kongondo
Link to post
Share on other sites
On 10/24/2019 at 3:06 PM, Ben Sayers said:

using Blog Style 1

Please confirm this. According to your post here:

it seems your posts are structured as: (domain.com/blog/some-post/). This would make it a Blog Style 2 and not Blog Style 1 which would be structured as: /domain.com/blog/posts/some-post/

Link to post
Share on other sites
On 10/27/2019 at 5:31 AM, kongondo said:

Please confirm this. According to your post... it seems your posts are structured as: (domain.com/blog/some-post/). This would make it a Blog Style 2 and not Blog Style 1 which would be structured as: /domain.com/blog/posts/some-post/

Sorry, my post on the forum should have said domain.com/blog/posts/some-post/ - I am using blog style #1. 

blog-style-1.jpg

Link to post
Share on other sites
  • 1 month later...

Hi @kongondo, I'm loving the work you've done with the blog module allready and am using it to set up a multi language blog. I do have a problem with rendering the blog in the secondary language.

The blog categories and tags are not rendered, I assume this is because they aren't translated yet? 

The blog posts themselves don't appear in the secondary language but still output the content from the primary language.

Do you have any idea what i could change to get the blog to work in my secondary language?

 

Dutch version:

image.thumb.png.9f44f871f5a35e9f0bcfe80f3776469d.png

French version:

image.thumb.png.cf4db587b15eac37347e5ba7dcb043f4.png

Link to post
Share on other sites
On 12/11/2019 at 7:56 PM, brdje said:

I'm loving the work you've done with the blog module allready

Hi @brdje. First, welcome to the forums! I am glad you are finding the blog module useful.

 

On 12/11/2019 at 7:56 PM, brdje said:

I assume this is because they aren't translated yet? 

You are right. A massive oversight on my part! I will work on this as soon as I get a bit of time, which might not be soon, I am afraid.

 

On 12/11/2019 at 7:56 PM, brdje said:

Do you have any idea what i could change to get the blog to work in my secondary language?

Since posts are just pages, you could just use PW API directly to access each blog field and let PW deal with the fetching of the value in the current language. For instance (rough example):

 

$posts = $pages->find("template=blog-post,limit=20");

$out = "";
foreach($posts as $post) {
    $out .= "<h2>{$post->title}</h2>";
    $out .=  $post->blog_body;
    $thumb = $post->blog_images->first()->width(250);
    $out .= "<img src='{$thumb->url}'>";
    $out .= '<hr>';
}

echo $out;

It's not ideal, but it should get you started, meanwhile.

Link to post
Share on other sites
  • 1 month later...

Hello,

I'm using the blog template by @kongondo (thank you!) and I've been going through and creating my website. I've been trying to work this issue out for a day and I haven't gotten far.

I can't figure out how I can sort the months in descending order as these are not pw pages. The years and the posts are shown in descending order, and I want to have the months in descending order too (June, May, April, etc) . How do I do that? I looked at the function for renderarchives and it's unfortunately beyond me at the moment. Thanks for any help on this! 

Regards,

Jonah

Archives

2019

April
    Post #4
    Post #3
    Post #2
    Post #1
May
    Post #4
    Post #3
    Post #2
    Post #1
June
    Post #4
    Post #3
    Post #2
    Post #1

 

Link to post
Share on other sites

Hi @montero4,

Welcome to the forums and ProcessWire. This seemed like a nice feature to add so I have gone ahead and added it as an option to getArchives(). I'll release over the weekend.

 

PS: I have moved your thread to the blog support forum.

  • Like 1
Link to post
Share on other sites

Update: Blog 2.4.5

Changelog

  1. Added new option (see example use below) to MarkupBlog::getArchives() that allows to specify if archive months should be sorted descending (Dec - Jan). Default is ascending (Jan - Dec), thanks to question by @montero4
  2. Fixed bug in template blog-archives.php that caused illegal offset warnings.
Module has been updated in the modules directory.
 
Example usage of new getArchives() option
 
getArchives() now accepts a third parameter as an $options array. If you want archive months to be sorted and rendered in descending order (December - January), you will need to pass this as an option in the $options array and set the value 'descending' to they key 'archives_month_sort_order'. Since this is the third parameter for the method, you will need to pass options for the first and second parameters as well. If you want the default ascending order of months, you don't have to change anything in your code. Just call getArchives() as usual without any parameters.  Otherwise, read on for descending order of months.
 
<?php
$blog = $modules->get("MarkupBlog");
// options: if we want to sort archive months in descending order
$archiveOptions = array('archives_month_sort_order'=>'descending');
// get archives: order months descending
$archives = $blog->getArchives(0, 1, $archiveOptions);
// if you want to render the archives
$content = $blog->renderArchives($archives);// order months descending

Please test and let me know.

Thanks.

 
 
  • Like 4
  • Thanks 1
Link to post
Share on other sites
  • 1 month later...

Hi  @kongondo ,

it's quite a while I'm planning to use your Blog Module. Now I started my first try, installing version 2.4.5 in PW 3.0.148.
I chose Blog style 3 and installed the demo template files.

When in the Blog dashboard I open the Authors page, I get the Error
"Call to a member function size() on boolean"  in ProcessBlog.module:1686.
Line 1686 is this one:

'<img src ="' . $author->blog_images->first->size(75, 75)->url .'" class="blog_author_image">'  :

What's going wrong?
Thank you
ottogal

 

  • Like 1
Link to post
Share on other sites

Hi @ottogal,

Thanks for catching this. I have a feeling there are other similar gotchas! I'll search for and resolve (if need be) these at a later date. For now, please change line #1685 from:

$authorPhoto = !empty($author->blog_images) ?

to:

$authorPhoto = $author->blog_images->count ?

Thanks.

  • Thanks 1
Link to post
Share on other sites
  • 2 months later...

Hi @kongondo

I've just installed your module (version 2.4.5 in PW 3.0.148). Upon installing I did select blog style 1 or 2, and in both cases I keep getting this warnings above the dashboard:

"Warning: Illegal offset type in ..\site\modules\MarkupBlog\ProcessBlog.module on line 916"
"Warning: Illegal offset type in ..\site\modules\MarkupBlog\ProcessBlog.module on line 917"

that refer to these two lines:

$posts->title => array('published' => $qn['blog-post'], 'unpublished' => $qn['unpublished'] ),
$comments->title => array('approved' =>  $numApproved, 'pending' => $numPending, 'spam' => $numSpam ),

How can I remove those warnings? Is there a quick way to fix it?

Thanks.

Link to post
Share on other sites
21 hours ago, lele_ballack said:

How can I remove those warnings? Is there a quick way to fix it?

I am not seeing those errors in my test site. But I do see some code that could be refactored. Please try the following for now:

Replace this (starting from line # 915)

$list = array(
    $posts->title => array('published' => $qn['blog-post'], 'unpublished' => $qn['unpublished'] ),
    $comments->title => array('approved' =>  $numApproved, 'pending' => $numPending, 'spam' => $numSpam ),
    $categories->title . ' & ' . $tags->title => array('categories' => $qn['blog-category'], 'tags' => $qn['blog-tag'] ),
);

 

With this:

$postsTitle = !empty($posts->title) ? $posts->title : "Posts";
$commentsTitle = !empty($comments->title) ? $comments->title : "Comments";
$categoriesTitle = !empty($categories->title) ? $categories->title : "Categories";
$tagsTitle = !empty($tags->title) ? $tags->title : "Tags";

$list = array(
    $postsTitle => array('published' => $qn['blog-post'], 'unpublished' => $qn['unpublished'] ),
    $commentsTitle => array('approved' =>  $numApproved, 'pending' => $numPending, 'spam' => $numSpam ),
    "{$categoriesTitle} & {$tagsTitle}" => array('categories' => $qn['blog-category'], 'tags' => $qn['blog-tag'] ),
);

Please let me know if it helps.

Thanks.

Link to post
Share on other sites

Thanks @kongondo for your quick reply! 

That worked really well and the warnings disappeared! 

Just noted that there is small bug though after implementing the new code: the comments counter appears now in the dashboard (title and icons only, without any real counting)  even though I chose a blog installation with no comments. 

Link to post
Share on other sites
On 6/26/2020 at 9:22 AM, lele_ballack said:

Just noted that there is small bug though after implementing the new code: the comments counter appears now in the dashboard (title and icons only, without any real counting)  even though I chose a blog installation with no comments. 

Hmm. That's very strange. I'll have a look. Thanks for reporting.

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 FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      https://github.com/chrisbennett-Bene/AdminThemeTweaker
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.



       

    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
×
×
  • Create New...