Leaderboard

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).

Just wrote a little about why I am here and not there http://www.mademyday...-over-modx.html // fixed URL, sorry.

com.gratlatons To forum for ocre 20.000 massages

This module tries to help in very common admin task: emailing user a new password. I implemented this as a fieldtype, not sure if that is best way to go? I did it that way to allow simple API usage and offering easy customization (like in what position to put the reset checkbox etc). Simple Five Steps installation™: Copy the file FieldtypeSendUserCredentials.module to /site/modules/ directory Install the module from Modules section Create new field, call it "send_password" or whatever you like to call it. Important: choose SendUserCredentials as a fieldtype Edit user template (if you can't find it, Filters => Show system templates) Add new field there Usage from admin: Edit user and check the new field. Save. Usage from API: $u = $users->get("apeisa"); $u->of(false); $u->send_password = 1; // send_password = whatever you have named your new field $u->save(); TODO: Offer better security by requiring password change right after login EDIT: Removed the permanent Added few comments and better usage from API instructions FieldtypeSendUserCredentials.module

Assign edit access to individual users on a per-page basis The user must already have page-edit permission on one of their roles in order to get edit access to assigned pages. Otherwise, they will only gain view access. This module is fully functional as-is, but intended as a proof-of-concept for those wanting to go further with adding custom edit and/or view access. The main functionality in this module consists of only a few lines of code, so it should be a simple edit for anyone wanting to take it further. If you make some useful additions to it, please post them. How to use Create a new role called "editor" (or whatever you want to call it) and give the role "page-edit" permission. If you already have a role in place that you want to use, that is fine too. Under "Access > Users" locate the user you want to assign edit access to. Edit this user. For this user's "Roles" field: choose the new role you added, "editor" (or whatever you called it). For this user's "Editable Pages" field: select one or more pages you want them to be able to edit. Save the user and you are done. To test, login as the user you edited to confirm it works how you expect. http://modules.processwire.com/modules/page-edit-per-user/ https://github.com/ryancramerdesign/PageEditPerUser

yoohoo

Some 2.3 updates now present on the ProcessWire dev branch at GitHub: New session handling features ProcessWire now supports alternate session handlers and includes a new module that provides for managing them in the database, rather than the file system. To enable, you just install the SessionHandlerDB module, and that takes over as the session handler. The advantage of a database session handler is that it can potentially be more secure in some shared hosting situations. It also enables ProcessWire to report on active sessions in the admin, so the new handler also adds a "Sessions" option to your "Setup" menu that gives you a table showing everyone browsing your site and where they are. I plan to expand upon this a bit more though. The new session handling interface also makes it possible for you to add modules that would move session handling to something like memcache, Amazon Dynamo DB, or really anywhere. New password security updates ProcessWire now uses Blowfish hashing for passwords when you are on PHP 5.3 or newer. If your database were to ever be compromised, this provides better protection from someone attempting to reverse engineer passwords from the hashes. Beyond blowfish hashing, we still use double salting as before (with one salt on the file system, and other unique to each user in the database). For existing accounts, the blowfish hash doesn't actually take effect until you change your password, so it'll be a gradual transition for many of us. Though the admin does give you a reminder every now and then. However, once you go blowfish, you can't go back, so don't develop a site in PHP 5.3 and then launch it to a PHP 5.2 server, unless you don't mind changing your password(s). And more… Addition of the WireHttp class, which provides ability to perform POST requests from the API. ImageSizer now uses better image type detection rather than image extension detection (via @teppo) WireArray now supports ability to sort by multiple fields at once as well as implements 'limit' and 'start' in selectors (via @nik) Updated to latest jQuery and jQuery UI (via @mindplay-dk) Removal of some big bottlenecks from FieldtypeRepeater (via @nik) Transparent GIFs are now supported during resizes (via @mrx) Support for 'min' and 'max' with integer and float fields Support for HTML5 'number' type with integer and float fields Support for HTML5 'required' attribute with many fields The datepicker in the datetime fieldtype now supports ability to specify selectable year range Several other updates in the commit log.

You definitely deserve a lecture for debugging PW dev branch there - concentrate man!

Based on the insane development speed of ProcessWire 2, I assume "version 2" is just Ryan teasing us and releasing the ProcessWire 1 in small pieces for wider audience "Oh, they want form builder? I have build it nine years ago..."

So simple! I am used to overcomplicate things thanks to my experiences with other CMS's. Thanks.

I have been using IE10 preview release for Windows 7 today and used it during site development (includes little content work). Good news: drag & drop uploads do work in IE10. Bad news: it seems to work very well on all around PW... that means no superfun IE bug hunting ahead...

Great news! What is your favorite massage Willy?

I was actually thinking of adding a "Tools" menu to ProcessWire admin (in addition to Pages, Setup, Modules, Access). The reason for it is that we've now got a lot of tools that don't necessarily fit the definition of "Setup", so thought it might be handy to come bundled with another place like that. PW1 had such a Tools menu like this.

The latest version of Form Builder (0.1.7) now has a File Upload input type, so we're a little ahead of schedule on having this ready. It's currently in beta test, but available for anyone that wants to try it out as a download from the Form Builder support board. So for anyone that was waiting for file upload capability in Form Builder forms, we've now got it.

(Note: Module name temporary and will change) As recently mentioned here I am recently working on a little module. This module gives you a new admin page under "Setup" to create pages in a "batch" mode. What does it do - You can select a parent page where you want to create your pages. Then it will give you a list of templates you can chose from. Those should be permission and template setting aware. Also only parents that really can have children will work, else it will give an alert. - Add as many pages you like by clicking "+add Page". You can set the pages published or hidden status. Sort or remove the pages. - After you entered a template and at least a title you'll be able to klick "create Pages". If successful it will append the list of pages you just created with an open in page tree or edit link, and also the parent. - You can add pages and repeat the process to add pages to the pages you created simply by changing the parent page in the field above the table and go on. It's all ajax and not page load. Also the links of the created pages that get appended below will stay in the document and only the form entries get cleared. This is still work in progress, but I thought enough to share and if you like you can try/test/use it. Download: ProcessTools.zip Screen:

EDIT: <script type="text/javascript" src="http://use.typekit.com/xxxxxxx.js"></script> <script type="text/javascript">try{Typekit.load();}catch(e){}</script> <style type="text/css"> .wf-loading .blog-title, .wf-loading .post-title { /* Hide the blog title and post titles while web fonts are loading */ visibility: hidden; } </style> That's from this link http://blog.typekit.com/2010/10/29/font-events-controlling-the-fout/ in 2010 but worth a try

Fixed the link, sorry. This forum software drives me nuts.

@soma: At least I used your solution from that very thread as I happened to need something very similar the next week you had shared it. Not that it would necessarily make you feel any better, but just wanted to tell that you were acknowledged back then . Anyway, clever usage of what ProcessWire makes possible, from the both of you.

If it's not in the sheet it's most likely also not in the documentation. I'll add it. I think there's still some useful things missing in documentation and so cheatsheet, but can't think of any ATM.

Funny that people didn't seem see that this proof of concept type of module has been posted and share a couple times. Nothing new. I actually posted too early as I thought it would be a more advanced module by Ryan The thread here is full of it: http://processwire.c...__40#entry17534

There seems to be a bug in ProcessPageType (dev branch) that affects at least user list: renderList() tries to render MarkupPagerNav with params $pages and $pagerOptions, which fails since $pagerOptions is by default null and MarkupPagerNav expects an array. Following changes seemed to fix this, at least in this case. Haven't had the chance to test further yet -- currently on a lecture, can't spend too much time debugging/testing.. - protected function renderList($selector = '', $pagerOptions = null) { + protected function renderList($selector = '', $pagerOptions = array()) { This came up while adding users to a site (26th user => page won't render.)

Thanks! Looks like I had an extra slash in there, now fixed. For you guys that asked for admin screenshots, I looked around to see if there was anything interesting worth making a screenshot of. Maybe the homepage editor? Here it is:

Href-attribute seems to be broken, see the screenshot. I'm using Chrome Version 23.0.1271.64 on a Mac. Edit: ...and same with Safari. Though why would the href be browser dependent anyways.

Just checked -- it looks like its not in the cheatsheet. Soma, if you are reading this: can you add it, or tell me how to add it?

i just like to say a big THANK YOU GUYS i'm realy happy that my little wish got this huge reaction and i'm more than happy that it got real! pw motivated me a lot to dive into php and i hope i can give someday a littlebit back to the community (extensions , etc.)

Congrats! Also, I went through something like the red-herring db problem few days ago, and the result is: always check your db after import, and compare it visually to original one. When there is a problem with DB, ProcessWire won't pick it up (as won't any system), but will fail with first error that happens due to corrupted DB (In my case, it was Sequel Pro export error)

anything with a happy ending?

Glad you figured it out! I didn't know what to suggest next.

I just wanted to write that i sometimes had similar issues i think when tinkering a lot with modules. I figured mostly just a refresh 'check for new modules will throw such an error but delete module cache and is fixed. If not manually delete cache. Glad u figured out what the problem was.

Hello lenoir! Someone just asked a similar question today. Apparently it's fixed in the latest development version : Nice theme by the way

PW 2.3 protects file-based assets to unpublished or non-public pages, so this won't be a concern much longer. Matching up names is just one way to do it. I just put together a quick module that provides another way you could do it even more easily:

You can count me in - I'm still under 100 posts myself but I've been reading almost every single post for a half a year now. I'd like to see the figures for Finland without visits from the three of us.

FTFY ^^

What do you have to say in your defence soma?

I'd suggest changing this line: if ($pages->find("template=blog-article, tags=$tag")->count() > 0) { To this: if ($pages->count("template=blog-article, tags=$tag") > 0) { The reason is that find() loads all those pages, whereas count() just counts them... far less overhead if you don't need the actual pages loaded (which it doesn't appear that you do).

As Apeisa says, within your foreach loop, you'll need an if statement so: foreach ($page->children() as $child) { if (count($child->images)) { echo "<li><div style='float:right;'><img style='margin:5px 0 5px 5px;' src='{$child->images->first()->size(232, 176)->url}' alt='' /></div>"; } echo "<div><a href='{$child->url}'>{$child->title}</a><br /><span class='summary'>{$child->summary}</span></div></li>"; } EDIT: Need to "count" to see if their are images

<?php if ($child->images) { // We have images } // You can also check the count if ($child->images->count() > 1) { // We have more than one image }

Just made version 1.1 of this module available (GitHub). Changes (additions actually) in latest version: Explore properties and data of matching pages in a tree view Language aware: multi-language and language-alternate fields supported Repeater fields and values Images and their variations on disk More data is loaded on-demand as the tree is traversed deeper [*]Quick links to edit/view pages, edit templates and run new selectors (select pages with the same template or children of a page) [*]Page statuses visualized like in default admin theme I'll update the first post in this thread and include some screenshots there as well.

Google certainly agrees - http://google-styleguide.googlecode.com/svn/trunk/htmlcssguide.xml#HTML_Style_Rules