Jump to content

Recommended Posts

would it be possible to incorporate an existing news section of a site to the blog profile?

  • Like 1

Share this post


Link to post
Share on other sites

So i'm a newbie in PW and make my first steps into deep.

so i've tried to translate this great addon to german....so far so good.
 
But the Top Menu Bar in Backend ( Dashboard Posts Categories Tags Authors Settings )

seems to cant get translated...so my question:

did i not get it or are there some strings hard coded in this module?

EDIT: worked the first one out....PW is so easy to learn great stuff... ;)

done a pull request: https://github.com/kongondo/Blog/pulls

Great Admintool

Featurerequests could be like described above:

- publish from/until feature (so you've get a eventcal option with dashboard, too without much effort or have a second addon)

- in Dashboard -> Overview could the Archive view linked to a row below with lists the posts in the clicked month?

- a blog addon that i used in another CMS has widget for "older + newer" topics - it's like "recent posts" but little different (maybe i find the time to contribute this by my self if i was more familiar with PW)

- what's about META tags like description and keywords?

i've seen some "automatic" functions for create them but let them overwrite from the author...

function makemetadescription ($thestring) {

$the_description = stripslashes($thestring);
$the_description = str_replace('"', ' ', $the_description);
$the_description = str_replace("'", ' ', $the_description);
$the_description = str_replace('\'', ' ', $the_description);
if (strlen($the_description) > 160) {
if(preg_match('/.{0,160}(?:[.!?:,])/su', $the_description, $match)) { $the_description = $match[0]; } //thanks to thorn

if (strlen($the_description) > 160) {
$pos = strpos($the_description, " ", 120);
if ($pos > 0) {$the_description = substr($the_description, 0, $pos); }	
}
}
//$the_description = ' '.$the_description;
$the_description = trim(str_replace(' ',' ',$the_description));

return (' '.$the_description);
}

function makemetakeywords ($thestring ) {

$the_keywords = $thestring;
if (strlen($the_keywords) > 100) {
if(preg_match('/.{0,100}(?:[.!?:,])/su', $the_keywords, $match)) { $the_keywords = $match[0]; } //thanks to thorn
if (strlen($the_keywords) > 100) {
$pos = strpos($the_keywords, " ", 100);
if ($pos > 0) {$the_keywords = substr($the_keywords, 0, $pos); }	
}
}	
$bad = array(
'\'', /* / */ '"', /* " */	'<', /* < */	'>', /* > */
'{', /* { */	'}', /* } */	'[', /* [ */	']', /* ] */	'`', /* ` */
'!', /* ! */	'@', /* @ */	'#', /* # */	'$', /* $ */	'%', /* % */
'^', /* ^ */	'&', /* & */	'*', /* * */	'(', /* ( */	')', /* ) */
'=', /* = */	'+', /* + */	'|', /* | */	'/', /* / */	'\\', /* \ */
';', /* ; */	':', /* : */	' ', /* */	'.', /* . */	'?' /* ? */
);
$the_keywords = str_replace($bad, ',', $the_keywords);
$the_keywords = str_replace(',,,',',',$the_keywords);
$the_keywords = str_replace(',,',',',$the_keywords);

return (' '.$the_keywords);
}
  • Like 1

Share this post


Link to post
Share on other sites

Some more Tweaking....

- tags are burned words in SEO maybe buzzwords or something is better use actually?

- tag pages should be noindex,follow per default? (Since newbee where is the best PW practise to setup such things)

Share this post


Link to post
Share on other sites

Kongondo,

Regarding blog_date field. I get the feeling it is designed to be the date/time that the blog post is published, but from what I can see it gets set when the post is first created and doesn't automatically change after that. I might be misunderstanding your use of the field, but I would like to see it change automatically when the post is published and not change after that - maybe even disable user editing of it?

I know we often draft up several posts at a time and publish them later. I don't think we should have to manually adjust this field when publishing the post.

Another thought for you - have you considered integrating this module:

http://modules.processwire.com/modules/schedule-pages/

or the functionality from it into the blog posts tab? This would make WP users feel at home. Thanks for considering.

blog_date field

You are right. It should be about the post publish date. I don't think this will be difficult to implement - I'll just steal and modify the code here by SiNNuT and Soma :D. I'd still like to leave a manual override (i.e. not disable user editing of it); I envisage cases where a post is published 'by mistake' and has to be recalled for later publication. 

Scheduled Pages

I'll have a think about this one. I can see the potential.

Thanks for your ideas!

  • Like 1

Share this post


Link to post
Share on other sites

Currently it looks like the excerpt length is hardcoded to 450 characters - perhaps adding an option for people to set this themselves would be a good idea? In the meantime, for anyone that wants to change this, find the line

Thanks for filing this in GitHub. I currently have this working on my local install. Added a 'blog_excerpt' integer field to the 'blog' template. Will also enable editing via the 'Settings' tab in ProcessBlog. Due to the nature of this module, for existing installs (i.e. if you've already installed ProcessBlog) you will have to manually create the field; The module will not attempt to modify existing fields; the risk of corrupting/loosing your data means it's not worth it :-). I'll post a notice here once I have updated the module, thanks.

Share this post


Link to post
Share on other sites

would it be possible to incorporate an existing news section of a site to the blog profile?

fenton,

Good question. It's something I've been discussing with some people. Currently, the only way to achieve this is to clone the module and modify it (typically paths and selectors) to read your news section pages (i.e. the fields). Obviously, that is not ideal or for everyone. However, Blog is meant for, er blogging. So, another solution is needed. The current idea is to create a separate (but similar) skeleton module that is highly configurable and adaptable to different needs such a news site, etc. At the moment, this is still an idea. There is no ETA yet :-)

Cheers.

  • Like 1

Share this post


Link to post
Share on other sites

So i'm a newbie in PW and make my first steps into deep.

so i've tried to translate this great addon to german....so far so good.

But the Top Menu Bar in Backend ( Dashboard Posts Categories Tags Authors Settings )

seems to cant get translated...so my question:

did i not get it or are there some strings hard coded in this module?

EDIT: worked the first one out....PW is so easy to learn great stuff... ;)

done a pull request: https://github.com/kongondo/Blog/pulls

Great Admintool

Featurerequests could be like described above:

- publish from/until feature (so you've get a eventcal option with dashboard, too without much effort or have a second addon)

- in Dashboard -> Overview could the Archive view linked to a row below with lists the posts in the clicked month?

- a blog addon that i used in another CMS has widget for "older + newer" topics - it's like "recent posts" but little different (maybe i find the time to contribute this by my self if i was more familiar with PW)

- what's about META tags like description and keywords?

i've seen some "automatic" functions for create them but let them overwrite from the author...

mr-fan

First, welcome to PW and the forums! Happy to hear Blog is of some use to you. Thank you for your suggestions

Translatable Strings

Apologies for my oversight! Thanks for the pull request. I'll have a look and update.

Publish from/until feature

See my response to @Adrian above. I'll have to think a bit more about this although it is a good idea I think. I just have to think about how to best implement it.

Archive - linked to row below with list of month's posts

Not sure about this one. The Posts tab already shows the lists of posts sorted by date

Meta tags, etc.

Not sure I follow what you mean?

Tags vs buzzwords

I don't think buzzwords will work :-)

noindex, nofollow

The best way to find stuff on these forums/PW site is to search using Google. E.g. noindex nofollow site:processwire.com

See this example: https://processwire.com/talk/topic/3928-meta-robots-on-individual-pages/?p=38483

Thanks!

Share this post


Link to post
Share on other sites

Apologies. version 1.0.0 of module was installed at /site/templates/Blog/ ...that should be /site/templates/ProcessBlog/ If updating the module within the PW Admin, this will write to this latter path... You will need to manually remove the former folder :-)

Share this post


Link to post
Share on other sites

Thanks for the Link for the robots - it's a thing that i missed until now - and it seems to implement easy like most everything in PW ;)

i will work further - thanks for this great addon.

PW is almost very peferct to my need or rather beeing so flexible to fit it.

Best Regards mr-fan

Share this post


Link to post
Share on other sites

Awesome work! Now, what if i needed to have 10 separate blogs like this on the same site?  >:D

  • Like 1

Share this post


Link to post
Share on other sites

.......Now, what if i needed to have 10 separate blogs like this on the same site?  >:D

Seriously? If yes, out of the box, no. But with some trickery, you can have MarkupBlog output posts from only a particular author, assuming each author has their own blog. I am just thinking out loud here. If this is a feature request, I'd like to have more details but also hear what others think :-)

Glad you like the module. :D

  • Like 2

Share this post


Link to post
Share on other sites

Seriously?

Yes, seriously  :( unfortunately I am working on just such a site right now. It's for a business that has 10 separate locations (pseudo-franchises, which are more or less independent) and they will all need to have their own separate blogs with their own URLs and their own tags, categories and archives. 

So far I've used a method where all the blogs have different templates in PW which all point to the same template file (which is based on Ryan's blog profile) but I've made the template file dynamic so the names of all the fields are built at run-time based on a naming convention. For example: tags-location1-name, tags-location2-name... etc. instead of just having 1 tags field. And all those suffixes are stored in a special hidden field in the root page of each location.

Don't mean to derail this thread, just wanted to point out a situation where more than 1 individual blog is needed and how much work it can take to set up something like that. 

Again, big thanks for your work, it's going to save me a lot of time on many projects!

Share this post


Link to post
Share on other sites

......just wanted to point out a situation where more than 1 individual blog is needed and how much work it can take to set up something like that. 

Yeah, something to think about for the future... :-)

Share this post


Link to post
Share on other sites

Update: Blog version 1.1

Read below before updating.

For new installs, proceed as normal

-------------------------------------

Changelog

1. Added new widget 'Post Author' - @adrian idea, thanks.

- This widget allows you to add a post's author's biography with each post. You can add it before or after a post (or wherever you wish). See example in updated 'blog-post.php'

example: 

$blog = $modules->get('MarkupBlog');
echo $blog->postAuthor();

- The widget can be enabled/disabled in the 'Settings' Tab of ProcessBlog. It is enabled by default

- Updated the CSS to style the widget

Screen

post-894-0-20359800-1401445817_thumb.png

2. Made 'posts truncate length' configurable - @looeee idea, thanks.

- This is for when you want to render a 'post summary' - e.g. as seen on /blog/posts/.

- Was previously hard-coded to 450. Default is now 450 where no value is specified

- Can be configured either on the page /blog/posts/ or 'Settings' Tab of ProcessBlog

UPGRADING

As I have said previously and repeat here (just in case you missed it :D) a module of this kind must not be altering your data if you've already installed it or where there are potential conflicts. 

Therefore, to upgrade, some manual input is required. Once we hit a lock-down on new features, then this requirement will fizzle out...

A. Author Widget

1. This comes with a new template without a template file. 

- Create a template called 'blog-widget-basic'

- Give it a tag 'blog' and a label 'Blog Widget: Basic' //just for consistency with other blog templates

- Add the field 'blog_summary' save. Then within the template (i.e. click on the upward arrow of the field), change the description to 'Widget Description' in the modal that opens up. Save...

- Still on the edit template view, under the 'Family' tab, specify 'No' under 'May pages using this template have children?' and 'Yes' to 'Can this template be used for new pages?' Save...

- Copy over the updated blog.css to /site/templates/css/ (this assumes you haven't made any custom changes to this file!!!)

2. Post Author page

- Under /blog/widgets/ create a new page called 'Post Author' and assign it the the above template ('blog-widget-basic')

- In the 'Widget Description' field enter a description, e.g. 'Renders Post's author biography.' Save...

The Author Widget should then automatically appear under 'Settings' in the Widgets section in ProcessBlog

B. Post Excerpt Length

1. Add Field to Template

- In the template 'blog-posts', add the field 'blog_quantity'. Save. Change the field's description to 'Posts truncate length'. Save

C. Update Blog to version 1.1

In PW, now update the module to version 1.1. This will copy over the new module files (ProcessBlog.module and MarkupBlog.module) and their related files.

Note: installer will not run again! So, don't worry :D

All done; now go write a post about how cool ProcessWire is  :P  O0

  • Like 5

Share this post


Link to post
Share on other sites

Hey kongondo - great improvements.

I have another suggestion for a widget for you :)

On the main posts page, I like having a thumbnail of the first image to the left of the summary text. Of course you could use the first image from the images field, but I think it would be more appropriate to use the first image embedded in the post - domdocument or even a regex does the trick nicely. You could maybe even have a "feature image" field which could be used for this purpose, or perhaps enable tags on the images field and have people enter "feature_thumb" or something like that in the tag field for the image they want to use as the thumbnail - this might be the simplest and most flexible approach and will also require no duplication of images.

Share this post


Link to post
Share on other sites

....I have another suggestion for a widget for you :)

On the main posts page, I like having a thumbnail of the first image to the left of the summary text. Of course you could use the first image from the images field, but I think it would be more appropriate to use the first image embedded in the post - domdocument or even a regex does the trick nicely. You could maybe even have a "feature image" field which could be used for this purpose, or perhaps enable tags on the images field and have people enter "feature_thumb" or something like that in the tag field for the image they want to use as the thumbnail - this might be the simplest and most flexible approach and will also require no duplication of images.

OK, I'll wait for a pull request from you  :P  ;) .....

I'll have a think...but I'll work on the auto-publish-date feature first...

Edit:

Show me an example post please, thanks.

Edited by kongondo

Share this post


Link to post
Share on other sites

Comments on/off?

Been thinking about a new feature. Ability to turn on/off comments both on a per post basis and on a Blog-wide basis. So, if a post has comments turned off, the user gets the usual 'Comments not allowed for this post' or something similar. Additionally, maybe also a feature to turn-off submitting of new comments on a post when approved comments hit a certain number, say '100'. What do you guys think?

Need to think a bit more about how best to implement this... :-)

  • Like 4

Share this post


Link to post
Share on other sites
Show me an example post please, thanks.

This should give you an idea of what I mean:

post-985-0-65264000-1401463010_thumb.png

On another note, I like being able to only display the Recent Posts when viewing a single post. I don't see much value in having it on the blog home page because the recent posts are there already.

As for comments - all those options sound great!

Share this post


Link to post
Share on other sites

Blogwide there is only one option -> ignore blogpagesettings and overwrite this settings but not change it...if one switch back to comments=on the blogpagesettings are already there? Don't know this is to do in the PWWay...

Share this post


Link to post
Share on other sites

Blogwide there is only one option -> ignore blogpagesettings and overwrite this settings but not change it...if one switch back to comments=on the blogpagesettings are already there? Don't know this is to do in the PWWay...

Exactly. so, the logic, in order of ascending precedence (i.e. 3 > 1, etc.) could probably go like this:

1. Comments are ON by default.

2. On each 'post' page (/blog/posts/my-post/), will include a checkbox: 'check to disable comments for this post'. This will ignore #1

3. On some settings page or on the 'posts' page (/blog/posts/) have a checkbox or similar that says: 'disable comments on all posts'. Ignore #1 & #2

So, #3 is 'greatest' and will ignore #1 and #2 but will NOT change their settings; checked boxes (#2) will remain checked and unchecked ones (#1) will remain unchecked but their 'directions' will be superseded by #3 .

#################################  EDIT #################################

Oops warped thinking on precedence above!!! It should be the other way round! See edits below..

So, the logic, in order of ascending precedence (i.e. 3 > 1, etc.) could probably go like this:

1. Comments are enabled by default everywhere.

2. On the 'comments' page (/blog/comments/) have a select that says: 'disable comments on all posts/disable new comments on all posts'. Ignore #1 but respect individual post's settings (#3)

3. On each 'post' page (/blog/posts/my-post/), will include a select: 'disable comments on this post/disable new comments on this post/always enable comments on this post'. This will ignore #1 & 2. This is like a get() in ProcessWire: it is explicit and ignores 'hidden' status.  

So, #3 (individual post setting) is 'greatest' and will ignore #1 and #2.

#################################  END EDIT #################################

Btw, you will notice very soon that there's very little 'do this the PW way' - in many cases, there is no PW way :D The system is so versatile yet powerful you will be amazed... :-)

  • Like 3

Share this post


Link to post
Share on other sites

i will try to learn fast....;) i'm already amazed and i only see the surface! i've to less time to dive into all the sourcecode...

Share this post


Link to post
Share on other sites

Had an oops moment in my post #47 above; edited it :D (sort of a note to self; feel free to ignore  ;)  :P )

Share this post


Link to post
Share on other sites

Fantastic work, kongondo. Your module is much needed for those of us who don't want to spend a lot of time stripping out the markup on Ryan's (equally awesome) blog module.

One question: I notice that blog posts have this url: www.domain/blog/posts/my-post-here

Have you considered any approach which might remove "/posts/" from that URL? My existing blog doesn't have the extra segment and I'd love to keep it that way, if possible.

I've also been thinking I could remove it via htaccess.

  • Like 2

Share this post


Link to post
Share on other sites

..........One question: I notice that blog posts have this url: www.domain/blog/posts/my-post-here

Have you considered any approach which might remove "/posts/" from that URL? My existing blog doesn't have the extra segment and I'd love to keep it that way, if possible.

I've also been thinking I could remove it via htaccess.

Hi FuturShoc. Glad you like the module.

I thought about this a lot, even with the /site/blog/.... URL, where others would prefer /site/my-awesome-post/...but decided to leave it to the user (for now at least...), if they so wish, to manipulate the URL segments... :-)

UPDATE:

Feature now available in Blog version 2

Edited by kongondo

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By gebeer
      I am happy to present my new fieldtype FieldtypeImageFromPage. It is made up of 2 modules:
      Fieldtype Image Reference From Another Page is a Fieldtype that stores a reference to a single image from another page. The image can be selected with the associated Inputfield.
      Inputfield Select Image From Page is an Inputfield to select a single image from images on a predefined page and it's children.
      And there also is a helper module that takes care of cleanup tasks.
      This module evolved out of a discussion about my other Module FieldtypeImagePicker.  It caters for use cases where a set of images is being reused multiple times across a site. With this fieldtype these images can be administered through a chosen page. All images uploaded to that page will be available in the inputfield.
      When to use ?
      Let editors choose an image from a set of images that is being used site-wide. Ideal for images that are being re-used across the site.
      Suited for images that are used on multiple pages throughout the site (e.g. icons).
      Other than the native ProcessWire images field, the images here are not stored per page. Only references to images on another page are stored. This has several advantages:
      one central place to organize images when images change, you only have to update them in one place. All references will be updated, too. (Provided the name of the image that has changed stays the same) Features
      Images can be manipulated like native ProcessWire images (resizing, cropping etc.) Image names are fully searchable through the API Accidental image deletion is prevented. When you want to delete an image from one of the pages that hold your site-wide images, the module searches all pages that use that image. If any page contains a reference to the image you are trying to delete, deletion will be prevented. You will get an error message to help you edit those pages and remove references there before you can finally delete the image. How to install and setup
      Download and install this module like any other modules in ProcessWire Create a page in the page tree that will hold your images. This page's template must have an images field Upload some images to the page you created in step 2 Create a new field. As type choose 'Image Reference From Another Page'. Save the field. In 'Details' Tab of the field choose the page you created in step 2 Click Save button Choose the images field name for the field that holds your images (on page template from step 2) Click Save button again Choose whether you want to include child pages of page from step 2 to supply images Add the field to any template You are now ready to use the field View of the inputfield on the page edit screen:

      View of the field settings

      The module can be installed from this github repo. Some more info in the README there, too.
      In my tests it was fairly stable. After receiving your valued feedback, I will eventually add it to the modules directory.
      My ideas for further improvement:
      - add ajax loading of thumbnails
      Happy to hear your feedback!
       
    • By gebeer
      Although the PW backend is really intuitive, ever so often my clients need some assistance. Be it they are not so tech savvy or they are not working in the backend often.
      For those cases it is nice to make some help videos available to editors. This is what this module does.
      ProcessHelpVideos Module
      A Process module to display help videos for the ProcessWire CMS. It can be used to make help videos (screencasts) available to content editors.
      This module adds a 'Help Videos" section to the ProcessWire backend. The help videos are accessible through an automatically created page in the Admin page tree. You can add your help videos as pages in the page tree. The module adds a hidden page to the page tree that acts as parent page for the help video pages. All necessary fields and templates will be installed automatically. If there are already a CKEditor field and/or a file field for mp4 files installed in the system, the module will use those. Otherwise it will create the necessary fields. Also the necessary templates for the parent help videos page and it's children are created on module install. The module installs a permission process-helpvideos. Every user role that should have access to the help video section, needs this permission. I use the help video approach on quite a few production sites. It is stable so far and well received by site owners/editors. Up until now I installed required fields, templates and pages manually and then added the module. Now I added all this logic to the install method of the module and it should be ready to share.
      The module and further description on how to use it is available on github: https://github.com/gebeer/ProcessHelpVideos
      If you like to give it a try, I am happy to receive your comments/suggestions here.
    • By Robin S
      A module created in response to the topic here:
      Page List Select Multiple Quickly
      Modifies PageListSelectMultiple to allow you to select multiple pages without the tree closing every time you select a page.
      The screencast says it all:

       
      https://github.com/Toutouwai/PageListSelectMultipleQuickly
      https://modules.processwire.com/modules/page-list-select-multiple-quickly/
    • By gebeer
      Hello all,
      sharing my new module FieldtypeImagePicker. It provides a configurable input field for choosing any type of image from a predefined folder.
      The need for it came up because a client had a custom SVG icon set and I wanted the editors to be able to choose an icon in the page editor.
      It can also be used to offer a choice of images that are used site-wide without having to upload them to individual pages.
      There are no image manipulation methods like with the native PW image field.
      Module and full description can be found on github https://github.com/gebeer/FieldtypeImagePicker
      Kudos to @Martijn Geerts. I used his module FieldTypeSelectFile as a base to build upon.
      Here's how the input field looks like in the page editor:

      Hope it can be of use to someone.
      If you like to give it a try, I'm happy to hear your comments or suggestions for improvement. Eventually this will go in the module directory soon, too.
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://github.com/BernhardBaumrock/RockPDF
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
×
×
  • Create New...