Pete

Paypal is reasonably straightforward to implement from scratch from what I remember dabbling with the basics some years ago - their docs were pretty good at the time.

This would assume they can get into the database in the first place in which case it's probably game over anyway... Not sure how I feel about this as it would be better to educate people about various attack methods than obfuscate table names for some sense of security that I'm not convinced it provides.

You went away for five minutes and it's like we all went hyper. Welcome back!

Love it! It's a different way of always having easy access to the tree and not losing your place. The way I was thinking of last week was having the page tree in a sidebar area a bit like MODx but this works better with any size of website. Now slow down, you're making the rest of us look bad

Depending on whether your products have variations like size and colour (clothing and such) or not that would determine for me whether to use PW and FoxyCart or something specific to e-commerce. The problem is that you could end up with 5 colours multiplied by 7 sizes and have different weights, costs and inventory for each, and there are more complicated examples than that - that's something that you might want to turn to specific software. If on the other hand you're dealing with simpler products like books or other products that don't have variations (or certainly don't have many) then PW and something like FoxyCart would be perfect.

Not a bad idea. I am aware that there are already a lot of forums and maybe better ways of organising them so I've got a doodle I want ot run by ryan before adding too many more. When I said coding examples for download, I just meant if someone wants to use the starting HTML-only template and integrate it rather than starting from scratch and typing every example in the book. Just thought it might be easier than having to type the HTML as well.

I think the Cheatsheet should also be in the book. Not sure quite how to lay it out but I have seen other examples in other coding books so I'll have a look as there will be something sensible. Maybe we can have a pull-out poster (someone suggested a tea towel the other week which isn't a bad idea ). A book can also be used well with downloadable examples - you could quite easily tell people to download the software, grab some example files that have the bare bones of a HTML template and get them to integrate a basic HTML template (separate from ProcessWire) into ProcessWire. Maybe the best example is to have a basic 5 page website currently built in HTML that has a basic contact form (doesn't need to work) and a basic gallery, and then integrate it with ProcessWire. My thinking here is that the majority of people who know how the basics of HTML and CSS will be used to working with a template of some sort and will want to integrate it with ProcessWire. That's an idea anyway. It's certainly my starting point for any website - built the template in HTML and CSS and then integrate it with the CMS. The start of the book needs to be thinking of the chapters and contents of each chapter and build it from there. Once that's decided upon you can fill in the pages - easy I agree that linking to PHP.net pages is a good idea if we think there are areas that people should or would like to read up on more that they get linked to in the sidebar or whatever.

I dislike BigCommerce solely on the grounds that I used Interspire Shopping Cart (the self-hosted version) where they treated us all like crap and strung us along for a couple of years with too few updates, show stopping bugs in many releases and eventually abandoned us to make more money on BigCommerce. Their forums were the polar opposite of these forums which just shows you how much of a difference it can make when you listen to your customers and aren't solely focused on making big bucks no matter the cost. Long story short (too late) I wouldn't trust them not to get distracted with their next money making scheme. Their forums (which I think are closed to non-members) are a damning assessment of their disregard for customers (by they, I mean management - there were some excellent support guys in there who were sadly stuck in the crossfire). My rather negative post here is nothing compared to the content of those forums so steer clear would be my advice.

I'd like to nominate myself as an idiot involved with the book In what capacity I'm not sure, as I often fail to finish what I start in a timely manner when it's not generating income. I have InDesign which I would see as essential to getting it into a publishable format for PDF and print, and I'm sure there must be a standard page size for both Europe and US (thinking ahead to getting copies printed on an as-needed basis using online publishers). I think this has digressed enough to warrant its own topic. Perhaps simply a Documentation forum would be a good idea that's purely for discussing documentation and not getting mixed up with the Tutorials or Getting Started forums - just thinking there are a lot if discussions to be had around writing a book!

I want a full-blown "Getting Started with ProcessWire" manual. I don't think I'm thinking too far ahead either - take a look at the MODx manual for example: http://modx.com/learn/modx-books/modx-the-official-guide/ - anyone who's used MODx can see that by looking at the contents pages it covers each aspect of the system nicely. I daresay that a similar approach with a PW manual would be easier to write since it's easy to use and explain - I also wasn't joking when I said somewhere else that Joss' overview of pages should be the first page anyone reads. In terms of what documentation would be useful, I honestly think it would be sensible to think of it in terms of a book that takes you from complete beginner through to basic and intermediate examples. Once you get into the advanced modules and scenarios you're often outside of the scope of normal documentation as you'll be talking about something very specific and that's where the forums help immensely. Perhaps with enough advanced tutorials there's scope for a second manual for advanced usage? I'm all for the idea of a manual that's downloadable via PDF and that can also be bought online pre-printed. What do you guys think? Sorry, going way off topic now Should we at least think about a contents page to get the structure of what people think is useful to learn in one place? (Apologies if this is already on the WIKI - typing at speed on my phone).

It'll be because $page is always the current page array so I'm assuming that diogo is correct and you're echoing $page->body somewhere below that and it's getting confused. Your solution to change the name is correct of course - it was just getting confused as you were causing it to interfere with the original pagearray for that page.

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