Leaderboard

I am preparing a quote for a customer for a big website (actually 4 websites of a similar kind). After several years of using MODX, I want to build that site in ProcessWire (of course). The client has no problem with switching the system because he trusts in my judgement. The only thing he fears is what if I am not available anymore (accident, sudden fabulous wealth etc.). While there is a good visibility of MODX folks around even in Germany, ProcessWire is new, is young and the common customer doesn't know it. So how can we convince doubtful people about the reliability of PW, how can we - especially in the local market - form as a network of people using PW which are are able to step in if someone can't handle his project anymore? I think perhaps we could start forming local user groups, starting with countries, later perhaps even cities / regions. The goal could be a listing of people using PW with a small profile (specialized in Backend, Frontend, contact data, hourly rates etc.) so we can show our customers: "Look, these people are using PW every day. These people can step in if I am not able to manage your project." Some kind of assurance and argument against the opinion that we are using a system no one else does. Opinions?

Sure! Mike over at CMSCritic is a good guy and I'd support anything he's doing over there. I'd encourage anyone that wants to vote for ProcessWire in any of those categories to please do so! I know I will. My experience is these guys are pretty hard to get through to. I've personally talked to Eric Meyer and Jeremy Keith about ProcessWire and gave them a card with the URL on it. Even had lunch with Eric Meyer (he sat down next to me at an AEA event), and he's about the nicest person I've met. But I think he was relieved to talk about family and kids rather than webdev. These guys get hounded with everyone they meet telling them about their project, and it's pretty much all noise to them (as most of it probably should be). The mention of a "CMS" is especially noisy, as nearly every developer has dabbled into making their own CMS at one time or another. I'd venture to guess these guys hear about some new CMS almost every day. They make a genuine effort to act interested, but they really aren't. They need to hear about something many times, or from one they know really well, before they will take the time to investigate. Ultimately I'm just interested in making sure ProcessWire is the best tool of its kind. Whether its "known" or not is beside the point. Granted, I'd like to share it with as many people that will benefit from it as possible, but would rather let folks find it at their own pace. I think ProcessWire is a real competitive advantage for many (at least is for me), enabling us to get things done quicker and at less cost. So if everyone was using it, it'd be harder for me to get work.

A recent post on PageArray find() made me try and fix a couple of things discovered there (and in some earlier posts, I think). What I came up with is a few modifications to WireArray class (base class for PageArrays): sort() accepts multiple fields to sort by. Fields can be given as a comma separated string "-modified, title" or an array of strings array("-modified", "title") find() supports start=n and multiple sort=field selectors some optimizations for sorting and limiting even quite big arrays without losing performance in certain conditions The new implementation seems to give same results as the old one where applicable (given only one field to sort by and no start selector for find()), but more tests are definitely needed. I've tested this on a site with more than 15000 pages and find()'ing 3000 of them at once for sorting/finding with the API calls. Performance is about the same as it was before. Even giving more than one field to sort by doesn't make it noticeably slower if limit is being used as well (those optimizations actually work). The replacement for wire/core/Array.php is attached if anyone's interested in trying it out. Array.php I tried some different methods of sorting as well, but just to find out Ryan had a good reason for all the little things I couldn't get a hold of at first . PHP sorting methods being unstable must have turned much of my hair gray in the last couple of days... While testing this I found out that sorting by a field with empty values at some records would act differently when done at initial $pages->find() (database query that is) compared to $aPageArray->find(). While this isn't affected by the WireArray code, I may dig deeper into it later. Giving sort=random works as it did before, but the code doesn't handle the situation it's not the only sort field given. Left a TODO-note in the comments on this (and the missing trackChange() call as well). @ryan: I will try to make a pull request as well just for the fun of it (being new to git). Do whatever you like with the code if you see any potential in it. You may want to rename function stableSort() and its last argument to something else at least. I know I'm not too happy with them.

I've been reading about ProcessWire off and on for the past couple of months to see if it's right for me or if I should stick with WordPress. I'm still trying to wrap my head around some of the concepts; I'm not a programmer, but I am eager to learn. There are things I like about both systems, but I keep coming back to ProcessWire's way of doing things every time I read a WordPress tutorial. So after lurking on the forums for a while, I'd like to say hello. The community here seems very helpful and kind to newbies. I've had to read some of the forum posts four times before I understand them, so I'll probably ask some dumb questions, but you all come across as a very patient bunch. I look forward to learning from you. - Tim

I wanted to give you a little preview of a new module I've been working on recently: the Form Builder module. This module lets you create simple-to-complex forms and place them in your site without any need for development. In this video we show how we can create, publish and test a simple contact form in less than 5 minutes. Then we take a quick look at a more complex form (already produced). I recommend viewing the full screen + HD 720p version so that you can see it more clearly than in this small forum embed. (note: there's no sound, so no need to adjust your volume) More about the Form Builder The Form Builder has many options for the developer to customize output and create their own themes, markup, etc. But the goal here was to build something that could enable you (or your client) to publish a form in less than 5 minutes, so that's the focus of this video. This tool is literally easy enough for your clients to create and manage their own forms. Or from a developers perspective, it takes something that used to consume hours and makes it happen in minutes. Form results save in the database and optionally can be CC'd to you by email. Result entries and be viewed, filtered by date, and even edited in the admin. You can export results to a spreadsheet as well. I'm working on the ability to export to pages, though that isn't quite ready yet. How the Form Builder will be licensed This module will be individually licensed on a per-site basis for a small license fee. It will also be available for free personal use to established forum members. Basically, I want to see if I can substitute some of my client work to focus on ProcessWire instead. And in order to do that, I need to have an income (I have a family to support). So I thought that building a special tool like this would be a way to make a go of it. A lot of you have asked to make donations to the ProcessWire project, and while we still won't be able to take donations, you will be able to support the ProcessWire project by purchasing and using the Form Builder in your own client projects. So a lot of motivation for this module came from wanting to provide something really special for all that had wanted to support ProcessWire. After a few months of work, I'm pretty happy with how this module has turned out -- it's already saved me tons of time in my client projects. So I'm thinking and hoping you guys will really like it too. I look forward to your feedback.

The IRC channel does seem to be busier than usual today - it's nice to see so many newcomers in there.

Something like this might be good? http://director-ee.com/ I also think that the client's concern is more one of proprietary vs. open source. The client is wise to have a real concern if they are dealing with a proprietary software. If they are dealing with an open source PHP software, they are already ahead of the game in terms of insurance. But a network or directory like you guys are talking about can only make things better, so seems like a great idea.

Hi Tim, I'm curious. Are you looking to become a 'programmer' who does sites and apps to make money? Or is it non-paid/hobby/personal projects. If you don't have any experience yet with cms'es i would just install ProcessWire and WordPress alongside eachother and experiment with both. It's good to have different tools in your toolbelt. Different projects have different requirements and while imho ProcessWire is one of the best, if not the best, allround PHP cms around, there can be situations where it would be better to choose a different solution. If you would want to setup your own social networking site maybe you'd choose BuddyPress.org. Or for some eCommerce website maybe you would want to use lemonstand.com/ Anyways, once you get going with PW i'm sure you will be addicted in no-time. I also want to mention the Blog Profile, you can learn alot by installing it, see how the fields and templates work together in the admin and after that look at the code in the templates directory.

@celfred, either the video you're trying to embed has embedding disabled or this could be a problem (or feature, can't really tell yet) at YouTube. There's similar problem reported at the WordPress bug tracking system here: http://core.trac.wordpress.org/ticket/14377. This example you gave returns code 401 Unauthorized and this is what oembed.com has to say about this particular error code: Will have to do some more testing later.. unless, of course, someone else knows a solution / answer to this problem already

Markup Simple Navigation Module While there was a lot of people asking how to make navigation, and there were many examples around already (apeisa, ryan...) I took the chance to sit down 2-3 hours to make a simple navigation module. It has even some options you can control some aspects of the output. Installation: 1. Put this module's folder "MarkupSimpleNavigation" into your /site/modules folder. 2. Go to your module Install page and click "Check for new modules". It will appear under the section Markup. Click "install" button. Done. Technically you don't even need to install it, after the first load call ( $modules->get("MarkupSimpleNavigation") ) it will install automaticly on first request if it isn't already. But it feels better. However, it will not be "autoloaded" by Processwire unless you load it in one of your php templates. Documentation: https://github.com/somatonic/MarkupSimpleNavigation/blob/master/README.md Modules Repository processwire.com mods.pw/u Download on github https://github.com/somatonic/MarkupSimpleNavigation Advanced example with hooks creating a Bootstrap 2.3.2 Multilevel Navbar https://gist.github.com/somatonic/6258081 I use hooks to manipulate certain attributes and classes to li's and anchors. If you understand the concept you can do a lot with this Module.

In case anyone is interested in using IRC to chat about ProcessWire, and having consulted with Ryan about it, I have registered #processwire on irc.freenode.net for that purpose. If you are a regular on freenode, just pop into #processwire. If you are not then the fastest way to get online is probably via the webchat interface at http://webchat.freenode.net/?channels=processwire&uio=d4 Hope to meet a few of you in there sometime.

זה לא ניתן לגשת לקבצים באתר /site/templates/ תבניות באופן ישיר. הנח את התסריט שלך במקום אחר. וכך יהיו

You're much into albums. Did you know "Alb" is ancient german myth creature that sit on your chest at night and make you have bad dreams "Albträume"? After reading you post I have more questions than you, so I think. I might get some sleep, have to pass on this for now.

Gazley, I think appending your special page like you intend is a good way to handle it (PW should take care of duplicated pages in array). And runtime sort sounds good to me too. So this is basically a cheer up post

You need to shave reno, your beard tickles in irc...

Exactly. In my case they are already using open source software (MODX). Their main concern is more the fact that this is a pretty big project with a lot of custom work and they fear that no one else can handle it if I am not able to anymore. I think a directory like the above could reduce this fear, because it shows that there are others who know PW and understand what I have done in this project. So, okay. Let's build a directory

OT @ Martijn It's apples and/to oranges in English.

Hi Tim - feel free to ask away. This is a good starting point if you haven't already read it: Other than that, the default installation can actually be quite helpful if you have a look through the templates - certainly the head.inc file has some good stuff in there for fetching data and iterating through it. It might be worth getting the latest download as well because the core files have changed a little over the past few months.

That's awesome ryan - looks pretty simple!

I was writing a reply yesterday when StopDaddy interfered. You now have all the info you need. but i'll post it anyways. Be sure to read. I'm assuming that the field is of the type 'textarea' without TinyMCE. This does not actually create html <p> tags. So if you hit 'enter' two times when editing the field contents it visually looks like a paragraph but it are in fact two newline characters. Newline characters are stored in the database but don't do anything visually when you echo it on the "web". Wanze's suggestions works. There even is a text formatter already for that. In the PW admin go to "Modules". Scroll to the Textformatter section and install the "Newlines to XHTML Line Breaks" module. Now go to Setup->Fields. In the fields table look for the relevant textarea field. Click on it. Go to the details tab and choose aforementioned Text Formatter. If you now look at "The Web" it should all be good. If all of this doesn't make sense to you or if your problem is somehow different you should read up on html and learn your tool (PW). and/or Provide us with a more detailed description of your problem and what you have already tried to solve it yourself. Things like looking at the generated html, corresponding CSS etcetera. If i speak for myself but guess most of the forum members: We are more than willing to help, also with basic questions, but some effort on your part is required. ps You should consider using a TinyMCE field because making look-a-like paragraphs generally isn't considered best practice

Ryan's php.ini guess seems to be the answer: http://www.directadmin.com/forum/showthread.php?t=43032&p=218391#post218391

This capability will be included in the first version, as I've now got it working. Here's a screenshot of a form configured to cross-post to Salesforce. When a form is submitted, it saves locally, emails to me, and then posts to Salesforce. Like many other services, Salesforce requires some extra variables in the request like "oid" (some sort of customer ID they use). They also use some of their own variable names, which you find when exporting a web-to-lead form there. In the screenshot you'll also see how to do these variable replacements. This same method can easily be used with other services like Campaign Monitor, Mail Chimp, etc. So we'll have this capability right from the beginning.

Can imagine that it's looks like a soup. Take a view evenings, and learn some basic PHP I recommend. After that spend some nights on the variable pages. Ryan has done a great job describing the variables. Give your self some time, don't want to much at once. You'll learn step by step. Now Soma, ryan, apeisa and all the other module writers are learning me OOP due to the fact that they comment their scripts most of the time very well. So i recommend when you start writing scripts, comment all what you're writing, what a variable is, what it does or just what you don't understand.

<a href="http://blog.mobilitika.com">Blog</a>

While it may be okay to do once in awhile, I would avoid structuring your site in a way that requires uploading the same image in multiple places. Instead, pull from the source page via the API and use the image. An example of this would be a site structure like this: /about/ /contact/ /press/ /history/ Lets say that you want all these pages to have the same header image. Rather than populating a header_image field on each page with the same image, populate it on just your /about/ page and let the others pull from it. Even if all the pages use the same template file, you can achieve it with this: $image = $page->header_image; if(!$image) $image = $page->rootParent->header_image; if($image) echo "<img src='{$image->url}'>"; The approach here is to give each page the ability to define it's header image, but make it optional. When it's not populated, it grabs the default from the root parent page (/about/). But lets say your structure is a little deeper than that: /about/ /contact/ /directions/ /press/ /history/ In that case, you may want to have it inherit the header image from the nearest parent that has it defined. So /about/contact/directions/ would show the header image from /about/contact/ (if it had one) rather than the one from /about/: $parent = $page; do { $image = $parent->header_image; $parent = $parent->parent; } while(!$image && $parent->id); if($image) echo "<img src='{$image->url}'>"; There may be other cases outside of the example above where you might have the need of using an image defined on another specific page. In that case, use a page reference field. You might call it header_image_page. It would essentially say "I want to display the header image from that page". This is a little better than a direct file reference because your image will still work even if the source page changes it. $image = $page->header_image_page->header_image; if($image) echo "<img src='{$image->url}'>";