kongondo

@Gazley - I'll delete the other thread then....

You read my mind...was gonna do that but got lazy and decided to do it later

Changed the <hr>s and the the h3 a on the tutorials page. Hope works OK now.

Yes...I realised that afterwards...and they don't look good in the 'green' so going with a lighter colour there - one of my browns or greys...Same with the tutorials page - it is too green for me!

Gone with the green for now

Thx.You mean this one #79B803? colour (or you mean my original website design, the green one! I got tired of that lol) Thanks Teppo - let me revert and see... Ta Thx Soma. Cool one. I'll try it. I was playing at Adobe Kuler but got tired... Thanks Reems

Thanks guys - would this colour work? #51BCD8. Thanks Or maybe this colour? Bright red maybe - design is not my forte clearly ...all suggestions will be considered, thanks.

@cory_dobson, welcome to PW and the forums . Glad you sorted it out. For your other issue, see this troubleshooting guide: http://processwire.com/docs/tutorials/troubleshooting-guide/ It's probably an .htaccess issue.

Guys there was this comment on reddit re my links' colour - that the blue is too light on a white background. Is that your experience as well?

specify each sort separately, e.g. $pages->get('/mypage/')->children('sort=-date, sort=created'); That will first sort by 'date' then by 'created' It's all documented here: http://processwire.com/api/selectors/#sort

One more - a video: http://processwire.com/videos/page-fieldtype/

ProcessWire module upgrades only update the module files...in Blog's case the following files will be overwritten ProcessBlog.module MarkupBlog.module ProcessBlog.js ProcessBlogInstall.inc (this is only ever run once; on first install) ProcessBlog.css README.md LICENSE.txt Nothing is installed. Nothing in your /site/templates/ will be touched so your Template Files, etc. WILL NOT be overwritten . If, on the other hand, you modified the above module files.....

Version bumped to 1.2.2 Main changes are to renderComments() [full documentation here]Added a 4th Array $options argument. In this array you can customise the texts describing the various comments' status such as: when there are no comments - 'Be the first to comment and win and iPad! [kidding!]'; when comments closed - 'Sorry buddy. Next time come earlier ', etc. No, these are not the defaults . The defaults are more sensible and will be used if you don't specify any of your your own. Also, using $options you can require users to login before posting a comment. Of course, you deal with the logging in bit. Blog only checks if user is logged in. Example code $options = array( 'comments_closed' => 'Sorry. Comments are now closed.',//message when comments closed 'comments_empty' => 'No comments found.',//message when there are no comments for post 'comments_login' => 'Log in first to comment.',//message when comment form hidden until user logs in 'comments_login_required' => true,//require user to log in before they can comment. Default is false ); //we call MarkupBlog $blog = $modules->get("MarkupBlog"); echo $blog->renderComments($page->blog_comments, null, $options);

Hi Wanze, Tried on local install. Getting cannot fetch token error Ideas? Thanks. PW 2.4.15 (dev) Edit: Working fine on live server. Thanks!

Read about the new way of installing CKE plugins over here: http://www.flamingruby.com/blog/processwire-weekly-13/#1-2 and more here http://www.flamingruby.com/blog/processwire-weekly-14/#1-4 There's a forum post that I can't find now....

@mr-fan - you read my mind! I had prev/next navigation but removed it . I'll put it back

Strange....could this be your problem? https://processwire.com/talk/topic/1610-navigation-outputting-even-hidden-pages/ TL:DR = updating a wrong site hence not seeing changes? i.e. have both local and live site admins open

Blog documentation up on my website. Focused on MarkupBlog. Decided to do them as PW lessons (hehe - kill 'em with one stone!)...99% done - just have to do some example Blogs. Thanks for being patient! <btw>Next lessons up - 'ProcessWire modules'. </btw>

Post #2000! Better be good! Better be big!! Thanks for waiting ...what? It's only been 1 year . Finally! Some tutorials are up! OK, for now, it is my Blog module's documentation. Hey, that's not cheating! Don't laugh . Meanwhile, I also refreshed my website (how can you refresh an empty house you say? hehe - but it now has content. Nuh, for real, it has content). Toned down on the narcissism as well. Updated first post. Next lessons by great public demand - "Process Wire Modules!" Cheers/k

Is 2.5 the greatest PW to date or what!?! Great additions Ryan!

@PWired, Unfortunately currently you can't do that without breaking links/paths in both ProcessBlog and MarkupBlog. You'd have to hack the module to change affected paths. In Blog 2.0 that I talked about in post #104, the plan is that you will be able to install your Blog anywhere in your site structure/tree. A similar question was asked in post #50. You might want to use url segments..to achieve what you want.. UPDATE: Feature now available in Blog version 2

Moved this here to dev talk sub-forum rather than pub

Were you developing on the production site then? Not locally?

Mod note: Moved this thread here from the 'Tutorials Forum'

Have a look here https://processwire.com/talk/topic/5594-page-1322-is-not-valid-for-some-page-name/ Edit: Beaten again! Scores 2- 1 to Adrian