Pete

I upgraded from 7 Pro to 8 Pro and have yet to encounter any issues. Only one app was incompatible, but upgrading it fixed that. I'm used to it already, but think the built in apps need some time to mature (mail app could use HTML signatures, but I guess they might want you to use Office 2013 when it's out for advanced stuff). Only major issue has been that it uses port 80, so XAMPP broke until I changed Apache to use port 81. Sure, it means you get uglier localhost URLs, but it's not a problem now I've resolved it. Having contacts from multiple email accounts, FB and Twitter in one place, plus seeing what everyone's up to all in one place with no ads is nice too (though I doubt it's unique to Windiws as I'm sure someone with a Mac will tell me ).

No worries - just wanted to check I wasn't going to reinvent the wheel before going any further. All I really need that's extra is to pull out the user's name and email address for now - groups is a bit beyond me. I know that using adLDAP I can get more information but I'd rather not use another class just for that. I'll have a tinker and see what I can come up with, but so far this solves a huge problem of not wanting to give users in a Windows domain environment yet another login to remember

I seem to remember the mobile view being better too. I think they were saying on their forums that they're going to focus more attention on the web app as it's a waste trying to develop for iOS and Android for something that's web-based.

I just used this to add AD login abilities to a company docs intranet site for PW and would like to suggest some changes. In this particular environment, the AD logins are in the format of "Forename Surname" <- the problem here is the space in the middle and PW replaces it with an underscore before the check against the LDAP server so it fails and doesn't authenticate properly. The following fixes it: Replace this: $name = $event->arguments[0]; $pass = $event->arguments[1]; with this: $name = wire('input')->post->login_name; $pass = wire('input')->post->login_pass; And this: $user = wire('users')->get("name=$name" with this: $user = wire('users')->get("name=".$event->arguments[0]); Any other suggestions welcome, but that should work correctly in more situations. Antti, did you do any more work with AD groups mapped to roles?

Multi language on the wiki software should be possible but I've never got the module for it to work and it was a pain last I checked. I'd suggest we need a PW based solution since that handles multi language well Of course that's honing to require some thought on how to set it up too, plus might need version history first as some way of moderating and rolling back changes.

I think eventually we will have a few very different site profiles that, combined with some good marketing videos, may do a lot of the convincing for us. For example, with the shop module I love the point "any page can be a product". Plus once there are enough totally different profiles its easier to show prospective clients that you can do anything without hacking the core at all. I know this has been mentioned elsewhere, but I think the profiles in my head would be Shop, Blog, Member-driven content and of course the default basic site. If you can show more then that's awesome of course but when trying to get across the point that it can do anything, having these varied examples to fall back on would make it so easy. Then to sell it to those heavily invested in other systems you could just change a few fields and tweak a template right in front of their eyes and show how simple it is. People are wary about having to learn anything new when they've spent a lot of time (even forgetting about the money they have probably invested years of time) so if you can get across how simple it is then I think you can win them over. So variety + simplicity + power = panther (which still sounds like it should be a bad aftershave ).

Loving this Luis - looked at the link and it's very nice indeed, good work I looked at the Google Doc too and ran it through Google Translate - I think pretty much all of that fits for the UK and probably most of the rest of the world too. Some countries have multiple tax classes just to make things interesting (Canada is one of them I think) so I would suggest that as Antti has done any further development of new features be really easy to extend or override where necessary (pretty obvious I know ). Keep up the good work as it would be amazing to eventually have a shop profile with the most common features already set up that can be installed with a blank PW site as a starting point for e-commerce sites.

Also, not sure whether you've seen this thread: Might be worth noting for future clients working with Drupal that there are some steps to help converting content.

Hi Joshua I think you're right in that you can do anything with PW that you put your mind to. I've had the same experience you've had with clients wanting to use Drupal but with WordPress, and have vowed in another thread not to touch any more work that comes my way where the client wants to use it - it was just that unpleasant an experience last time I used it. The problem I find is when someone else has implemented a dozen plugins and you have to go into someone's work and find out where the issues are if something doesn't work as expected - you spend more time bug-hunting instead of developing. That said, a lot of it can be to do with familiarity of a platform. I've got no experience with Drupal and little with Wordpress, so I'm sure if the roles were reveresed I'd struggle a bit with ProcessWire at first, just maybe not as much as I have with other systems. It's just the frustration of forcing a system to do what you want when you know there's a quicker, better way for a given type of project that really puts me off using some other systems nowadays. With enough time I think you can achieve anything with ProcessWire. Whilst I've not built a site exceeding more than a few hundred pages yet, I have managed to integrate it with forum software and built a file repository. I've never found myself thinking I couldn't do anything with it - it's just a matter of working out how to do something rather than if you can. For one project I did have to do a little work to mock-up a small piece of a site to entice someone away from another system to ProcessWire and it worked, so one way to do this if you feel they're open to suggestion is to put together a small demo that's relevant to their content and show them how it could work out better for them. Of course, this has to take into account whether they're receptive in the first place, plus it's a case of weighing up the chance they'll switch against time when you're not earning money, but it comes back to the saying "a picture is worth a thousand words"... I think "a demo is worth a short novel" applies in this case It's always easier if you have time to show someone something than to try and describe the benefit. I'm also really excited about a lot of the modules that have been released recently - for example some members here are talking about some interesting things with regards to Antti's shop module that look amazing (had a quick peek at the example linked in this particular post and loving it: http://processwire.c...isa/#entry18784 ). I'd love to soon be able to use ProcessWire for any type of site because I believe it's flexible enough to fit pretty much any role.

A hash is usually used in a URL to jump to a HTML anchor further down a page (like <a name="bob"></a> halfway down a page called "tim.html" could be called via yoursite.com/tim.html#bob and that page would load and automatically jump down to that anchor). I'm not sure an anchor would work any other way due to this.

I really like this implementation of columns and am going to use it on a few sites soon I think to make better use ot the page - ryan, could there be an option in the fieldset options to hide the title rather than what's been done above (hidden by CSS)? Not that there's anything wrong with using field widths of course, but this way that had a combination of the two does look neater in my opinion, and certainly adds more options. I wonder if there's scope to include some things like this in the default site profile too - just to show some more possibilities out of the box? Only problem of course is that I can't think of any of the default templates that would use this fieldset-as-solumns layout.

I think from memory that the table is called users (can't check from my phone) but the password would of course be encrypted so that wouldn't do you much good if you we're intending to reset it there.

It's just a case of including the class and you're away with a couple of lines of code though so I'm not getting where that's making it too complicated in this case. I just personally don't think that it's a good idea to exclude Twitter because they don't use Oauth2 if its not hard to resolve - its an immensely popular platform and I think would be worth the extra code. Like I said, I'm happy to look at it once the rest of the module is done and see how best it makes sense to integrate it.

Could we not just include a few more files? I know you're wanting everything to be Oauth2, but it does only take 20 mins to sort the Twitter integration - just a thought and not a criticism. It's not like download size is really an issue either thinking about it. I'm happy to take a look at it when the rest of the module is ready

Try something like find("name=$mypage") in your code above since you don't have the full path available to you. I'm assuming you're wanting to match against the sanitised page name (ie. the URL version of the page title) - if not its title= and not name=

Twitter auth is simple enough with Matt Harris' library (he works for Twitter). I used to use Tijs' library myself, but Matt's is more up to date and seemed easier to use - it's used in one of my Twitter modules for PW in fact.

Don't worry, when I started with PW everything I tried to do had an easier way of achieving it Quite often I'll scratch my head over something for hours one evening and then have a eureka moment an solve it the next morning after sleep and caffeine

Erm... No PHP required - just add " | Your Site Name" before the closing </title> tag and you're done. I think that's what you meant anyway?

Haha, I just got that reference! When was it the Mayans predicted the end of the world again? I forget.

Well there was that one that President Obama won in 2009 Like many news reports are saying, it's an odd time to be awarding it but it is actually for everything over the past many decades and bringing together half a billion people from various nations since Europe had been in turmoil and was really on the ropes earlier last century.

Are you definitely trying to access it at yoursite.com/processwire ? Sorry, got to ask the silly questions first.

Nico - increased it to 50. Marty - I suspect this will be fixed in the next version coming *soon* (no idea when soon is, but the speed of updates in PW means waiting for any other software update is like having your teeth pulled out ). I'd hesitate to spend time on it just yet if a new release is coming in the next week or so, but I agree that it is terribly frustrating when you press "back" on your phone and can't click on the topics beneath the overlay. Marc - yes it does. If you're on a smartphone you can load the forums, touch the icon at the top-right and touch the New Content button. It's pretty quick as it doesn't load the usual theme for the forums and works reasonably well even in slower data areas, although 3G and wi-fi would be preferable to waiting.

I like the images on all the other pages - the homepage one I keep trying to work out if he has any arms or not and how long it takes him to button that outfit up It's a good-looking site and I think the other imagery used throughout manages successfully to get away form the image of lawyers as stuffy, unapproachable people (not sure whether they have that image worldwide, but I suspect they do).

I like Marc's idea as then you could have a field called gallery that could be a multiple image inputfield and you're away

I like this because it was already what I was doing The closing PHP tag is something I've picked up from coding with PW.