Pete

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.

Stop the development please, I want to get off This reminds me that I really need to start thinking about translations when I do development myself, so I'm making a mental note and following these topics with interest.

Gravatar support would be cool. I think I've seen it done somewhere else that it links to Gravatar based on the email address and defaults to a pre-set list of icons otherwise so you're not looking at the same boring silhouette or "no avatar" text. Something like that would be as simple as adding a default avatars folder and picking one at random and could make it a bit fun. To see what I mean, scroll to the comments here and you'll see a bunch of stand-in cartoon avatars for those without one: http://www.rockpapershotgun.com/2012/08/28/rome-sweet-rome-crusader-kings-ii-expands/ Maybe not a necessary feature, but certainly an easy thing to code to make it as easy as dropping some images into a "default-avatars" folder to have it select one. If I had to guess, I think it might select those from the site above based on the square root of the member ID rounded to the nearest whole number or something like that, since they are the same for each person every time you load the page. Anyway, I've babbled on about that point enough. Spam protection - stopforumspam.com would be a good option if it's not in already, but there are others as well. The obvious issue is the more that you check against the longer it takes to query. Maybe when PW is a lot more mainstream it could even go down the route of a PW-run central anti-spam database like these forums have (run by IPB and spammers marked as spammers by site owners). Of course that requires manpower that's not available at present and the database would be very empty to begin with To prevent double post even without a redirect could a unique ID just not be sent with the form submission? I guess like on the forums you might want to say something in addition to what you just posted so it would be good to check if the content of the new post is the same as the old post and if not then append it to the previous post. I don't mean post, I mean comment Textformatter plugins - are we talking about support for Markdown and the new BBCode one you've done? That would be fab. I think that's all my thoughts for now. Brain tired, sleep imminent. Oh wait, it's only 1.45pm

Love it - I always like those well-laid-out menus like when you hover over the services tab. They can obviously be messy, but when they're done well like this it really helps navigation.

Don't think you can easily and that's why he's asking Ryan.

I love it when a plan comes together.

Hi ryan I'm using this to send a form to an email. I've got a couple of fields that are textareas, but I'd like the email to include the newlines I enter in the textareas - currently it seems to strip them out and put them all on one line. Is there a way to have it preserve newlines after submit?

I think the drop-down menu would make sense, especially if it can be added to with further modules. Maybe it would make sense if the select box uses "optgroup" tags so that each module's actions stand out separately?

Okay, I updated this to 1.0.1 to search recursively for files under the /site/templates/js and /styles folders - this is available from the modules directory as v1.0.1. I thought I'd work on v1.0.2 which lets you specify starting folders further up the tree whilst I'm at it but have hit a snag. It works fine, but when you change the path and hit save the drop-downs don't update their path unless you save the module a second time. Anyone have any ideas why you'd need to save the module twice for the config page to be able to use an updated value?

Go to edit your field and under the input tab of the field change the "Input field type" from Select to "Page list select". Tada! You can now browse the page tree On the same tab you can also set the page parent to restrict the list of selectable pages. If you have an awful lot of pages and you're the only one maintaining the site, or other people know what's on the site, you could also change the input field type to Autocomplete (can't remember if you have to install that FieldType module first or if it's in by default nowadays). EDIT: I need to type shorter replies so Soma doesn't beat me to it

Can you point us in the direction of their license page, or copy and paste it here?

Hehe, well they're a bit old school for me as I'm 30 Here's what's coming in the next version in terms of the editor: http://community.invisionpower.com/blog/1174/entry-7940-ipboard-34-dev-update-editor-improvements/

IE10 requires Windows 8, but I'm looking forward to that as well to be honest. I just wish the way to build tiles and stuff on the Metro interface was HTML5 and jQuery and not the uber-complicated system they've developed instead.

Hehe, it's easy to set a group policy to update computers but a bit more hassle to get it to install FF or Chrome and set it up as default browser. Not impossible I know, but just not got around to it yet.

I think they take time to build up a lot of bug fixes and release the next incremental version every month or so. Whilst I prefer PW's style of being able to download the latest version of the repo to get almost instant fixes I can see why they do it like that. I just hope the next version resolves some of these issues.

How long was the text on the post?

I might see if there's another editor option but I doubt there will be as it's not as easy as PW to change things like that. The editor can be turned off completely via your profile settings and you can use BBCode instead, but that's not an amazing option - might be better for people used to other types of editors though?

Well tough Smileys/emoticons are an easy fix - we can manually add conversions so they will work, though it is not standard to have a hyphen in them and I've used a lot of forum software - more standard without. Like I say though this can easily be solved by adding more variations in the admin so that is neither here nor there. Indentation is an annoying bug. It's on their list of things to fix. Seriously though? Neither of these are showstoppers and no software is perfect (apart from PW). Various editor improvements are coming in in v3.4 so I suspect a lot of the little quirks will be fixed then. It's interesting to note that the editor that you guys don't like is ckEditor (I think - might be TinyMCE even) but there are indeed quirks with their custom implementation. Compared to the previous software though I think it's a lot more useful overall. In summary, it would be a huge pain to switch again and the alternatives all have their own issues, bugs and drawbacks so I don't think either issue is enough to even consider it.

I've used closest() a few times rather than parent()->parent() repetitively, or if there was ever a chance the layout would change slightly on the page but I knew that somewhere back up the tree a particular element would always exist in relation to the current one. It probably wouldn't be used all that much in PW since another layer of pages would rarely be added between the current page and the parent page, but saying that I'm sure I've run into this before myself so it may as well go i and I'll try and find where I've seen that code where I needed to do something similar. A bit off topic, but ryan: have you at any point emailed anyone at jQuery about PW? I think they'd be interested in the concept