Leaderboard

Hi, I just rebuild my website using ProcessWire: http://nico.is/ Should be working on all major browsers (that excludes IE). Two things: - The "browsers" are build with pure CSS3 (not the arrows) - Have a look at the footer / Nico

Purchased, awesome module. thank you

I just wanted to share that I just published a ProcessWire review on CMS Critic. If you have anything to contribute as to why you love ProcessWire, please share in the comments. Thanks guys!

I'm setting up a site that is private - it has no public viewable pages. First I tried to edit the "Guest" role and turn off "View Pages" - that's not allowed. Then I tried turning off the "Guest" role on the Access tab for the Home page, thinking all the child-pages would inherit that setting by default - that's not allowed either. Are both of these restrictions "real" and in place for a reason? It seems the only way to set up a private site, is to go through all the templates one by one and turn off the "Guest" role for each and every one of them - not a very practical or safe approach for a site that is intentionally private by default...

Both are ideas I had too. So links are working now and I'm working on multiple images (I already uploaded at least two images of every site)

I've written a module that fulfils a small but hopefully useful need to provide clients with links to "live" but work-in-progress pages so they can be viewed by those that don't have a CMS login. The basic process is to add a "create draft" link to the page listing (after edit, new, move, delete etc). When clicked, this link creates a clone of the page and adds an MD5 hash of the current time to the URL so that a draft clone with an effectively "un-guessable" URL (name) is created that can be given out to clients to view the page. This clone has a "publish" link added to it in the page listing so this can then be copied over the original published page, and the draft deleted, with one click. The cloned pages also has "(DRAFT)" added to the title. Does this sound useful to anyone? The only problem is that, because the "draft" page is published it will show up in menu listings and anything else that is utilizing the site structure or API to grab live pages. If the "published" nature of the cloned pages makes this idea unworkable then I will go back to the drawing board! But if it has potential to be useful then I will at the very least publish the source on github or copy it in here so it can be tampered with by others. It occurs to me that it wouldn't be hard to filter out these pages with "(DRAFT)" at the end of the title so they don't show up in menu listings etc, but this would require extra effort on the part of the developer in every case where the fetching of pages is occurring.

I've been working on a blog profile that we can have as an installation option for ProcessWire. The goal is to have a profile that someone could download and setup a pretty nice website/blog without having to touch any code (i.e. it's ready-to-run and populate). I'm hoping that this is something that may help us to grow our audience beyond the web development community. The requirement is that it must be as easy (or easier) than WordPress, both to install and use. This profile is also for web developers, as it's a blog profile ready to be styled and enhanced -- a good starting point. It uses the Zurb Foundation CSS framework, so it is fully responsive and mobile-ready. It's not much to look at now, but should be fully functional. I'm making progress and wanted to post a preview. The content you see here is from one of my client's blogs and the content is just here to test things out. http://processwire.com/blogtest/ I'm hoping to get this up on GitHub next week. I've never really done much blogging, so am seeking feedback on what others would suggest to make the blog profile as good, powerful and simple as it can be. Right now it's pretty much a generic Zurb Foundation "look and feel", so it probably needs at least some color tweaks and integration of some masthead photo(s) or something.

I know the bulk of you are coders and likely can figure this out on your own but for those who are not, I thought I'd throw this solution in here just in case someone else has a need for it. I created a simple widget-google-plus.php file for those who want to add a Google Plus widget to their sidebar (or elsewhere) in Processwire. To use, simply upload the attached widget, changing the profile URL to yours and add the CSS / tweak as needed. I've no clue how to build a module so I am doing this as a tutorial. First the logic: If you are anything like me, you crave customization. I hated the fact that Google wouldn't let me remove the border from around their google plus badge so I decided to create a solution of my own. Here's how it looks straight from Google: To get rid of this obnoxious border, I created a new widget (attached) with this code: <div id="googleplus_widget"> <span> <div class="g-plus" data-width="275" data-height="69" data-theme="light" data-href="https://plus.google.com/your-profile-id-goes-here"></div> <script type="text/javascript"> (function() { var po = document.createElement('script'); po.type = 'text/javascript'; po.async = true; po.src = 'https://apis.google.com/js/plusone.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s); })(); </script> </span> </div> As you can see, it's wrapped in divs which I then styled with the following CSS: #googleplus_widget{ width: 280px; height: 50px; } #googleplus_widget span{ width: 200px; height: 50px; float: left; overflow: hidden; background: #fff; } #googleplus_widget span div{ margin: -1px 0 0 -1px !important; position: relative; } To use, simply modify the attached widget-google-plus.php with your google plus profile URL, upload to your ProcessWire installations /site/templates directory and go to Setup and then Templates within the back end of your install. The new widget php file should show up under the "Templates found in /site/templates/*.php" , check it off, click add template and then add it to your sidebar if you choose to do so. That's it. Hope that helps someone. I know it's a minor contribution but at the very least, this is recorded for me to reference later when / if I forget BTW. If there's an easy way to make this into a module, I'd love to be able to do so even if just for myself and future newbs. widget-google-plus.php

Just found processwire.net! whoa. When did this come online?

Lately I’ve been building a little script for a local journalist who manages a open Google Docs spreadsheet where Swiss journalists can enter there social media data like Twitter names etc. The script updates a Twitter list with the collected Twitter names in the spreadsheet, means it gets the document feed through Google Docs API and updates the list through Twitter API. Long story short I’ve been dealing with the oauth authentication mechanism. I started thinking about creating a module for PW to connect user accounts with oauth providers like Twitter. Could be helpful in more community focussed projects.

how .about edit /site/templates/markup/posts.php cha.nge if($total) echo "<h3>" . sprintf(__('Posts %1$d to %2$d of %3$d'), $start, $end, $total) . "</h3>"; to if($total && wire('page')->id > 1) echo "<h3>" . sprintf(__('Posts %1$d to %2$d of %3$d'), $start, $end, $total) . "</h3>";

/site/templates/home.php cha.nge $content = $page->body . renderPosts("limit={$page->quantity}"); to $content = $page->body . renderPosts("limit={$page->quantity}", true); see.more in /site/templates/blog.inc too

I'd be glad to contribute to the front-end dev.

We have been developing it with varying speed for a long time already. How does it feel for you guys? Any ideas where to improve? Direct contributions to css are also welcome I think. Jbroussia: not exactly a framework, but it is built using goldilocks approach. I think it is still one of the best ways to do responsive design.

Text says: The screenshot below the text is "ProcessWire-15.jpg" (see the text under section "Who can access this page?" in the picture).

That sounds interesting - here's a thought: if the URL is going to be "unguessable" anyhow, then why do the draft pages even have to be real, published pages? It might make more sense to keep them unpublished, so you don't have to "fix it in the mix" by trying to filter them - I suspect that's going to lead down a long road of other side-effects. Instead, you could set up a controller that takes the unguessable key as an argument - so you get something like "site.com/preview/2442cb34cfc234dbf41cbf3c4", where "preview" is a page that accepts the key as an argument... your controller (or I think the term is "process"?) can then fetch the unpublished preview and render the page. Does that sound like a working approach?

Due to the name change, the module is now here: https://github.com/mindplay-dk/PageListPin I have tagged it as 1.0.0.

Just a quick note to say that I'm going to attempt to set up my "online visibility / seo" business site (thatcriticguy.com) using this profile / processwire. I'll likely be back offering my suggestions soon. Might even slap up a review on CMS Critic while i'm at it.

Version 1.1.1 now available. Just fixed a bug that occurred if multi-byte support was not installed on your host. (Thanks to renobird for finding that.)

I have gone ahead and added this capability to the dev branch. Now pages with repeaters can access images within the repeaters, and repeater pages can access images from their containing pages.

Thanks to everyone for the warm welcome! I'm really digging Ryan's tracks, a good mix of beats and spaciousness. Sunvox looks cool, my wife just got an iPad so I should check it out. TBH I'm banging away on an 8-1/2 year old HP Pentium 4 PC at the moment. I'm exploring both the Default and Blog PW site profiles, things are starting to make sense. Also I just got Robin Nixon's PHP/MySQL/JS/CSS book. Thanks again!

I just pushed an update to the source that should prevent it from creating directories for pages that don't need them. Next up: going to make a module that removes empty directories, for those that want it.