Pete

In fact, wouldn't a very basic way of doing it be to simply have a version, author and datestamp field added to every field table? Or am I over-simplifying things? Could perhaps handle file/image field (and others) versioning simply that way too. That would add some overhead though I guess on larger sites by leaving versions in the same tables though now I think about it. Oh well, I'm sure you'll come up with a good solution.

I really like the sound of that. I would still suggest putting in an option to revert the whole page to a specific date as well, just because that's what people are used to with version control, but I like this method a lot as there's no other system where you could really do it this way without it being really difficult. I'm not saying it would be easy this way, but since all fields are tables already it sure makes it a bit simpler than it could be.

I did have need for a few things like this and it did take while to wrap my head around, but as long as the benefits are explained it's not a problem. I would put it into context and explain that if you added age ranges (assuming you were collecting user stats during sugnuo or doing a quiz or something like that) then you can use this with selectors to pull simple stats. The benefits aren't always immediately obvious as you might not have need it using such a simple field with selectors at the time you create the field, but the flexibility it offers if you do need to do something like that is amazing.

I think in this case you probably wouldn't have those two fields at all. It almost sounds like a case for putting any pre and post content code in the template file instead if it's not going to change much? That's fine of course unless you want to use those fields to have slightly different content on a per page basis? One of the things that is quite different coming from MODx that I found was that you learn that creating many templates for different content in PW is a great help whereas in MODx it became a bit of a chore I found as it just wasn't as easy to assign fields to templates. Not sure if that was of any help And then I re-read your post and you are trying to do it on a per page basis. Ignore me

I love everything about this post but also wanted to say I'd not seen such lovely icons for flags in different sizes before as the ones you've linked to at icondrawer - nice!

I keep meaning to mention something I've seen in a CMS I used about 8 years ago (feel old now) that was pretty bloated. They had a cache that basically cached the parsed field contents for a page into a text file. Versions were simply stored as that page name with a date stuck on the end as the filename, and the system fed through the latest version and handled it that way, keeping X versions. It was simple but it worked and didn't put unnecessary amounts of data in the database that way. Probably not the route we want to go, but I'm wondering if we might be trying to over-complicate versioning - there's certainly a worry that it could add some serious overhead to the database even for the slightest tweak (probably why Apeisa's idea of versioning fields that have changes rather than the whole page sounds appealing).

Ah right, that will teach me for rushing to read a post and not doing it thoroughly

There was an issue a while back with cloning repeaters that has since been fixed. Are you using the latest version?

Neat - good to know.

This was the info was trying to find - thanks ryan

Good stuff Ryan - you're thinking of everything!

That's where I was getting PNG from jacmaes, although it's not obvious unless you know where to look. You can also save the resulting image as a PNG if you wanted to. I remember back in the good old days where I auto-generated PNG article titles using PHP and custom fonts before any other options were available - those were the days

Well obviously if you've got the luxury of having a stack of real devices this doesn't make sense, but not many of us do. I'm curious as to what way they differ from the real devices? Aside from the obvious ones of on a large screen resolution they sometimes look far bigger than the real device screen (some imagination has to be used there).

Well then you have to have a list excluding "the" and so on. If I find the article with the solution I'll dig it out as I'm fairly sure it lists all the pros and cons as well.

No problem - any time

I had to refresh it once or twice to load the new styles.

Yup. Probably not the best way to go the more I think about it, plus it might suggest the forum support isn't the best, but it I'd probably the best support I've ever had with a software product.

Nice updates, my only thoughts are when opening some elements it switches some blocks to different columns - I guess this is simply to keep the column lengths more or less the same length? Is there any way to turn that off as I'm not sure the animation/reordering is necessary and could be a bit confusing even if you use the cheatsheet so much you know things are supposed to be in a certain column. Certainly not a big/important issue

That must have been a momentary glitch as it works for me now too. It definitely wasn't for a minute though.

Cool - finally back at my PC now so I can play with this!

I'm coming in very late with a reply here, but when migrating it's always worth deleting the contents of the site/cache folder just in case anything got cached that could be causing interference in some way.

Obviously I'm adding my 2 cents weeks later as I'm catching up on topics I've not read, but I had a similar situation with images. The scenario was a gallery where the client wanted to add new photos over time, and they obviously wanted the new photos to appear first without reordering them manually, so the solution was: foreach ($page->images->reverse() as $galleryimage) { // code here as normal Pretty sure you could use foreach $page->children()->reverse() as well, but might not be suitable for this particular scenario. That said, the info might be useful to others so I thought it was worth posting.

We can actually change the three letter word check - I think it's actually a built-in restriction of mySQL more than anything. ryan - do you think it's worth making it possible to search for three letter words on the forums? If so I can certainly dig out the solution as I had to implement it elsewhere last year. The only downside is that on very busy sites this can add overhead when people put the word "and" in the middle of a search query and it goes off to find that word, which must appear in most threads which is the reason I think mySQL uses four letters as the minimum by default.

Mats - love this one as it's a nice simple layout (didn't realise you could customise Twitter Bootstrap until now!), and like the ability to view the background image too! Very neat

I agree with ryan on this one - maybe the City website could be re-done by you too (just followed the link at the top-right)