Peter Knight

Just noticed there's quite a few videos and screenshots in the docs using very old Admin themes. Screenshots should be relatively easy to update once a theme is accepted (default or Reno). Videos are going to be tricker. But as someone who initially looked at PW and then bounced off due to the look of the early admin (bloody designers!) I think these first impressions are vital and should be updated.

Really impressed. For some reason (before you built this) I assumed the Monitor app would be accessed via a private web page. Of course, it would naturally be part of the Admin as you've done. Not sure why I jumped to that conclusion :-/

Yes - good points Martijn. In this case, I am developing for my own skills / curiosity but I'll definitely keep that in mind. I have an earlier post bookmarked too regarding sanitizing entered data etc,

Thanks guys. That gives me a direction at least. Much appreciated.

Hi guys. I want to learn something new but not sure where to get started or what the technique is even called. I have a page inside the PW admin with several fields. I'd like to present this fields (not their values) on the front end of a web page. Populating them (front end) would create a new PW page in the admin with the values etc. I'll start looking at some kind of form hooked up to the PW API but I wondered if fields such as auto complete and page select were possible or would rely on several 3rd party libraries? Just looking for point in right direction as opposed to code etc. thanks.

Ryan - you're the twinkly fairy atop our ProcessWire Christmas tree. But seriously, I wonder if you should include a screen grab from GoogleTrends too? It does a great job of showing the increase in Searches for ProcessWire on Google. BTW, your clarity and openness here just highlights the WTF-fest surrounding another platform I use. Nobody knows the number of the next version, they can't agree on the product name, there's no public (if any) roadmap and it's probably over a year since there was any type of public info. I wish them well but reading great posts like yours on how solid PW is and how bright it's future (and present) is, clarifies for me that banking on PW has been the right decision for my business and clients too. And that's not because the other CMS is headlining at Confusion-Palooza but because PW on its own merits has a bright, long road ahead. You've written too a post which I'll happily send clients to when they ask "well, what is ProcessWire"?

I think a central manager (ProcessWatch ?) is a great idea and something I've needed in the past. My collection of PW sites is growing rapidly and a birds eye view if all of them would be a real bonus as we manage more and more. Are there recent developments with PW3 which allows it to share data with other PW sites? Maybe the time has never been better to have a central PW install with the: 1. Ability to see which version is running and what latest Dev and Stable version is 2. Ability to upgrade , backup database etc 3. See a modules installed and their version. See if a new version is available 4. See the health of a site (some kind of ping or status - live or non responsive) 5. See who is logged in per site 6. See latest changes per site I think all of the above are already available within a PW install via native functions and Module so I wonder how they could be harnessed on a central console.

Hmm, I'm not sure what mean. Possibly I've misunderstood what you're trying to do. Initially I thought you were trying to make a 1-level / linear menu but you may be trying to nest items? Why don't you create a simple mockup of how you want this to look on the front end of your site? I'd have a better idea then. It maybe a case that Somas navigation module might be better if you are building a hierarchy instead of a flat nav menu although I don't think that allows you to cherry pick what items are included.

If it's a page, you can add it regardless of depth.

I'm sure there was a way to manually crop an image within an Images field BEFORE you added it to a page? Am I imagining this? There was a small crop icon on the top right of an image and now it's gone. Possibly it's a result of changing an Images field to CroppableImage but I thought it may have been a bug?

And the most used plugin types are security based. Because you'd need em, right?

Solved with the help of Tom's question in 2012 I adapted it slightly to <?php if ($page->prev->id) { $prevThumb = $page->prev()->Images->first()->getCrop('articlesquare'); echo " <h3>Previous Article</h3> <figure class='uk-overlay'> <img src='{$prevThumb->url}' /> <div class='uk-overlay-panel uk-overlay-chevron-left'></div> </figure> <a href='{$page->prev->url}'>{$page->prev->title}</a> ";} ?>

Hi I have a series of child pages with Next and Back thumbnails under each page. Parent - Child 1 - Child 2 - Child 3 - Child 4 I want Child page 1 to know it's the first page and not try to render a thumbnail. Likewise, I want Child page 4 to know it's the last page etc... My code works when I am not trying to call a thumbnail but as soon as I try to check for the existence of a previous or next page, my check fails. <figure class="uk-overlay"> <?php //get the cropped thumbnail from the previous page $image = $page->prev->Images->first()->getCrop('articlesquare'); // if there is a previous page, show a thumbnail if($page->prev){ echo "<img src='{$image->url}' alt='{$image->description}' class='art-prev' />"; } else { echo "";} ?> <div class="uk-overlay-panel uk-overlay-chevron-left"></div> </figure> <a class="<?=$page->prev->id ? 'previous' : 'no-before'?>" href="<?php echo $page->prev->path; ?>"><?=$page->prev->title?></a> Should I in fact be approaching this differently as the page is first looking for the existence of a cropped thumbnail?

Nice idea. I was looking into something similar today.

There aren't enough Like buttons for this!

isn't the default url domain.com/wp-admin.php In PW I can only setup page urls like this domain.com/wp-admin/

@benbyford I got a little lost in the Docs and found them hard to follow. Eventually I reverted to a Plesk extension which did the hard work for me. Which part are you stuck on? I found that the default PW .htaccess was preventing the installation of the extension and had to temporarily rename it.

I have HootSuite running for social media management. One thing I like to do is have separate streams running for various CMS I have an interest in. This means I can quickly see all posts mentioning CMS A, CMS B, CMS C etc in a dedicated stream. Makes it easy to follow community topics and product developments etc. But it also makes it easy to gauge social media chatter in relation to a CMS. One thing I've always noticed is how few mentions and tweets PW gets compared to other CMS. IMHO we have a very active and enthusiastic community (as evident from the forums) but a relatively quiet community when it comes to Twitter and Facebook. I'm guilty of this myself but the same thing occurs to me every time I see those three social media streams lined up side by side. Why is it that users of CMS B and CMS A are so vocal on twitter, google plus etc and quick to promote their CMS when PW gets a mention or re-tweet only every second of third day? Incidentally, the 2 other CMS I follow are not huge platforms where you'd naturally expect thousands of tweets a day in comparison to ProcessWire. Anyway, the above occurred to me again after reading Ryan's roadmap post where there was specific mention of This was followed by mention of : curiously there was no mention of social media. Is there an unintentional prejudice against Twitter, GooglePlus and Facebook etc that we're not aware of? Ok, it's an odd question but I thought it'd be worth a check. ProcessWire is growing in userbase, the forums are attracting new members weekly, the CMS itself is a work of art, we have wonderful blog updates on a weekly basis and we have Teppo's PW Weekly too. That energy and excitement seems to ripple out so far and then stop when it reaches an invisible social media force field...

This post has had an inexplicable surge of Likes over the past few weeks so there seems to be quite a bit of interest in this 7 months later. I've been unable to follow these concepts up with the time they deserve but those interested in an mage field tidy up can see Toms own beautiful work mentioned on the Dec 18 blog post. Furthermore, Ryan mentioned in today's Roadmap blog post that these (Tom's) designs are already being worked on by LostKobrakai. Exciting stuff!

Never used the delayed output method. Wondering if it's the best method to start with or does it increase the learning curve. Welcome to PW

Yippeee. I did it See last line of this code. <?php $articles = $pages->find("template=articles-post"); //find all posts based on this template foreach ($articles as $article){ // these are this $audience = $article->articles_tag_audience; echo " <div class='small-12 medium-6 large-4 columns masonary-brick'> <div class='article-wrapper {$audience->implode(" ", "title")}'>

Thanks - will try. At the moment I don't need to (don't know how to) sanitize page titles because they'll always be 1 word titles determined by me. But I like the idea.

Hi I'm trying to inject a list of tags (page titles) into a DIV so that this: <div class ="article-wrapper"> becomes <div class ="article-wrapper tag01 tag 02 tag 03"> It seems very simple but it's failing to output and not throwing any warnings. It's the variable on line 4 called audience that should be scooping up my articles_tag_audience page titles <?php $articles = $pages->find("template=articles-post"); //find all posts based on this template foreach ($articles as $article){ // these are this $audience = $article->articles_tag_audience; echo " <div class='small-12 medium-6 large-4 columns masonary-brick'> <div class='article-wrapper {$audience->title} '> etc... I've also tried <div class='article-wrapper . {$audience->title} .'> which has worked on occasion. Oddly, the following is used (and works) further into my code block { echo $audience->implode(", ", "<a href='{url}'>{title}</a>"); } so I know the page titles exist.

Hey @nico I hadn't (yet) as I thought it was me overlooking something. Will do soon. Thanks

Merry Christmas everyone.