Peter Knight

Agree and have noticed that some clients devalue a CMS when they think "it's free". What I tend to do is mention that it's freely available but represents a product into which thousands of man-hours worth of development have been invested. Still need to work on the phrasing there but *some* clients need to be reminded that just because it's "free" doesn't mean it just appeared on the web overnight. Or more importantly that it's some kind of download which then requires zero installation, setup, build, maintenance, patching, upgrades, training ... ... ... ...

Having worked with senior Marketing in Enterprise sized organisations and even a Fortune 500, I can tell you right now what they expect from a CMS. Some of these might be suprising but its good to know. Comprehensive users / usergroups / roles / access permissions etc etc File management and secure file hosting Draft to staging to published workflow Related to above, ability for admins to review stuff before it's live (including getting notified when pages are ready for review) and share pages with other team members for review Form wizards so they can build their own forms Media management Custom dashboards for their "own" areas Round the clock support Approval from their IT department etc who review security, upgrades, patches etc etc BTW, my involvement with these companies was not website related but I've seen their setups and spoken with them in the past about such things. I'm happy to run any specific questions from Ryan and Co past them if more detail is required.

Thanks Nico.

Would love to have an indication within the admin that there was an update available. A simple icon in the footer could suffice. See the pink circle in footer of attached mockup Suggest it's only visible to users with correct permissions and reflects status of stable branch.

Worked beautifully for me. Just tried it on my new ProcessWire blog and updated it from 2.4.12 to 2.4.18. Took approx 20 seconds from download of Zip to install and upgrade. No errors. Admin and site working great. My first blog post after upgrading was about the new upgrade Module. Now, that's circular

Hi guys. Just wanted to properly say "hi" and thank everyone for all the help lately. I'd been posting as "sparrow" for many months while I got started and many of the regulars here have been a great help. I'm an independent web designer from Dublin, Ireland, and my primary CMS is MODX. A while ago I decided that 3 CMS would be a good number to settle on and I began to evaluate Craft and PW. What attracted me to PW specifically has been all the good stuff I'm sure you already appreciate but in particular, I really like: PW fields and especially how powerful the Profields set are Lister (not released yet) Image management (native and CropImage etc. Image control is brilliant in PW) Fields control (allowing me to specify exactly which field(s) to display per template) How friendly the community is How communicative Ryan is re. the product and the fact that there is a roadmap and that roadmap is largely followed and updated The array of great Modules available etc etc. But basically, PW has been impossible to ignore with the recent adittions of Profields and Lister. I'm very much at the beginnings of my PW journey so to be balanced, these are the areas that I've found challenging: Speed. I find *just* having a tree slows my editing down a lot. Would love to see a tree on the left and the page edit on the right. Obviously, I'm coming to this from a MODX perspective Right-click Again, probably baggage from MODX but it's very useful to be able to right-click a page and duplicate, delete, move, hide from menu, quick-edit etc etc. I can't do this on PW. But mayeb there's not such a need. User control The user control and permissions look very basic. I'm used to much more fine grained control over which elements of the admin a client can see Manager appearance When I first installed PW I found the box-iness and colors a bit hard to settle into. Some of that may have just been TinyMCE which I replaced and I believe made a huge difference. I know there are lots of themes available so that's not an issue now but was definitely a "first impressions" thing. PHP That's not PWs fault. I've gotten used to working with tags so being pushed into a bit more PHP has been a challenge. I'm enjoying it though and feel my skills are slowly but surely coming on. So that's my 2cent. Thanks again for all the help so far and it's great to be part of yet another very friendly CMS community. On a side note, I have started a mini blog based on PW, Craft and MODX as I think they really are 3 of the best CMS available. Will update soon when I have a little more content.

Sounds like something I've seen recently in Craft ( entry types ). http://buildwithcraft.com/docs/sections-and-entries#entry-types Good to know PW is up to the job too.

I did look there first but those logos don't have the P symbol used on the site. Google image search has mixed results but may have found something I can cobble. Would be great to have a brand section on the site.

if anyone has the PW logo as a PNG or EPZ, can you provide a copy? Thanks

Cheers Fokke. I'm familiar with the Page field and it's brilliant. I'm not sure that it'd match my tagging requirements though ?

I'm building a site for a college where they teach approx 20 courses. Each course page will have a: tutor duration price and I'd like each of these to be clickable tags whch loads a page listing matching courses. So if Prof. Beezlebub is teaching religion, I want web users toclick his name and see a list of his other courses etc In the PW admin, I want editors to be able to specify what courses contain which tags. Can someone give me a very basic overview of whats involved. I don't see a field type called Tags in the Filed setup. I also want to make sure that a tag from a Courss will load a list of other courses, but not any matching tags from say, a blog. Many thanks

No. 1 - an optional add-on.

Fixed my issue and just updating this in case anyone has same problems. Authors profiles are just users. If you have a user, you can set their blurb in the Users area. I'd renamed my /blog/ page to /blog-test/ and this is why some of my links weren't working and why the right column wasn't displaying "Recent Comments" and "View by" etc Blog settings are back since I renamed my /blog-test/ to blog/ upgraded PHP to 5.5 and updated the blog module to the latest version.

Cheers Ryan I revisited the requirements page for the dev branch and noticed: PHP version 5.3.8 or newer.Once I upgraded the hosts PHP version to 5.5, it worked. My oversight but thanks for chipping in.

Should I be able to add Authors in the Blog>Settings>Author page? Currently links to my author are throwing a 404 and I was sure that previouly, this was the correct space to add authors. PW 2.4.0 Also, none of my General Settings ar ebeing saved. When I open the General settings page, all the fields are blank. Populating anything and saving throws an error of: Can't save page 0: : Pages of type NullPage are not saveable

Hi guys Just tried an upgrade from 2.4.0 to todays Dev branch and now have an error message. Whats the best way to diagnose? I can restore the old files but wondered if this was fixable?

Hey dupalski Just out of interest, what kind of features on your site do you think might need either Modules or Extras? I'm a long time MODX user who has just started using ProcessWire so I understand your question. To be fair to both systems, they're both terrific and you really can't go wrong by choosing either. Particularly with a site as small as you mention. You're not going to make a bad decision so just get stuck in. The only thing I would say is to eventually give each CMS a proper go. I know time restrictions mean you have to choose between either CMS right now and roll with it, but I've found each CMS works a little differently and has different strengths. Knowing both can only make you grow as a designer/developer and it makes no sense to me how some people choose *a* CMS and stick with it at the exclusion of everything else. I haven't replaced MODX as my CMS but am simply broadening my toolset. What I will say about PW is that since "joining", I've found the community to be incredibly helpful. MODX community is very helpful too. But what I particularly like about PW is how communicative Ryan (main developer) is about roadmap, features, the upcoming release etc etc. Good luck with the site.

Genius. Thank you

So if we update to 1.2.2 will we loose any changes we've made in the interim?

Agree. I'm coming from that CMS and I really like the ability to not have to rely on includes so much.

Thanks Soma. Happy days @mr-fan Re. RTFM you're right. I need to familiarise myself with selectors more and how to use them. hazards of choosing a new CMS on a tight deadline.

Can it be done with Soma's SimpleMarkupNavigation? It seems to have more control over setting the options but I can only seem to work it by starting at the root and not the parent <?php $treeMenu = $modules->get("MarkupSimpleNavigation"); // load the module $options = array( 'parent_class' => 'parent', 'current_class' => 'current', 'has_children_class' => 'has_children', 'levels' => true, 'levels_prefix' => 'level-', 'max_levels' => 1, 'firstlast' => false, 'collapsed' => true, 'show_root' => true, 'selector' => '', 'selector_field' => 'nav_selector', 'outer_tpl' => '<ul>||</ul>', 'inner_tpl' => '<ul>||</ul>', 'list_tpl' => '<li%s>||</li>', 'list_field_class' => '', 'item_tpl' => '<a href="{url}">{title}</a>', 'item_current_tpl' => '<a href="{url}">{title}</a>', 'xtemplates' => '', 'xitem_tpl' => '<a href="{url}">{title}</a>', 'xitem_current_tpl' => '<span>{title}</span>', 'date_format' => 'Y/m/d', 'code_formatting' => false, 'debug' => false ); echo $treeMenu->render($options); // render default menu ?>

In MODX there's a snippet call Ultimate Parent. I use it for building sub-menus on the left navigation of my pages. IE Whereas my top nav would list all level 1 pages, UltimateParent would only list sub-pages of the current Page. Is there a PW module for this or would it be simply a case of using some PHP with the API?

That would normally be my own setup. In this instance, it doesn't work. Well, it works for the homepage but any sub-pages dont work. I suspect my issue is one to do with my shared hosting environment Because the domain name has yet to be setup, I am working on on a "domain reference" where my hosting company names a folder on a server after the name of my site IE I have my rewrite based set to RewriteBase /mysite.com/ But my working homepage (until domain is working) is http://217.199.187.73/mysite.com/

I'm having some problems with css, include and image paths and wondered what the advice was for the location of following assets (folder in root) - scripts - images - css Currently I have it in the root but perhaps it should be located in the default site/assets/ directory which comes with PW? Reason I ask is because I have a templates folder with a homepage and basic-page template located at site/templates. Both files are located in exactly the same level but both require different paths for the CSS Homepage only works with <link rel="stylesheet" href="assets/scripts/foundation/css/normalize.css"> <link rel="stylesheet" href="assets/scripts/foundation/css/foundation.css"> <link rel="stylesheet" href="assets/scripts/foundation/css/foundation-custom.css"> <link rel="stylesheet" href="assets/css/styles.css"> Basic page only works if I add "../" before above <link rel="stylesheet" href="../assets/scripts/foundation/css/normalize.css"> <link rel="stylesheet" href="../assets/scripts/foundation/css/foundation.css"> <link rel="stylesheet" href="../assets/scripts/foundation/css/foundation-custom.css"> <link rel="stylesheet" href="../assets/css/styles.css"> I should probably make the above into a single include but I'd rather solve this mystery first.