Leaderboard

Hi, I'm currently building a Community website in PW and now planning 'history of the village' pages. This is where members of the community will send in stories, memories, photos etc. I was wondering how easy it would be to create a timeline like the one in Facebook, where the items are displayed by the date they occurred (not date added to timeline). Unlike Facebook the posts will have to be moderated (like Wordpress comments) before they appear on the timeline. I have no idea how to go about this so any thoughts will be greatly appreciated.

Greetings NooseLadder, Sounds interesting! I'm also "cooncepting" some similar ideas. For example, I live in a very active arts community, and I want to let people post images, descriptions, and addresses of their exhibitions. If you get going on this and would like to collaborate, let me know. Maybe we can share some ideas -- or even develop a ProcessWire profile to share with the community? I'm still fairly new here, but I already can see that this sort of concept would be fun to implement with ProcessWire. My main effort right now is learning to build entry forms for "regular" visitors to submit stories. Keep us posted on your progress. Thanks, Matthew

If those pages don't have a template file, you could check for the existence of the file foreach($parents as $parent) { if(file exists) //echo link } or you can use the same template for all the section pages foreach($parents as $parent) { if($parent->template != "section") //echo link } or create a global field (available in all templates) from type checkbox, and check it on the section pages foreach($parents as $parent) { if($parent->section = 0) //echo link <-- EDIT: I changed from 1 to 0 here }

@onjegolders, you're doing more then great !

Hi guys, I'm Marco, Italian IT technicians and PHP developer. In the past I've used Symfony, Wordpress (and Drupal, Joomla, ..).. in this days I try to come close to EE2.. but these aren't a good days for EE2 community. I read about PW from a tweet, and now.. Have a nice day, Marco

Yes, I've been meaning to add it but neglected to put it on my list. I've just added it, so will plan this as a 2.3 addition.

Pattern support is now in place for text fields (dev branch). The pattern applies both client side (HTML5 pattern attribute) and server side, for the validation. I looked through all of those patterns are html5pattern.com and couldn't find any that weren't PCRE compatible. So if it's not 100% compatible, I sure can't tell the difference. My guess is that HTML5 patterns are compatible with PCRE, but some of the more advanced PCRE stuff (maybe atomic grouping or negative lookbehind?) might not be compatible with HTML5.

Hi, http://kudlek.com/ this is my second project with PW and one I like in particular. I made this side in Textpattern but migrated it as my client wasn't happy with what he got from TXP (and me neither). There is nothing very special on this site but some gimmicks needed my attention such as the exhibitions archive. I enjoyed it very much to work with PW and the endless flexibility it has to offer. There were no limits. My client is very happy with the system. I have Ergo admin theme installed. Best, Christoph

Just launched this site a few minutes ago. It's not totally done, as I've still got some detail work to do, but figured it was at a good point to share: http://www.houghtonacademy.org I did the design and development on this one. Like the blog profile, this one uses the Skeleton responsive CSS framework. Though I went a lot further with the media queries on the mobile side than I did for the blog profile. So you should see a nicely optimized layouts for tablets, mobile portrait and mobile landscape. So far only tested on iPhone though. Many of the graphics (though not all) are also optimized for Retina displays. When you get to the homepage, you should get a different photo and tagline on every page load. Highlights (in terms of ProcessWire development): Faculty Directory: http://houghtonacade.../about/faculty/ The data for the faculty directory is updated once daily and it pulls from a service called Veracross, that manages all their school systems. They are all represented as pages in ProcessWire, so the client can add unique biographies and such that aren't present in the service it pulls from. Form Builder is used throughout the faculty directory to power the individual employee contact forms. Events Calendar: http://houghtonacade.../news/calendar/ The events calendar uses jQuery plugin FullCalendar and it pulls from a ProcessWire-powered JSON feed. ProcessWire gets the data from a Veracross feed a few times a day, caches it, and creates a new feed specific to use with FullCalendar. The events data is also used on other pages in the site, such as the homepage. Photo galleries: http://houghtonacade...f/photogallery/ There are several photo galleries throughout the site, and they use the Photoswipe jQuery plugin, which is really great when using mobile as it duplicates the behavior of using the built-in iPhone photo gallery. Thanks to Soma for recommending this back in another thread. Video pages: http://houghtonacade...out/headmaster/ These are powered using the TextformatterVideoEmbed module and are responsive (per the latest update to this module).

Thanks Adam, I'm trying to put the points forward and put PW's name out there! http://www.andregoldstein.co.uk/blog/why-more-often-than-not-i-use-processwire/

1.) He's using Joomla. He can't understand this. 2.) It's not about the number of features. Actually, the less, the better- are you really using all of them? 75% of them? 50% of them? 3.) Years of testing… Right. (come on. If anything has 100% of code years-tested, it's probably outdated) 4.) Want to do it different way than your precious module? Yea, fuck you. [This is 95% applicable for WP/drupal as well) --- With building on huge CMS + modules, you end up doing a lot of compromises, which I'm not willing to do. And those are also the bad compromises, the ones users see (unlike e.g. Rails, which makes do stuff his way, but output and experience are in your own hands) --- Ultimately, I'm not selling my clients my ability to stick modules together. I sell the best possible website (in terms of Bussiness Goals and UX) I can create.

ProcessWire modules are by nature meant to save time. There are 3 modules that I think can be big time savers on almost every project: The MarkupPagerNav module included with ProcessWire is hard to imagine being without. Yet, I was doing pagination without this for a long time before making it, and... things get done a lot quicker now. The MarkupSimpleNavigation module can be a big time saver when it comes to many common navigation scenarios. The FormBuilder module is a big time saver when it comes to creating forms. It's turned the most annoying and consuming part of development (for me at least) into one of the quickest and easiest. When it comes to front-end development, I'll admit that I've always preferred starting from scratch. But lately I've been enjoying what some of the CSS frameworks like Skeleton, Foundation and HTML Kickstart bring to the plate (and Twitter Bootstrap I'm guessing, but have not used it). With the appropriate project, these are huge time savers. The project I'm working on now (for a boarding school) needed to be responsive and very unique in design, and I found Skeleton to be the perfect balance there. It provides just enough to make things responsive, and very little else. That left little room for the design to be influenced by the framework (which was desirable in this case). If I didn't need responsive on a particular project, and could let the design benefit from some framework influence, I'd go straight to HTML Kickstart as the biggest time saving framework. Lastly, I'd say that using the Basic Profile as a starting point has always been a big time saver for me. Almost every site I build needs the core framework of fields and templates included with the basic profile. While all the markup and CSS ultimately get replaced, it saves a lot of time having these things there ready to implement.

I don't have a simple solution to this one, but will do more thinking about how I could have ProcessWire provide a hook like Pages::statusChanged or something like that. But until we have something like that, here are a couple ways you could do it: Option 1 Add a hook to Pages::saveReady and have your hook function do something like this: Pages::saveReady hook $page = $event->arguments[0]; if($page->id && $page->isChanged('status') && !$page->is(Page::statusUnpublished)) { $result = $this->db->query("SELECT status FROM pages WHERE id={$page->id}"); list($status) = $result->fetch_row(); if($status & Page::statusUnpublished) { // page is about to be published // send your email } } Option 2 The other option would be to change your workflow such that user submitted pages went into a different parent than the live ones. For instance, user-submissions might go into parent /pending/ and published submissions would live in /live/. Then you could have your hook monitor for when a page is moving from /pending/ to /live/. If you wanted to, you could also have it take care of the publishing automatically: Pages::saveReady hook $page = $event->arguments[0]; if(!$page->parentPrevious) return; // if page is not being moved then stop now if($page->parent->name == 'live' && $page->parentPrevious->name == 'pending') { $page->removeStatus(Page::statusUnpublished); // send your email }

And why you also want them to insert in the page body tinymce text? You could still use a "textimages" field or so underneath the tinmyce field so image could be uploaded there if really needed. Sounds from other posts, like you're trying to bend things a little while having all possible (queries, categories, repeaters) that is currently not there and repeaters are maybe an good option to be able to query them. I wouldn't consider repeaters designed for that use, but surely works (apart from not being accessible in a outside repeater text field or from other pages. Depends a little on what exactly we're dealing with here. Products catalogue, news articles, common content/infos? If it where really about meta infos and something like gettyimages, the one image as a page together with meta infos as much as needed would be the way to go. If for articles or news I would consider just using a images field for each category (summary, gallery, details) and upload them separate in a dedicated field. Maybe tradeoff reusablity some for easy, straight forward setup. I would consider giving function meaning by using many images fields, rather than a category select. Especially as in your case the category is "function" and not real meta info. Maybe it can be even mixed with some centralized image content that are pages with collections of images and you can add them to any page through page select field. I would carefully think it out what really matters. Also creatiing a new extended image field that has a pagefield might a good solution too. Works surely better for single image fields as it would for multiple, but in both cases you will always have to set the "category" everytime you replace or upload a new image. There's really a lot that can be considered regarding image management, but I never felt I needed more than there is. Not saying there could be more options for special cases in a image default field. Still maybe a module would be the way to go to give a needed functionality rather than using something that will may limit you later on.

I understand that other CMSs have places where you might edit code in the CMS, and I also understand there is a convenience factor in many cases. But the main reason why I want to support snippets is actually to encourage sharing of code snippets. It's feasible that we can have a library of snippets that people can just paste in, and this is accessible to anyone. This is the area where I think the snippets may be worth the compromise of their downside. But I will do as you suggested and document why people might want to avoid using snippets for custom site-specific code, or plugging things into live sites. Thanks, Ryan