Peter Knight

Are there any plans to introduce custom icons within the tree? Either based on template (config setting?) or on a page by page basis hooked up to a font awesome library etc. For example, this admin theme has a page icon beside each page In general, is this best handled by some custom CSS or would a module be a better approach.

Looks like a broken link or they've removed the post.

Thanks everyone for sharing their stories. Much appreciated and aligns with some of my own experiences. Anyone else?

Most Marketing people I meet have heard of WordPress. It seems I'm repeatedly being asked if I "do wordpress?" when I meet new clients and start talking about content management. Without knowing exactly why their project would be better suited to a more accomplished CMS, most marketing people simply reach for WordPress because "thats what everyone uses right?". It's a challenge we all probably face. In 2015 I'm trying to strengthen my reasons for clients to be more "open" with their CMS choice and at least consider other options. With that in mind, I am wondering how many members here are ex WordPress? I'm trying to get a rough ideas of numbers and some brief stories too. If you have a moment and you came to PW from WP, could you write a few lines about: What made you leave WordPress in general How you discovered PW What you like about PW Any client feedback you've had where a client too moved from WP to PW If you'd prefer to private message me about this, please do.Just to be clear, I'm not looking for a general WP bash here or to create some kind of flame war.

Happy new year back at you, Ivan and everyone else. Hope 2015 is a great one professionally AND personally. Nice to see pics of peoples neighborhoods too

@stikki. What had you been using prior to PW? And welcome to the forums

Peter - this was one of my questions too before I started using PW. Luckily PW handles this natively in a very cool way via pagination as @Mats mentioned. There's a few other nice touches which PW features: The search in PW is lightning fast and allows you to jump to any page within seconds. Even if that page is buried within container pages etc, it's a quick operation. PW has a Recent (Pages) shortcut under the Pages tab which is another great way to access recent pages within a few clicks. Finally, there's a paid Extra called ListerPro which allows you to save views of certain pages. It's a good question but not anything you need to be worried about. I think the PW demo of the fictional SkyScrapers site (see link on PW site) holds some bunches of pages within the paginated format. Worth a quick look.

Not sad at all. A whiz in the accoustics and video department though

waiting on @blad or @josss to make a remix called "I'm dreaming of a wire Christmas".

Merry Christmas too, everyone.

Hi Josephic Welcome to the Forums. Would you be happy to have Top Menu link to the first child? Google ProcessWire First Child Redirect

Well explained. It's really important when you're learning a new system to be completely comfortable with the terminology. If the words used to describe something doesn't gel with you, then you're not going to absorb the concept. Reminds me many years ago of trying to learn expression engine when everything in the tutorial book (and Expression Engine) was called a blog. I didn't get it (at the time) until EE 2 came out and their internal terminology changed. So these days, to counter getting hung up on a keyword or label which I find confusing, I will treat a word as an anagram instead. IE Instead of thinking "its a page", imagine it's a P.A.G.E and make up your own meaning for this such as Part of Anything Going to be Edited Pod for All your Generated Entries Place Already Great for Expansion I'm sure there's better possibilities but it may help. Or it may make things worse :-/

Can you point me in the right direction for mirroring a list of pages by say, archive (month) or authors or categories. For example, the Archives page might have: December 2014 Post 1 Title Post 2 Title November 2013 Post 1 Title Post 2 Title For example, the Categories page might have: Category A Post 1 Title Post 2 Title Category B Post 1 Title Post 2 Title In MarkupBlog Module, you're using this. is it less verbose if it's done with native PW methods? public function renderArchives(Array $years, Array $options = null) { $out = ''; //default options for archives $defaultOptions = array( 'archives_posts_text' =>$this->_('post,posts'),//come in the format 'singular,plural' for e.g. October 5 'posts' 'archives_month_view_all_text' => $this->_('View All'),//'view all' that month's archives if limit set on amount to list ); //merge user options with default archives options if($options != null && is_array($options)) $options = array_merge($defaultOptions, $options); else $options = $defaultOptions; list($singular, $plural) = explode(',', $options['archives_posts_text']);//come in the format 'singular,plural' $post = '%d ' . $singular; $posts = '%d ' . $plural; foreach($years as $year=>$y) { $year = $y['name']; $total = $y['total']; $months = $y['months'];//this is an array $url = $y['url']; $out .= "<div class='archive'> <h3><a href='$url'>$year</a></h3> <span class='num-posts'>" . sprintf(_n($post, $posts, $total), $total) . "</span>"; $out .= "<ul class='posts-group'>"; foreach($months as $monthNum => $month){ $out .= "<li><a href='" . $month['url'] . "'>" . $month['name'] . "</a>"; $out .= "<span class='num-posts'>" . sprintf(_n($post, $posts, $month['total']), $month['total']) . "</span>"; if(count($month['posts'])) {//posts will be empty if $blog->archives() call specified 0 for limit; $out .= "<ul>"; foreach($month['posts'] as $item){ $out .= "<li><a href='$item->url'>$item->title</a></li>"; } if($month['total'] > count($month['posts'])){ $out .= "<li><a class='more' href='" . $month['url'] . "'>" . $options['archives_month_view_all_text'] . "</a></li>"; } $out .= "</ul>"; } $out .= "</li>"; }//end foreach $months as $monthNum $out .= "</ul></div>"; }//end foreach $years as $year return $out; }

Think it depends on the designer/developer. I like to have a summary on blog-posts at least as sometimes you wish to keep the title short but then have a longer summary. Originally, I did that for SEO reasons too.

I've been looking at creating my own templates and test pages and adding some much more lo-fi / basic code. As Kongondo says, the templates provided are just examples and you could output any markup you wish by making your own templates. For example, if you wish to create your own blog-post.php template, you can make a template called blog-post-custom.php etc and manually call a few fields. Here's the body of an extremley basic blog post template. It relies less on variables within other files and includes. <!-- Get the title in a H3 tag--> <h3><?php echo $page->title; ?></h3> <!-- Get the body --> <?php echo $page->blog_body; ?> <!-- Get the comments --> <?php echo $page->blog_comments->render(); ?> <!-- Get the comment form --> <?php echo $page->blog_comments->renderForm(); ?> Likely it bypasses much Kongondos genius but this would actually suffice for my requirements. I'm not sure how I would grab the number of comments this page has but I'll figure it out.

I'm definitely missing some key logic here. If I look at my current blog-post.php template, the entire contents of that template are <?php /** * Post template * Demo template file populated with MarkupBlog output and additional custom code for a Blog Post * */ //CALL THE MODULE - MarkupBlog $blog = $modules->get("MarkupBlog"); //subnav $subNav = ''; //subnav: get date info for creating link to archives page in subnav $date = $page->getUnformatted('blog_date'); $year = date('Y', $date); $month = date('n', $date); //subnav: if there are categories and/or tags, then make a separate nav for them if(count($page->blog_categories)) $subNav .= $blog->renderNav(__('Related Categories'), $page->blog_categories); if(count($page->blog_tags)) $subNav .= $blog->renderNav(__('Related Tags'), $page->blog_tags); //subnav: contains authors, archives and categories links $authorURL = $pages->get('template=blog-authors')->url; $archivesURL = $pages->get('template=blog-archives')->url; $subNavItems = array( $authorURL . $page->createdUser->name . "/" => $page->createdUser->get('title|name'), $archivesURL . $year . "/" . $month . "/" => strftime('%B %Y', $date) ); $subNav .= $blog->renderNav(__('See Also'), $subNavItems); //main content //render a single full post including title, comments, comment form + next/prev posts links, etc //$blog->postAuthor(): if available, add 'post author widget' at the end (or at the top if desired) of each post // $content = $blog->renderPosts($page) . $blog->renderComments($page->blog_comments) . $blog->renderNextPrevPosts($page);//without post author /* for this demo, renderComments() has to adapt to whether blog commenting feature was installed or not whilst remaining blog structure/style-agnostic in your own blog install, you would know if you enabled the feature so there would be no need for such a check in addition, our 'check' code is not code you would normally use in a template file. we use such code here to be both foolproof that the commenting feature is installed and blog structure-agnostic */ #not foolproof; user could have post-installed custom commenting feature (e.g. Disqus) with a similar field blog_comments //$renderComments = $page->template->hasField('blog_comments') ? $blog->renderComments($page->blog_comments) : ''; $blogConfigs = $modules->getModuleConfigData('ProcessBlog'); $renderComments = $blogConfigs['commentsUse'] == 1 ? $blog->renderComments($page->blog_comments) : ''; $content = $blog->renderPosts($page) . $blog->postAuthor() . $renderComments . $blog->renderNextPrevPosts($page);//with post author widget //include the main/common markup require_once("blog-main.inc"); I can see towards the end that Kongondo has a content variable and is outouts Page Author Comments Next / Previous links I guess the black hole for me is - where is the html markup which wraps around these? it's not in blog-post.php and we're not supposed to touch blog.module. Perhaps I'm approaching this with my old MODX mindset and the Articles school of templating where each part of the blog (posts, comments, Tags) had their own mni template with html.

Thanks man. Noted about the menus. Thats what the Christmas break is for, right?

Hu guys I'm delighted to say that my new site is powered by Process Wire. Or rather, "Priceless Wine" and "Princess Wine" as my iPhone mistakenly predictive texts the name. There is also a page on ProcessWire in the CMS section which I'd love your feedback on. Currently I don't think it truly communicates PWs best features for Editors but it's a good start. Only almost finished? The site isn't 100% complete so consider this a "soft launch". Once complete, it'll replace my existing edenweb.ie site which wasn't being updated or developed as much as it should. - - - - - - - - - - - - - - - - - - - - - - - - - - - Background - Why ProcessWire pt 1. A few months back a key client who uses up approx 3 days of my week (for over 3 years) announced a pause on their web and marketing activities for various internal corporate reasons. This happened quite suddenly and obviously that left me with half my week "open" and needing to be filled. It also meant that I would be looking for new work and approaching prospects with a site which was approx 3 years out of date, under developed and didn't really communicate my latest skills or work. Not ideal! - I rapidly needed something live. But more importantly, I needed something better. I needed something built on a CMS which would allow me to rapidly publish content and accelerate future ideas and development. In short, my current CMS is/was great but I was tired of working around default field sets and presumptions it made about my content (amongst other reasons). With ProcessWire, the ability to have a page with just two fields (if I want) is remarkably underestimated. It means I can customise field layouts appropriate to my content. Even better - it means I can customise field layouts appropriate to my clients content and I choose my CMS on their requirements. Anyway, I made the decision to take a deep breath, take a few weeks to enjoy the extra unexpected free time and to rebuild the site in PW. My business will be 15 years old this January and I thought I'd mark the new year with a new domain, new business name and a new CMS. Here's to new beginnings! - - - - - - - - - - - - - - - - - - - - - - - - - - - Under the hood At the time of writing, the site is running 2.5.10 dev. There's not a huge amount of Modules running in the background. Where I've used a Module, it's been to accentuate back-end functionality rather than the front end. Config allows me to make setting changes directly within the admin. Its a great Module and saves me editing any config files and manually FTP'ing. Lister Pro gives me an easy way to manage the "studio updates". Hanna Code allows me to work with some of the tricker layouts such as the page on PW Forms is used for the Contact Form and I'm using direct embed with some jQuery and CSS to strip out some unwanted formatting. ProCache is running in the background to speed things up. Thats more out of professional curiosity right now Vs any focuseed attention on site speed. AIOM was running recentlyto minify all my style sheets and JS but I pulled it recently. might revisit. Blog module is running the er, blog! I've some work to do there in terms of content layout etc but it's a wonderful piece of work. RenoTheme is keeping everything lovely in the admin Upgrades is a real life saver and allows me to update the whole CMS in a few clicks MarkupSimpleNavigation is powering the menus. Regarding the actual PHP used in templates, I doubt there's anything there of interest to you seasoned PHP guys. I've achieved 99% of the site using simple foreach loops and PW selectors. - - - - - - - - - - - - - - - - - - - - - - - - - - - Background - Why ProcessWire pt 2. When I first heard of PW, I was very content with my current CMS so I had a brief look around the site, read some blog posts but ultimately moved on. It looked interesting but I didn't really have a need to investigate further. Fast forward a few years and realising I need to expand my CMS toolset a bit, I had a better look at PW and downloaded it. I really liked *some* elements and appreciated how I could determine the field layout. You see where this is going? Interest increasing! But honestly? I couldn't imagine putting my clients on front of PW with the theme it had (at the time) and TinyMCE as the default editor. It looked real clunky and I wasn't sure I wanted another CMS with the tree representing pages. Somewhat trivial and shallow reasons not to use something but there we go. I'm a designer and I also have to think about my clients experiences too. But I kept an eye on PW and in the background, a few things were happening which were interesting. Communication from Ryan was frequent, open and transparent Planned updates were being released on or before schedule Unplanned updates were often released on or before I realised I even needed them I discovered TinyMCE could be swappable for CK editor and I could use alternative admin themes I discovered a few Modules for listing pages via DataTables as opposed to tree mode Not really sure of the timeline here but this is from mid 2013 onwards btw. The crazy things is from that point onwards, it seemed increasingly impossible to ignore PW. Every few months there was an amazing leap in either the core features or some brilliant module I hoped for was published. EG: I was looking for a way to decrease the time it takes to publish a page in the right place with the right template and the Add New button appeared I was looking for a way to represent pages in a List rather than a tree and ListerPro was announed Hoping for a better way to upgrade PW and the Update module was released Needing a proper blog with categories and the Blog module was there Looking for a better admin UI and RenoTheme came along Needed more flexible field layouts in a matrix and ProFields released Looking for a way to store chunks of html/php etc and Hanna Code was released Ok, that sounds like an Arethra Franklin song about PW but you get the idea! Seriously, it got to the point where I was either silently (or via the Forums) hoping for a particular feature and Ryan would already be working on it or would just release it having finished it. And it was always done in a much more elegant, scalable and powerful way than I imagined or hoped. Just last month I wrote a forum post highlighting a wish for an admin-based settings module. Thinking "nah, there I go complicating things again. Make do with the config.php file" I deleted it. Literally the next day, the Config module was released. It's spooky! Anyway, I've rambled on a bit. But to sum up - I try to redo my site every few years in a different framework and platform. I can see the front-end framework changing in future but I think EdenStudios has found a good, permanent home in PW. PW and Ryan are doing everything right. It's not the only great CMS but it's a damn fine CMS in great hands supported by a great community.

I love the Telecrapper. Some guy hooked his landline up to a computer which could recognise incoming cold calls by their number. His computer would then kick in with a series of random conversations he'd pre-recorded. Here's a recording http://www.ebaumsworld.com/flash/play/464574/ Here's the guys homepage http://myplace.frontier.com/~pumamanor/ At the end of that page theres a few great audio files although the sound quality isn't great.

I might jump in here too and ask the same thing. Hopefully we're asking the same question. Currently, my /blog/posts/ page lists all my posts in the structure as follows Post Title Posted by Author Name. Date and Time Post summary with ellipses at approx 50 words If we want to change this to add the contents of a field such as Post Title Post_Summary field Posted by Author Name. Date and Time Post summary with ellipses at approx 50 words would we need to edit the file called MarkupBlog.module ? And if so, how is that not overwritten when we perform an update to the Blog module?

I have the same issue with 2.5.10 dev even when I remove the old session files. I've just moved the site from my local environment to the live server and am getting the same error Unrecognized HTTP host: 'domain.me' - Please update your $config->httpHosts setting in... domain.me is just for illustration but you get the idea. This is my config $config->httpHosts = array('domain.me','www.domain.me' );

That's interesting. I do it the other way around as to me, the homeage consists of contents from deeper within the site.

Have I got this right? You have a portfolio section in PW. It consists of several Projects and each project is a Page. Projects - project a - project b - project c On each Project field, you have the followign fields Title Image Tag Body etc You then want to pull 1 or more projects onto the homepage and display just the contents of these fields Title Image Tag

Thanks so much. Great to read how it was approached and implemented. The photography of the plants is largely very good. Was that something you had a part in or was there a library you chose from?

I guess both. Just a brief description of what going on in the background in terms of PW, PHP and then the JS. Are the zones and origins etc tags in PW and how you are pulling them onto a web page and then displaying results?