Pete

In all seriousness, you wouldn't want support tickets without some sort of paid support system otherwise you end up answering the same old questions but just behind closed doors where nobody can see them. Business Class support isn't a bad idea though for folks who are making a living off building websites and need that level of support.

There should be an option to attach a file to a post in the forums - that wil allow you to attach the image.

This should give you the answers - its worth reading it all, but specifically steps 4-6 are what you're after:

@Adam I did think the same thing - coining new phrases when most of it is common sense and achievable already. It sounds really like you could achieve the same results with ProcessWire. The majority of it is a case of ProcessWire being your CMS (level 1), the client, designer and developer working out a good structure and easy to use desgn, some newsletter signups for things like MailChimp which are easy enough to do (level 2) and then level 3 is mostly Google Analytics to be honest. The bit at the end of the video is quite cool, and would be possible to code for ProcessWire definitely, but I would question whether most people need it. It depends greatly on what your business is as to whether you need that much information about your visitors' every move.

What I would do is set up a page called Client Area or something like that, and then for each child page immediately below that use a Page fieldtype that allows you to select the user that can access that page. This way, in the Client Area page itself you can restrict it to only show pages for a specific logged-in user and stick the rest of their content under the relevant page. I would have a custom login form on the Client Area page that then simply redirects them to the right child page on successful login. It would also have some logic so that they can't jus force their way into another user's content. It does depend a bit on the structure you want to give for each user but the sky's the limit with ProcessWire. I can't go into more detail as I'm typing this on my phone, but that is one option that would be relatively straightforward if someone else comes along and fills in some of the blanks (I'm sure someone will, they're good like that).

I'm always keeping an eye out for new icons, but for interface design I've relied heavily on Yusuke Kamiyamane's Fugue icon set. I think I first found the set back when there were "only" around 2,000 icons in the set, and now there are over 3,400 and counting. A couple of intranet projects have benefitted from this set, and the one-off price tag is quite reasonable for the amount of icons, including their .PSD source files and variants. Does anyone else have sets that they'd care to share? I know there are tonnes out there, but the real gems are hard to find in amongst the rest.

jQuery UI also means you can roll your own themes very easily.

It's alright I suppose On a serious note, it's definitely a good thing that I can think of half a dozen uses for it already, so good work!

I agree with that guy's generalisations - frameworks are always bad. I hate saving tonnes of time and love reinventing the wheel on a daily basis because I have nothing better to do and love watching the years fly by.

That said, it's not difficult to set up a MySQL database.

ryan - can I request that more fields be searchable? For example: searching for "CSV" returns nothing, but I think it should return the Process Data Import module since it's in the summary text. assuming that that might be because of the 3 character limit on some search selectors, you would think that "ProcessDataImport" which is the class name would return a result also, but it only seems to search the title field which has spaces in between the words. In some cases the class name is quite different to the module title in the directory I think that's all I spotted... for now

The footer link to "download our brochure" doesn't seem to do anything.

You can do this though I think: $pages->find('template=something,sort=-id')->sort('-title'); That selector is nonsense of course, but I'm sure you can do this to sort by two things.

Turns out it did it whether it was a capital or lowercase, so I just changed it to this instead: // this is what it usually is on other forums 8) // this is another variation I've removed in order to play it safe No previous posts with the code in should be affected, but I updated yours to check it works I think part of the problem is that when moving from SMF to IPB it's carried some of this across so there was a mix of two sets of smileys, sometimes doing the same things. You can run a poll if you like but I've done it already

I can easily change that smiley so it only does that with a capital B or something.

Love it. Love the cleverness of the headline too - I was immediately wondering why the full stops were there, but it works well as a sentence and separate statements too. Good stuff!

What's wrong with the Fancybox 2 license? I've not been paying any attention to licenses again and using it for everything Edit: just saw the fact that it requires payment for commercial work (I've only got it on personal projects or unlaunched projects at present). Not a bad price though, but I can understand searching for a free alternative since there are hundreds out there.

This is awesome. I always thought of it as testing two options with massively different layouts, but it makes sense that just increasing a button size or making a slight tweak on one design will allow you to refine an already good design over time. I'm definitely interested in testing this out, and of course you're right that it's made really simple with ProcessWire - clone a page, change its template to a slightly altered one (or just some page content even) and you're away! Of course, the more visitors your site gets the better the test results will be - it would be difficult for a brand new site that only gets a handful of visitors a week, so I think it's more for sites that are already established.

Does GA do the work of loading one of the variations when the original page is requested then? If so then that's pretty cool!

It's short and simple would be my thought. I'm not sure what the long-hand version would be but I suspect it would be a full-on database query, complete with some sub-queries in some cases, so I think the legibility and speed of coding gain outweighs the headache of the long version and the minute saving in query time. Everything's easier when you don't even need to know what the DB structure is

Harder to hit two flies I think

Sure you're not doing my trick of mixing up dec and live sites in your browser's tabs?

Two birds with one stone is the English equivalent, but only cos we're mean to birds I'd like it to be one message too as some pages of mine have a LOT of fields. It might even be sensible to have it as a collapsible div so it just says "X fields updated" and have it reveal the info by clicking on a "more details" link. Just a thought - that way you retain the useful list but could style it in a better way than a comma-separated list on one line - I'm thinking a bullet list.

I think I'm with you there ryan - I use jQuery a fair amount but I never feel like I know it inside out and don't often use the same sort of functions as I would in PW so I'd never really get confused. I often look up jQuery functionality as I need it as it's never quite as straightforward for me as PW is.

PW's database is really scalable in that each field is a table. This is fine, but for comments systems and other cases where you're only going to build the structure ONCE and scale it to millions of entries it can be preferable to have it in its own table. For example, if you build it as PW pages to only have 3 fields - name, email and comment, that's 3 tables (but remember there are other tables that come into play! - the pages table and the field_title table have to be in there for each page!). Sure, it's quick enough since it's still the one query that's getting data from those tables, but it would save some overhead when you get to really large numbers of comments to have it as one table. In fact I doubt the overhead would even be very high with separate tables doing it all as PW pages, so maybe ryan can elaborate on possible reasons to keep it separate.