Pete

But surely the problem with doing the on the fly is that they're done every page load and affects the user's experience when browsing the site if a thumbnail is to be created on the fly as well? Or am I not understanding this correctly (far more likely ). I think the idea of a config setting where you can set options when creating the field could be the way to go.

My pages started n the 5k's - looking at the database on a fresh install, page 40 is the guest page, then page 5802 is test-role. It just looked a bit of an odd point for the numbers to jump at. It's not really an issue, just looked a bit weird in the DB

When I create a page in 2.1, then go back later on (because of a typo for instance) and go to the Settings tab to change the page name, it doesn't save my changes in PW 2.1.

Just for info, this works and saves the dropdown if you use ryan's amended preg_match line in the module and you're interested in a key -> value dropdown list. One future improvement I'd like to see is if there could be a setting to force the user to select something from the list, otherwise the page will throw an error message when saved. There are plenty of times when you want something to be filled out and select lists are no different. Only trouble is I wouldn't know where to begin with that. Yet. I'm learning slowly but surely

This isn't a bug, but the page numbers in a PW 2.1 installation suddenly jump from low numbers to 5000-odd. I'm guessing you were testing it with lots of content at one point ryan and then didn't reset the auto_increment in the DB? Like I say, not a bug, but it is a weird jump in the numbers.

Love the module - soemthing similar exists in MODx where page links (in the old version) are written as [~7~] and translated on the fly (possibly the cached version has them converted to real URL's - can't remember). I think the TinyMCE alteration would be the way to go if at all possible as it's then a built-in solution. For now though it wouldn't be rocket science for me to do a search and replace in the database to simply strip out any mentions of /pw/ in the fields, just thought it was worth mentioning.

Hi chaps I was just having a look at importing some content from another site (excellent examples of how to import images on the forums here as well!), and I noticed that in the PW database itself when an image is inserted into the body there's an alarming path involved. For example: <p><a href="/pw/site/assets/files/5812/sailing.jpg"><img src="/pw/site/assets/files/5812/sailing.212x0.jpg" width="212" height="141" /></a></p> On my localhost test server the site is in a /pw/ directory, but if I pushed this live then the image links would be incorrect (they would obviously just need to be /site/assets/...). Does PW somehow take this into account when a site goes live and the folder structure changes? On other CMS systems I've used it would just be a relative URL as well, so no / at the beginning and rely on the user to set the base_href in the head area of the HTML template which is a bit more reliable if you're testing at one address, maybe having to test on an intermediate server as well with a different URL (unlikely in most cases but it can happen depending on the client) and then finally going live on the actual final domain.

I've used jCrop on a project myself - the project itself is here: http://code.google.com/p/jcrop/ and I think if you download the package it does have the examples to play with. It is very handy and would be a nice thing to add to the image insertion process currently available in PW. I guess that it would be best to have some per-template configuration options for this though (if that's actually possible) as for some sections of a website you might want to restrict the dimensions to 16:9 or 4:3 to make all thumbnails on a page appear uniform, whereas on others you might want other restrictions or no restrictions.

I think you've pinned down my feelings exactly. I like X-COM, that's why I ended up building x-com.co.uk (which eventually transformed into StrategyCore) and it got to a point where I spent more time on the site as it was more rewarding talking to the site regulars and working on the site than it was playing the games. It's all taken a back seat to "real" life though in recent years, but if some part of my real life still involves building websites for others and maybe making some money on my own projects (your own are always the most fun, especially when there's a good community) then that's not a bad trade at all.

It's a good idea ryan, but I agree with slkwrm on this one - on a lot of sites I've worked on I'll format dates differently for different things. News articles on a site's homepage tend to get a long version of the date (Wednesday 20th July 2011) whereas on the same page I might have a little list on a sidebar pulling just page titles for "last 10 files uploaded" or something whereby it would just be the title and a short version of the date, so the date format would be 20th Jul '11 or something like that. I have seen it in forum software where there are config settings for both occasions though, so a config setting for long date format and short date format and to be honest that might not be a bad way to go as the majority of the time I'd only use two different options.

Thanks man - if you ever feel like turning back the clocks to 1994 again, you can now play the original X-COM on Windows 7 pretty easily if you grab it via Steam. Bizarrely, although I'm the guy who built the site (structure and a lot of the content - can't claim to have written all of those articles though!) I also have little time for gaming any more and when I do I prefer to dive into an FPS for an hour or so just to unwind, so it's Left 4 Dead or Team Fortress 2 for me nowadays. Most of the time it's web development though, which I like to think of as a puzzle game

I was dragging them from the list of images further down the page - so upload one, save the page, scroll down to the images beneath the other fields (I'm on the default PAge template here) and drag a thumbnail into the editor

Yup - it wasn't a major issue for me, just a little unexpected.

That's good to know. Just another quick on on picking a username and password when installing - when I typed in the password it was a normal input field and not a password one (as in the password was displayed in plain text). Not sure if this was in v2 or v2.1 as I've installed both in the last 24 hours, but it's worth double-checking that code just in case - the stupid autocomplete built into Firefox picked the field contents up right away and stored it so that's not good.

It gets trickier than that with other software - the majority of forum software allows some symbols as well and even character codes to create funky member names in some cases. Certainly uppercase, lowercase and numbers are the norm from what I've used in the past.

Off the top of your collective heads, can you think of any reason why I shouldn't upgrade jQuery and the jQuery UI to the latest versions? I'm in the process of looking at cobbling a new image/file upload module together and incorporating this at the same time: http://aquantum-demo.appspot.com/file-upload - the requirements for that are that it needs jQuery 1.6+ and UI 1.8+. The plan is initially to see what I can do on a per-image basis (each image is separate as per the current setup) with a view to possibly expanding it so that you can upload multiple files at once. The thinking behind trying to incorporate something like this is to be able to handle larger files better. Some people who are editors on sites I've worked on don't know much about image resolution for instance so would upload a huge photo - ProcessWire 2.1 can now set the maximum size of course, but without some sort of upload progress bar some site content editors get confused, think somethings broken and click off the page before an upload is complete. Also, for large files uploaded for a file repository, it's just a handy tool. I quite like the uploader I linked to as it doesn't appear to require Flash and seems quite streamlined, however I'm also tempted to try and get Uploadify working this way as well. Future expansion (assuming I get the basics sorted) could include a modal box for uploading multiple files (closing the modal would update the image/file list - it works pretty well in my imagination) but I'm getting ahead of myself again.

No worries. Just thought of an amazing use of the page fieldtype - just for reference the site I'm tempted to convert to PW at some point is http://www.strategycore.co.uk - pretty much everything there aside from the Forums and Files sections is run on MODx with a bunch of custom snippets and templates - specifically the Articles and Databank parts of the site which at a quick glance at I'm sure you can see how simple it would be to do the same sort of structure in ProcessWire (took me a LOT of coding of snippets in MODx to get everything playing nicely together). Since a lot of the pages reference each other, this is ideal - behind the scenes is a section for Companies, and for each game it references companies for Developer, Producer etc, and similarly in the Articles section each article has a field for which game it's associated with and so on. I'm getting a bit excited about the possibilities, but lack of free time and other commitments mean it'll be a while before I realistically get time to look at setting up a PW installation to move all of that content across. Hopefully I'll get the chance to get stuck with it on a commercial project first - probably wiser if I start with something less complicated anyway to get my bearings!

Wow - thanks ryan, that video looked awesome - as you say not exactly what I need just now but every new thing I see about ProcessWire gives me ideas for use in other projects and makes me wonder why other CMS'/CMF's haven't thought about things like these before. Not to boost your ego too much, but so far it's like you're reading my mind before I've even thought of the next problem. It's almost creepy :-\ ;D

Just another quick thought on images in pages - having one image per row in the editor keeps things nice and clear and allows for a larger description field, however if you're whipping up a page with screenshots on it for example and have 40 images it's a lot of scrolling down. What are people's thoughts on having it as 3 images per row or something like that? I know it's not as easy as all that and would require some code changes, especially in terms of dragging and dropping to re-order them, but it might be a more useful default. Just my opinion but I'd be happy to hear yours As you might have noticed from my posts I spend a lot of time thinking - "what would the end-user think?". Makes you come up with some silly suggestions sometimes, but end users are a silly bunch sometimes as well

No worries. Although I realise 2.1 isn't "final" yet, a simple alteration to avoid confusion would be for the message to specify that you can't use uppercase letters as at first I thought I'd got a space or other random character in the username before trying lowercase letters.

I think in the first instance what I'm going to be doing is running a PW site alongside Invision Power Board. In this case I don't have to worry about duplicating member names and IDs in PW as they'll never change in the forum software, so literally all I need to be able to do is start typing a member's name and have autocomplete do the hard work of getting username and ID from the IPB database, storing the user ID in a plain text field in PW. I'll have a tinker and see what I can come up with, but it might well take me some time to get used to PW since I only downloaded it yesterday

Hi folks Just a couple of quick queries regarding field types. Firstly, is it possible to have a select dropdown field where it gets the select options from the results of a database query? If so, could someone point me in the right direction as to how to go about it? And secondly, for datasets that are quite large you could end up with a MASSIVE list the above scenario becomes less practical, so has anyone thought about how you might do an Ajax input field whereby you start typing someone's name for example and it does one of those nifty autocomplete thingys: http://docs.jquery.com/Plugins/autocomplete - the obvious issue here is how you then save the key (in this case I guess the user ID in the external database) to that field. These are just tow examples I can think of that would be very handy if they don't already exist, and in both cases I'm thinking specifically of an example where it's querying a non-PW database (trying to make different systems play together - specifically I'd like to query some fields from forum software if possible).

Okay, just tested the original issue I was having in PW2 and just installed PW21 and I'm experiencing the same issue. I thought when you inserted an image into the page content and scaled it down it was supposed to create a separate thumbnail (I could be wrong)? Whether I link it to the larger version or not, it still doesn't create a separate thumbnail image which I think it's supposed to. The attached screen shows that the thumbnail (after I saved the page) is just the large image (600px wide) scaled down via width and height attributes. For info I'm testing on XAMPP.

Okay, so it's not the end of the world or anything, but when I installed the latest version of v2.1 it complained when I tried to create a user account that had uppercase letters in it. Any chance this could be made a little less strict - it let me type my name in v2

Hehe, dunno why I even tried doing that but I did and when it worked I assumed it was intentional It's certainly something else that's a bit cool to show off to clients and, more importantly, potential clients - they love the flashy stuff even if it's not all that important.