Pete

Funnily enough I was thinking that this would make a good module the other day. There are instances on larger sites where you are likely to have many templates and not add other user roles til the end, so a permissions matrix would come in handy. Where I think it would be even more useful is in conjunction with the module that allows you to give per-page access, but every time I think about how that might work I get a major headache. I need to mock up some examples of how this might work. A template permission matrix is a far easier prospect by comparison.

My fingers must be like sausages today - so many typos on various forums

Hi folks Anyone who's tried logging in for the past hour or so will have seen a message saying we were upgrading the forums. Unfortunately everything that could go wrong did go wrong, but I've put everything back to how it was now and you can discuss ProcessWire once again For those that are interested, what worked fine on my local copy simply failed to work when I tried merging it with the liver version here - something to do with the merging routines in the new version of the forum software and/or something I've overlooked. I'll re-visit it at a later date and, having learned my lesson, I'll try and get it working in a sub-forum on the live site before taking the forums offline again. Apologies for the interruption!

I agree with pretty much all of what he says and wonder if we should be checking for any topics with zero replies? I could run a query sometime next week I suppose (busy this week).

Well that would depend on your time, but what sounds silly to me is porting it all to ProcessWire as an "alpha" which would work perfectly well, then translating all that to an entirely different programming language which presents different problems - you're essentially first building it on a framework that helps you in certain ways, then throwing it all away and writing it from scratch, including all of the user and page management features etc that ProcessWire gives you out of the box. The short version of all the above posts is: You will likely need to rewrite most of the code in these modules You will need to know how to do this yourself (i.e. have a decent grasp of PHP) You will need plenty of time to do it all in - I say a year as if this was me working on this for myself and not for a client I have time constraints during the day and less time during my evenings and weekends that I would be working on it. Either way it's no small task you're embarking upon and there's no easy shortcuts to getting there, but ProcessWire is a good system to build many web applications in Doing this all and porting it over to Ruby as a version 2 sounds silly. Stick with one or the other from the start. EDIT: In fact your last question is worrying - combine ProcessWire's flexibility and UI with Wordpress? That is also frankly silly. At one level they are both CMS' (Content Management Systems) and duplicate each others' work, though ProcessWire is arguably the better choice, certainly to those of us who use it. What you are suggesting now in terms of a car analogy would be called a "cut 'n shut" in the UK (and probably elsewhere) - taking two halves of different cars and welding them together. It's possible (illegal in the case of cars ), but... why?

Now I'm stumped. So you're going to port a lot of apps over to ProcessWire from WordPress and, if that wasn't going to take enough time (several months of your time at the very least, if not a year), you're going to ditch it eventually and port the whole lot over to a completely different programming language? Are you sure you're not pulling our leg with this because I've got little time for jokes that waste people's time here. Not trying to sound nasty, but what you're suggesting sounds a bit silly and that's just the way it is.

I think there are a few things to bear in mind here: You will need to know a fair amount of PHP to proceed. No CMS will allow you to simply port functions from another CMS by replacing X with Y - the functions will usually interact differently with the core code. A clumsy example is that it's essentially like taking wheels from a quad bike and trying to attach it to a monster truck - yes they're both wheels but they are incompatible and there will be a lot of effort involved in making them work together. It may well be easier to add your required functionality to the shopping cart module diogo mentioned: http://modules.processwire.com/modules/shopping-cart/ - again though you will need to look at that source code and be able to code PHP to continue If you're happy coding PHP, there are several topics to help you on your way to understanding ProcessWire modules Firstly, read up on the documentation on the site - you will need an understanding of how the system works first: http://processwire.com/api/ Next there is some useful information on creating modules here: http://wiki.processwire.com/index.php/Module_Creation and here: Finally, the cheatsheet is handy to have to hand: http://processwire.com/api/cheatsheet/ Let us know how you get on.

Ditto from me to all of the above. I've visited a fair few forums over the years and I've not seen another software-related forum as friendly as this. It definitely has to do with ryan always reading and helping out on the forums from day one. I agree with Soma that there will come a day when ryan can't read or offer code examples in every post and that's when people start getting more selective and eventually you need Moderators for different forums that are fairly specialist in those areas (I'll moderate the Pub forum ) but we're a way off that yet and it's good to see that the friendliness and helpfulness rubs off on new members and everyone helps each other out where they can. The trick is that no matter how fast or big the forums grow, we need to maintain this sense of community - so far it's working just fine!

The idea behind the jobs forum is for anyone looking for paid development work to post their requirements in one place and for developers to get in touch with them. Any project can be posted, whether it's custom development work, website design, or complete installation and setup of a website. There are a few guidelines that are useful to bear in mind to help things go smoothly: Give a good amount of detail about the project so that prospective developers know roughly what will be involved. If a project requires an NDA for any reason, try and give non-specific details such as the type of development work involved (module development etc). Let people know how to contact you - if no contact details are given, people will most likely PM you on the forums here. If you have a requirement to work with a developer in the same country as you, please mention this to narrow the field of applicants. If you are happy mentioning a budget in the open, this is also fine but not required.

I added the forum and one other: - I may even find time to move some topics around

If you point me in the direction of those other suggestions I can do them all in about 5 minutes. I'm struggling to keep up with all the new posts made here daily at present, but I'd be happy to oblige with some new forums! EDIT: Ah, guess one of the others is this: http://processwire.c...page__hl__forum I've added Module/Plugin Development as a sub-forum of the existing Modules/Plugins forum (made sense to me) as well as adding a Jobs forum which I think fits just above the Showcase and Pub forums. Any more?

It's pretty well tested up to many thousands of pages, but you wouldn't actually want to output thousands of related pages into the page (or bring them into memory) so you could change Soma's find-> selector examples to have a ,limit=5 on the end, sort by newest to oldest (get the latest 5 related pages) or even grab a number of random pages. Putting a limit on it will pretty much write in the SQL behind the scenes that you only want to get X results so it works the way you probably normally would if you were manually writing the SQL yourself. I wouldn't worry too much about it - it's very well put together, and you can always test using Xdebug or something if you're still unsure.

ryan - congrats, and this is obviously the only sensible way to be in two places at once:

That's what we were talking about with the site directory

Perhaps there could be a FormBuilder form set up to begin collecting these before the Site Directory is built? Seems like a case of setting up the form and then using the publish to page option here:

Can I just say that if ever there is a book written about how to use ProcessWire, this should be the foreword - it's perfect! I did fail to read it in the suggested accent and read it in an Austrian Arnold Schwarzenegger accent - it was amazing (like this - http://bit.ly/c7op9H ).

diogo - I love opening that one in my browser then resizing it smaller. They've got a lovely effect when it has to switch between the larger images and the mobile ones - it seems to load a little loading icon then brings up the smaller images. I'm going to snoop around the source code Probably the nicest looking example I've seen of responsive design.

I think that whilst on the surface this sounds a bit like a coding headache I can see various different workflows working for different scenarios. The way I think that this would work best is with either a matrix permssions module (a bit old-school) or a visual workflow permissions editor so you can really tailor the permissions and approvals based on your own way of working. What I mean by that last bit is a bit like how Lemonstand e-commerce handles discounts - you set the conditions (in this case I guess which parent in the tree you want this to apply to the children of) and what happens when certain conditions are met. Here's a quick example of Lemonstand's system - don't bother reading it all but look at the screenshots for a rough idea of how you set these things up: http://lemonstand.com/docs/shopping_cart_price_rules/ Obviously the PW version could be done easily with an ASMSelect menu to select the parent or a certain page template or a custom Selector. Just thinking out loud.

Nice one!

Love it. The clouds don't move for me in Chrome or Firefox on Windows 8 but they do in Safari... albeit very jerkily! Whether they move or not isn't essential though since it's the content that counts and the focus should be on the screenshots. I'm seeing both sides of the argument (not that anyone's arguing) on having the Futura admin theme on the homepage - I wonder if these three areas should be some sort of slideshow instead? Perhaps the middle panel could start out as the default admin theme - if only to match the colours - and then fade through? It's a tricky one as all the shots show off the admin or a module, but I wonder if somehow it needs to show what you can create with ProcessWire too as Tripsite and VillaRental from your site sold me on ProcessWire ryan!

There have actually been talks of a non-Mediawiki documentation section for the PW site, more because Mediawiki is a pain to administrate and upgrade and is easily spammed. I think the biggest hurdle to overcome is that I can't see it working without version control for the pages if you are allowing anyone to edit pages. It would be nice to be able to roll back spam edits or even have the ability for certain people to approve changes to some sections I think.

I always check Fontsquirrel first as it has a lot of good free fonts. Failing that I check some of the others linked to above but if I have a specific font in mind that's not on any of those sites I'll buy the @font-face kit from myfonts.com

Pass as to why those links don't work by the way ryan - no matter what I do to them it doesn't format properly

Regular expressions are like a different language to me I'm much more comfortable with regular espresso's You threw this in to trip people up right? This sounds made up (but I'm certain it isn't ).

Well I've made a start on one for real estate (a slow start) and already come to the realisation that needs for this profile in the UK and USA will be different as well as in other countries. The good thing is though that we're not talking about a module or a plugin from some other system - it's just fields and templates for now - so as long as I comment the relevant areas properly it's easier than any other system to alter the fields and customise it all.