raydale

This looks like a great module Wanze!

 

I have a suggestion: It would be great to be able to click on the title of a page and open that page for editing in a lightbox overlay not sure how easy this is though.

 

I can see a great use for this as a quick SEO overview as the title, name (url) and parent (parent url) are shown. Further to that - it would be great to be able to have this available with reduced privileges for roles less than the superuser (with just the ability to see the list and perform actions applicable to their selected roles).

This looks fantastic Ryan. I will be making a purchase for sure.

 

ProcessWire already seems incredibly scalable and ProCache looks to be the icing on the cake.

I honestly haven't tried it yet. But if for some reason it doesn't work, I'm sure I'll be able to make it work pretty easily. 

 

Okay, no problem. Thanks Ryan. I'll probably be getting a license in the next few days anyway.

I agree Nico. However, perhaps this could be managed in a different way?

 

It seems that a lot of the ProcessWire permissions are tied into the actual templates - hiding the true level of flexibility. Well, maybe the site templates should also be listed under 'Access -> Roles -> [Role]' with the ability to change permissions for those templates within the roles page (as well as the current way they are handled per template).

 

Below is a screenshot of how Drupal handles permissions across its nodes (content types / templates) in one single screen for each role (columns in the table):

 

 

I think that this would be a usability gain for site administrators.

Thanks for the information Pete, good to know. I am guessing those assumptions are spot on.

I must have been living under a rock recently, I've only just noticed the 'Form Builder' has been released. I will be getting this for sure.

 

One quick question: will I have the ability to have multiple forms on a page? For example, a general contact form and a newsletter email capture form?

Just catching up with all things ProcessWire lately and am excited by what I see being put into 2.3.

 

The new traversal functions and LinkMonitor module and comments monitor look good. I also really like the concept of having $config->prependTemplateFile and $config->appendTemplateFile to reduce the need to call includes in template files.

The problem with my idea of a "simpler" blog profile is that if I build it it's going to feel a bit wrong as it will throw some best practices out of the window to essentially "dumb it down", so if I were to attempt that then I might feel a littly dirty by the end of the process

 

The dumbed down 'dirty' approach is pretty much all I do!

 

Seriously, it serves as a good point and one that most designers with low to moderate development capabilities (I'm firmly in that bracket) wil be comfortable with. In fact if you look at most of the code samples in WordPress theming and tutorials, inline coding is pretty much the accepted standard. This bracket of people must represent a large section of those looking to use a CMS.

 

The fact that ProcessWire allows for this kind of approach and doesn't discriminate against it is a strong selling point in my view.

 

I'm currently putting a profile together for a website that I might 'generalise' and share - full with inline code.

Thanks Joss and OrganisedFellow. I've been away on other projects for a while. Glad you found the study useful.

 

BTW - this site will be up for a bit of a refresh around May this year. I'll post an update then and a bit more in retrospect.

@adamkiss - well I am hoping that I can persuade clients to use PW more over the coming months as new business starts to flow again, I can maybe even persuade a few older clients to give WordPress a break.

 

@MathewSchenker - Greetings to you too. It's interesting to see someone familiar with Joomla moving across to ProcessWire. There is a lot of hype in the Joomla community about 3.0 (with 3.5 slated soon too?), but still no CCK type features in core?

 

I know what you mean about it being less work to start over. Both Drupal and Joomla have been a knightmare to upgrade and design for. WordPress less so, but some of the community plugins and even premium themes used by some clients are poor. I am primarily a designer, but I am still a little concerned about some of the coding practices in WordPress plugins and themes used.

 

I have learned some big lessons over the past 10 months or so, especially in which CMS to use for which situation. I have to say that ProcessWire seems to more easily cope with nearly everything (the exceptions being forums and turnkey eCommerce at the moment).

 

The trouble I am finding is that once a client is comfortable with a particular system, they are very reluctant to move away from it and building a convincing case can be difficult at times.

Hi guys,

It's been a while since I was involved in the forums here. I've been away working with legacy Drupal, Joomla and WordPress systems due to client requirements. It's been a time hog and not all that enjoyable a process.

I finally had a chance to use PW for a project again yesterday and what a breath of fresh air it has been! I had forgotten how easy, consistent and reliable querying pages was, no more temperamental WP_Query object in WordPress or complex render arrays in Drupal.

It's great to see how the community has grown since I last checked in, as well as the improvements to ProcessWire overall. Ryan is steering forward in a very strong direction. I'm going to have to get the FormBuilder plugin I think, it looks to be fantastic.

Anyway, I hope to be hanging around here more soon as a bit of work/life freedom approaches. Keep up the good work.

HAHA!!!

Thanks very much for your patience Diogo and Soma! It works now.

I have looked through the instructions again and it does clearly state 'Once installation has completed, move or rename the /tmp/site/ directory to a /site-name/ directory in your main ProcessWire installation'.

Of course being an idiot I scan read the steps and ended up just putting the 'site' folder INTO a 'site-name' directory. I hope this helps anyone else coming across this problem.

Thanks again guys.

Hi Guys,

I have read through other topics on using PW for multisite setups and am a bit none the wiser unfortunately. Let me explain my scenario:

I have a potential client project whereby they want to have 3 websites all as separate websites in terms of:

• content
• look & feel
• domain names
• Users

However, for me to setup up the websites for them it makes no sense for me to be managing 3 separate hosting accounts and them to be paying for all of that. Also, 1 of their websites will be a primary site with a few thousand visitors per month, but the 2 more secondary websites will only have a couple of hundred visitors. Perfect for a multisite install to my mind which wouldn't tax server resources too much.

This to me seemed a perfect opportunity to setup a multisite under one hosting environment whereby domains are mapped to subdirectories or whatever setup I would need.

My problem is that I have no idea as to how I go about setting all of this up in PW. I have done this before with WordPress using the domain mapping plugin under a multisite install. All without dealing with symlinks or much code at all. However, I would really like to use PW for this as long as it's not too complex. With PW I can deliver a client user experience in the admin area that is much more streamlined for their particular use case.

Just saw this. A fantastic read and more than anything else, it just reaffirms the view for beginners that high-quality work is definitely achievable with Processwire. Case studies like this I think are definitely a confidence boost for any other designer using this system.

Would be great to see a few more, and for different types of site.

Thanks very much onjegolders - I'm glad you found it useful. I hope to get more people contributing Case studies and I plan to write one for my next client site with PW coming up soon.

I hope the case studies will highlight the strengths that PW has in real life scenarios (it has many) and help people to decide on using it.

No problem Ryan. I will get more case studies up as I go along. Hopefully, this will entice other people here to do the same and add real use cases for people considering PW. I'm also hoping that this will persuade people that PW actually delivers on its promise - and isn't too good to be true as it first seems.

I think a subforum should be fine.