Leaderboard

I can only concur that this has been a great year. It was nearly impossible not to get infected by the momentum of PW's development. Love (that's an understatement) the JS $pages API plan, and the pages export/import function could even be a solid base for native staging support, just by hooking into the proper PW actions and filling a staging actions table. You're absolutely right, @apeisa, PW is much more than just a brilliant website platform. Our intranet site really does some "heavy lifting", consolidating information from the ERP system, the DMS, personnel and operational time keeping, financial accounting and a few proprietary databases. That way, it also serves as the middleware for a big, distributed test run database. Like Sense, it drives a few chained workflows, e.g. for bridging the feedback gap between dunning proposals and our sales managers. All our intra-company course scheduling/booking runs on PW too, including supervisor approval, and it was surprisingly easy to implement. HR was over the moon with PW's ease of use. For 2017, we're planning a site that provides our customers with all the publicly available documentation for the machines and plant parts we sold them, requiring just a QR code scan on their side. Setting up a working (UIKit styled, multilingual) prototype only took me a few hours and really impressed our sales guys If 2017 is going to be anything like this year, it's going to be a blast. Thank you @ryan! A happy, healthy and inventive new year to everyone!

Great blog post Ryan, thank you! Great year behind and even better coming! What comes weekly news, I think maybe @teppo and PW Weekly could report interesting new stuff from dev branch - instead of full blog post by @ryan each week? Also I think what would really help PW as a community project is that modularity would be more easily seen from code repositories also. I mean separation of /wire/ from rest of the stuff, keeping admin as own project and making several core modules as their own projects (although they could be "essentials" that would always be installed with ProcessWIre). What comes to Avoine, I hope I found time to write case story about how we use ProcessWire as backend solution to our member register platform Avoine Sense. Sense was released early 2016 and it already hosts about 10 member registers that together hold about 150 000 members. Feature-wise Sense already has newsletters, custom reporting tool, invoicing, model based templates/fields, background jobs, client specific procedures build by chaining actions (ie. create excel, connect ftp, deliver file and finally send sms to admin), full read/write REST API with Oauth2 authentication, mobile application, embeddable login/edit forms etc... ProcessWire has been amazing platform for our application development (currently we have 4-5 developers working on it). I strongly encourage that you all consider ProcessWire as a viable alternative for serious application development also. It is perfect platform for building dynamic websites, but it is also pretty brilliant platform for application development!

Ryan, I can only agree with you - 2016 has been a great year for ProcessWire. Ever since I began working with it, I've been excited at almost every weekly update, and the system is growing to be more and more mature every step of the way, without losing sight of the ProcessWire philosophy. For next year, I'm most excited for the following: new admin theme (the idea sounds really good); image/photo tools upgrades; new website; import/export tools; and CKEditor image upgrades. In terms of the schedule-change for updates, I do think you're on the right track. However, I can only imagine that the weekly activity on the GH repo would not reduce excessively, and so perhaps someone who's lingers around the repo often enough could write brief posts for the blog, discussing various fixes, patches, and small feature-releases. I'm not sure what your plans are for the blog on the new website (which I'm most excited about, as you could well-imagine), but perhaps it can be split into feature and non-feature posts, the former of which would be written by you and authors who do case-studies on specific things, like Benjamin and a few others have done in the past when there was no weekly update from you. From my side, I think this will assist in growing our already-thriving community, and keep the momentum you discussed in your post. Thoughts? Happy New Year to you and the rest of the community - wishing you all the best for 2017 and beyond. ?

One way of doing it would be: foreach($pages->find("parent=recommendations") as $child){ echo $child->title; } but there are many more ways to accomplish that goal. Best starting point would be to read the docs of selectors

Happy New Year! Looking back over the last year, it's been a really great year for the project, and wow has it gone fast! In this post we'll look back at some of what we've accomplished over the last year, and–more importantly–introduce and review our 2017 roadmap. Today we've also released version 3.0.47 dev, which doesn't add anything new feature wise, but does contain several optimization and bug fix comments. https://processwire.com/blog/posts/roadmap-2017/

On Vimeo: What Comes Next Is the Future (2016)

Hello, I have been working on my first pw site the last view days. Normally I work with Wordpress. I never really had to make a theme myself so this was a nice challange. I took some parts from another theme and added some scripts I found online. The waves on the frontpage are based on repeating field. A text area, background color, wave color and yes/no for the waves. The contact form is made of PHP as I could not get a javaScript solution working. Please share some input to make it better... and please be nice as it is my first attempt at PW.. link is: pw.webhoes.nl Sanne

My bad. It was a read-only issue. I solved it creating a new config.php file and copy the content of the original into the new one.

My personal/professional website as designer (UI/UX, motion graphics) and developer. The process of this thing took ages and there's still a lot of content missing, it's always a hassle with your personal websites. But building it with PW was a breeze, I really love all the flexibility the system provides. I can't imagine using any other cms in the future… Check it out: www.thomasaull.de

Another great year with the great PW community!! This year was the year I got tons of projects in PW, and they were just like ProcessWire is wants things to be: fast, simple and fun!!! All the learning paid up, thanks everyones, couldn't have done it without your help and buried posts!

Basic implementation of the Simple MDE as an Inputfield. https://simplemde.com/ Module developed in reply to request from @OrganizedFellow (https://processwire.com/talk/topic/13474-found-a-handy-js-based-markdown-editor/) Modules Directory: http://modules.processwire.com/modules/inputfield-simple-mde/ Github: https://github.com/outflux3/InputfieldSimpleMDE Editor example: Preview mode: Frontend output (using Markdown/Parsedown textformatter and Image Tags) Limitations etc: This has been tested with multiple instances on 1 page and seems to work fine. Toolbar is not configurable, but you can edit the JS file; In the spirit of keeping this simple, there are no module settings. If you want the spellchecker, you can enable it in the JS file. If is seems that there is a need for configurable instances, it could be added, but so far this works fine and can't see any reason to complicate it further.

I am glad to present our recent website. It was made, of course, with Processwire and this is the first time we use this CMS in our company. The website (in French only) is aimed to gather ski results from four youth ski clubs (our clients). The administrators needed something easy to use and be able to import XML ski results after a race. Those results are divided between ages (four categories, girls and boys), each ski category having its own rules for distribute points and ranking. The administrators wanted also a place where representatives of each club could post photos (elite team only). Processwire was the perfect candidate for this site which is fully mobile. Race calendar and results (click on this archived season to see the whole process since the present season has not yet begun as the writing of this post.) Annual ranking Documents (use of hanna code to place and identify type of document) Photo albums Elite clubs

Thank you! Yes I confirm : /site/config.php. I solved my issue (see my post before).

As for adding a class to the current page based on the current's page URL name and the parent's URL name, you have many options. Here's how I might do it, by adding a class to the body tag that would make it possible to target any element on a page in your CSS: <body class='<?php echo "page_{$page->name} parent_{$page->parent->name}"; ?>'> If you were on a page with URL "/news/press/", the result would look like this: <body class='page_press parent_news'> Rather than assigning body classes based on the current page and current parent, I usually find it's more convenient to assign a class based on the current section, or "root parent page" as it's called in ProcessWire. Typically these section pages are those that appear in the top navigation. Having every page identify it's section via a <body> class means we can easily highlight the current section in the navigation with our CSS. So here's how I might output the body tag: <body id="section_<?php echo $page->rootParent->name?>"> If we were on the page /news/press/, the result would be: <body id="section_news">

I guess you had a deadline of sorts. But still, I'm always weary of showing anything that is not either complete or falls below what I think the Client expects. Been at the wrong end of it too many times for no reason of my doing. .... or help out with (mostly) constructive suggestions ...

Just a quick heads-up: I'm moving this topic to the module development subforum.

Hi Sanne, nicely done. At first glance, I spotted two small issues: the carousel arrows unfortunately don't work, and the "LEES MEER" buttons on the portfolio page aren't functional (I'm using Firefox here). That said, I like the soft slide-into-place effect on navigating between pages, and the styling is pleasing and harmonic.

Never mind @Guy Verville! It's a nice site, thanks for showcasing it. It is just that this forum is full of developers, so we cannot help it but comment...

Hi Francis, I know those tools. Perhaps I was too eager to show this site before optimizing it. We didn't stressed that much this aspect because the client doesn't need to be known. That seems weird, but there is no Google Analytics set on this site. Why? Because this is almost an intranet of a sort. Anyway, that doesn't excuse anything. As the Webpagetest tells, there is another more irritating aspect : the first byte latency. Those statistics are to be taken with a grain of salt also. The visitor gets visuals after 1.5 sec (http://www.webpagetest.org/video/view.php?id=161230_DH_MDH.1.0). What takes so long are those images in the photo album which aren't that optimized even though there is a routine to implement srcset/sizes alternatives, and also the buttons (I don't understand that there aren't svg. I'll ask the team to redo that). So, too soon to present this. :-(

I dont think there is such field, I would perhaps add some CSS to fix (clear or before-after pseudos).

v117 contains @bernhard's idea (see above). I've also managed to add the "100%" text on full-width fields because this makes percentages align nicer.

Order of input and label should be changed because of css seletor based on checkbox state (checked / unchecked) like this. input[type=checkbox]:checked + label:before {} I used this markup to get font awesome and css styled checkboxes work. <div class=field> <input class=input> <label class=inputfieldheader>Field three</label> </div> It would be awesome if modules like inputfields and form api would be written for frontend usage, but it's optimized for admin backend use only.

We did discuss a UK meetup some considerable time ago. (Wow, 2012, not far off 5 years ago!) There were probably only half a dozen UK based active forum participants back then, and it's something I would be happy to revisit.

I just private messaged you with some stuff, but for anyone else that is following the discussion, check out how Hanna Code Helper handles the loading of a CKEditor plugin: https://github.com/teppokoivula/HannaCodeHelper/blob/c26b3b7eeafa17dd8500dc1b89cbb88218ceca9c/HannaCodeHelper.module#L55-L97

Pretty much exactly what I offer as a web designer -> look at wix or sqaurespace and if you want to do something more interesting in functionality or design then come to me and I'll make up a PW site with the extra requirements. I like working on new and interesting projects not just banging out the same site again and again, so PW works well for me. Plus the community are super helpful! I never enjoyed the swamp of wordpress and drupal modules and forums