Pete

Martijn - no, it wasn't that one, it was renobird's idea that thistimj linked to above - I like renobird's solution as it should work with any admin theme now it's a module

I'm going to ignore the field completely and jump straight to shouting: THANK YOU SO MUCH FOR DEPENDENT SELECTS! This is yet another awesome feature I've been silently wishing for for a while - one select field causing a filter on another (which I'm guessing works also for just two regular select fields and doesn't rely on this fieldtype?). Loving how, logically, when the first select field doesn't have a value the second simply isn't shown. Back to the module - I love that too, but one select filtering another one opens up a new world of possibilities so I'm ecstatic with that by itself

Thought I'd step in and show support for this - love the idea as a whole and Marty's hit upon an interesting use case there right away for easily setting up small sections of repetitive content that is a bit more modular perhaps than a site profile and useful when such things are outside the scope of a module themselves. @Soma - I need to pay more attention to the cheatsheet as I'd not seen getArray() - would've been incredibly useful when I was debugging something the other day and print()'ing a page object... which causes a mess on the screen

Well I've maybe made a bit of a bold statement there saying "nothing would be deprecated", as ryan could rip out half of the functionality tomorrow if he was in a mind to cripple the product, but you're right. It's more obvious to developers that because the code is abstracted and human-readable there's less chance of something becoming deprecated, and if there's a way for ryan to overhaul a complex 200-line API function to 40 lines and make it 10x faster as a result at a later date then it can be done without breaking people's websites which is the beauty of it. But as you say, that doesn't help newcomers or a lot of decision-making managers who are checking a product out based on their developer's suggestion. Something could be done to address that - it's just a case of working out how to get it across easily. In fact it might sound silly, but something as simple as a couple of pages like ProcessWire for Agencies" and "ProcessWire for Developers" with the main points for each that are linked from prominent places on the homepage (perhaps even before the first paragraph) could really help - people want to know how it will benefit them specifically. @ryan: feel free to correct me if I've made any bold claims in my previous posts, but I think I'm on the right track about the abstraction and I certainly can't think why you'd ever want to change any of the function names since they make sense.

Don't ditch jqueryui - it's confusing on the odd occasion when I've wanted to override something, but it is as logical as Mr Spock once you get use to the HTML it generates I'll be honest and say I think the biggest hurdle can be the colours. Some people just have an issue with baby blue and pink. It's hurtful I know, but someone has actually said to me that that made it look childish to them (I don't agree, and they should darned well look deeper than appearances, but I can at least step outside myself and see things from their perspective). Back when I worked for another web dev company, being able to change admin colours was something that was brought up, so simply being able to choose colours might help. I'm thinking if that functionality is built in, perhaps with a simple colour-picker for the 3-4 main colours, then that would help. That and some pre-defined colour schemes as has been mentioned. You could save the chosen colour scheme to a CSS file with relative ease so that it's all cached nicely too. I like where all this is going as it reminds be a bit of MODx with the ever-present tree, but like ryan says it's not always appropriate (and not every client has widescreen monitors yet even where this might be a problem ). In a future default admin theme I'd agree with others who have said this and suggest some configurability built in would really help. Things like: Easy way to create a custom colour scheme - maybe save as json so can be copy and pasted to other installations easily? Even a simple image upload field so they can stick a company logo at the top Easy way to select another page as the default admin (not applicable to everyone, but since we're talking about configuration options for the admin this might make sense to have it in the same config page) And why not take it one further and allow devs/agencies to type their company name in somewhere as well as a support telephone number? I'm not suggesting total white-labelling as it's important ProcessWire's copyright stays there and that the system is ProcessWire, but if we can think of a sensible way of helping devs struggling with brand identity to tick some of these boxes then it might well help. I know that branding can be a big issue to big companies, but certainly not all - it might be worth bearing in mind and making it easy so that they're not inclined to be rude and take out the copyright and logo so they've got somewhere to stick their own name and info (seen it happen before years ago). Not all of this will help people who only look at the surface of the product - compared to some more elaborate (read: overly compex styling) CMS admins out there it looks more streamlined and functional to many of us, but that translates to "basic" and "under-developed" to others - and there's no helping those people

Hehe, 3 simultaneous posts (nearly)

The problem is that you can echo PHP variables into Javascript but not the other way around - PHP is processed on the server before it's served to the browser - JavaScript is processed via the browser so it simply doesn't understand what you're doing. In the first example, you've essentially typed " = visitortime" EDIT: adrian beat me to it There are a few different options on StackOverflow, but I like the PHP approach in this one best so far as - whilst it's not foolproof - it doesn't use Javascript so it can't be manipulated by the user: http://stackoverflow.com/questions/1718935/how-do-i-get-a-visitors-time-zone-in-php

Also, the developer showcase idea has come up a few times before, but I think it's one of those things that will happen when someone has enough time. Something like this maybe: http://director-ee.com/ - but with quality control checks (the skills matrix there is based of what people claim their skillsets are, rather than what they have proven). Maybe this is something that could tie into case studies, so that in proving their skills they're also contributing their experiences. It's not a foolproof idea by any means, ashow do you prove you made something on the internet when you might not be who you say you are? But I would wager it would be more accurate. Anyway, I digress. But it feels good to have typed a lot on the forums for the first time in a while

A million times this! Of course, you can't tell someone they're perhaps being lazy in real life if you want to work with them, but as I read the first post and before seeing ryan's my first thought was "I bet the design agency would prefer to play it safe" which is understandable to a degree and probably true of many. I've only worked for a web development company once, and I had the good fortune that they listened to me when I said I could save them time with a CMS (this is back when I was using MODx). If I could take ProcessWire back in time with me I'd have saved them even more time and money! Seriously though, it might not hurt to say to them some of the things that have been mentioned above in terms of security and stability. What I'd add to that is that ProcessWire is built for today's web technology - there are many other CMS' out there still supporting legacy versions of PHP and crippling themselves (by comparison) by not being able to leverage the advancements in PHP's core in recent versions. I would submit that ProcessWire is the forward-thinking person's CMS of choiceTM in this regard. It's not hampered by legacy code and the thing that I still love is that it's been so wonderfully abstracted that even if PHP6 was a total rewrite that turned every function on its head and renamed most of them it wouldn't change your API calls, because we access the data through the PW API then the API would still be the same (ryan would have quite the headache in that fantasy scenario, but the API is actually a safety net to a degree - nothing in the core would be deprecated in the future from what I can see as there's simply no need - it's that abstracted and has been built extremely sensibly in the way that it reads). What I would suggest owzim, time-permitting, is that you put together all these points for this or other agencies and maybe even offer to build something for them to show how fast sites can be developed. Speed and ease of use are two of the biggest selling points for the people who are going to part with the cash, and for agencies ease of use also means other workers can easily learn the system. Then you're giving the agency the tantalisingly juicy apple of saving time and therefore making more profit. Onto democracy, totally agree. Without leadership things can stagnate in a pool of good-natured suggestions and resultant inaction or, worse, people working in silos and doing their own things. I think on a project like this the thing is that as long as you don't get too despondent when an idea isn't included in the core then you'll get on juuust fine, but feel free to keep suggestions coming

Hi folks This isn't a new concept, but since I use this on several sites and was getting frustrated by having to add the fields and put the CSS in the admin template's CSS file to have it overwritten on updates I thought I'd make it into a module where it should work regardless of which admin template you use and shouldn't be affected by updates since the CSS to hide the fieldset's container styles is now in a separate CSS file completely. Unfortunately I can't find the original topic where this concept was introduced (if anyone can find it, please link to it as I can't take credit for the idea), but essentially what the module does is create a left and right columns that are actually fieldsets, and you simply add the fieldsets to your template and place fields in each of the columns to suit yourself. Enough chit-chat, the screenshot below will explain it better: I think when this was originally discussed it was back before ryan had introduced field widths, but I think this still has a place for where you have differing heights of field (as per the ASMSelect field on the right of the shot) where using field widths would result in a space before the next row of fields. In fact, this works especially well on pages where you have small bits of information to enter and want to leave a larger left column for text editor, image and file fields. The beauty of now having variable width columns per-template now as well is that you can change the fieldsets from their set widths of 70% and 30% respectively to whatever suits your needs on a particular template. Download from the modules directory. Usage Download and install the module above Add admin_column_left and admin_column_right fieldsets to your template and put the fields in the relevant column fieldsets (Optional) change the field width for either column, taking care to leave 1% for a gap between the two columns (default is left column at 70%, right column at 29%) That's it!

Hmm... actually it doesn't seem to work. Using latest dev branch and it still defaults to the page list when another page is set as the first child of the Admin page

Finally using this in a booking system - thanks Diogo Might still be nice to make it core though ryan? I don't think it would hurt and I can't see it causing any real confusion as the only time you would want to tweak the order of the admin pages you would probably be putting in custom admin pages and want tomaybe do something like this anyway. I guess what I'm saying is it won't affect 99% of users, but would be helpful to the 1% without adding any bloat.

I did hear, but haven't checked the facts, that the head of Nokia is an ex-MS guy and through this will become a MS employee again. From the outside and with none of the facts to hand It looks a bit like he went to Nokia to help them out and in the process set up a relatively cheap deal knowing he'd be back at Microsoft. I know it doesn't sound like a cheap deal, but compared to Vodafone's recent transaction it's pocket money

Yeah, but I wanted to take it one step further and hide some of them based on roles. I had totally forgotten about that module though so thanks guys

Hmm yes, I hadn't thought of required fields (I was more thinking about field dependency in that if the user has a role then show that field) - required fields make it a bit trickier as all required fields should be shown of course regardless of the user's role or the page won't save. That might be a useful thing to have in the future though for editing workflow - I guess a simple way of doing it might be something like this: The editor edits the pages they have access to - before the page can be saved, they fill out their fields. If the manager role can see other fields and one or more is required, when the editor saves the page in the step above it simply cannot be published, but it can be saved. When the manager finishes filling out the other required fields then the page can finally be saved. Something like that might get around the issue.

ryan - just a thought, but would it be possible to make it so that fields can be shown depending on whether a user has a certain role, or even ID? Certainly roles would take you one step closer to a system I used to use where there was an editing flow with a website's content - someone would work on content, then their manager would fill out some other fields on the same page, sometimes in another tab in the editor, before finally publishing a page. It's not something that everyone needs, but to my untrained eye it also doesn't look like it would be too difficult to add (*ducks for cover*), would make it even more powerful and could be useful in many different scenarios. I guess the selector for that would be something like user.role=editor|manager as well as user.id=41 maybe for scenarios where the main admin user wants to test some stuff or have hidden fields that other superusers can't see (though that's silly as other superusers could give themselves access anyway - just thinking of odd scenarios!). Can anyone else think of uses for this?

I think I've been getting confused - it must have been in a private beta earlier this year and I'm not as blind as I thought. The actual launch appears to have been the 15th of August so I don't feel so bad now: https://stripe.com/blog/introducing-stripe-uk I think the only drawback is that they don't offer the ability to transfer to your bank account on demand, favouring a 7 day automatic rolling payment schedule (to be honest having the money in their system a few days longer is probably one of the ways they make a profit from the system aside from the fees - which are 1% lower than PayPal). I don't think that that is really a huge deal though as there is usually some waiting period for transfers with most merchants and in this case you can know in advance what day each week money will land in your bank. The fact that they've opened a London office and are working with other European countries as well as Australia also shows their commitment to going global and the fact that they are likely to be around a while. I think they've got the potential to take quite a slice of the market at this rate, or certainly stir it up and kick a few bums into action in terms of the more archaic merchants out there.

OH MY GOD I COULD NOT BE HAPPIER ABOUT THIS NEWS! Yes, my caps lock was on for a reason there, and yes, I'm working on a module for Jason already During my tests, Stripe can be described as nothing short of awesome. It's got the nicest looking backend (ahem) and is a doddle to use! Module on its way soon The great thing when you go to click on a button to make a payment is that stripe's module just slides down the screen in sort of a modal overlay, but the card details being entered are going straight to Stripe's site, so no PCI headaches as whilst it looks like payment details are entered on your site they're not and the customer gets a smooth experience to boot. Basically, other merchants should take note (yes, you too PayPal). EDIT: Oh, it's been around in the UK since March? Why did nobody tell me? Last time I had a look for decent UK merchants was February and didn't notice when doing the module for Jason that it was available in the UK too

Nice, functional, fast site - I like it. That's ProCache!

I think it's more that so many of us hadn't thought about this before but can instantly see the benefits ryan, not that we've necessarily all been waiting for it before now. I think that's testament to how well it's been implemented.

Great addition, thanks ryan or building it and Antti/Avoine for sponsoring it! It can make several of my more complicated forms on some projects a whole lot shorter and more legible now And like many others, I marvel at how well ryan's initial versions of amazing features just seem to be so polished!

It's all possible in ProcessWire, but that looks like a more complex site than most. To my mind it would almost be easier to map out the templates on paper first to work out which fields you need for which templates and how they interact, then we could get a better idea of time involved. The problem from an outsider's perspective is that to me it looks almost over-complicated in places (so many options for searches that might be able to be streamlined using something like $pages->find('template=images|contributors|locations|discussions, keywords%=your search phrase') for example to search a common keyword field across multiple templates, assuming you have that field against many templates).That took me a bit off track, but the rest of the site looks quite large and very bespoke is what I'm getting at - it would be very difficult for an outsider to give you any idea of timescale to reproduce it in ProcessWire. Having said that, if I was going to do anything as complicated as that myself then I would be 100% confident that you could build it all with ProcessWire. The sky is the limit, it just depends how much time you have

I have just one problem with this approach. It's perfect for what I need for a site where customers can buy things/services as every email address is unique, however a username might not be! For example, if I have two customers called John Smith sign up, I have to do a check during registration to make sure that if there is a John Smith already that a number gets appended to their username (so john-smith-1 or something like that). Feels a bit messy, but there really isn't any way around that I guess? I'm being too picky though I think as even when a user edits their profile they don't need to know that behind the scenes their user page is stored with a name of john-smith-1 Okay, I'll shut up now since I've talked myself out of actually having a problem!

Cool Errm... many Mac apps aren't, and vice-versa.

I always forget about that - another good reason!