Leaderboard

I've been asked how to integrate Will Bond's Flourish library with ProcessWire so I thought I'd post the code I use. I downloaded the Flourish classes (not the whole flourish project) and put them into /site/.flourish. I then pasted the following into the top of my head.inc file. function flourish_loader( $class_name ) { // Customize this to your root Flourish directory $flourish_root = wire('config')->paths->root . 'site/.flourish/'; $file = $flourish_root . $class_name . '.php'; if (file_exists($file)) { include $file; } } spl_autoload_register( 'flourish_loader', true ); After that, you should be able to use flourish classes anywhere in your templates. NB, if you do download the whole flourish project into .flourish, then read Alan's post on how to adapt the above to your layout.

Dear Ryan, Thank you very much for this CMS, it really make me wonder that it is difference from other CMS that easy to custom filed after i read and learn from you. Thanks for work hard, I love this CMS maybe my next project will move to processwire. Andy

Thanks Didjee! I've updated the git repo with your fix.

Glad you found it useful

Welcome to the forums Didjee! Thanks for the fix. Great first post!

I committed a couple small additions this morning: 1. Fieldset indentation in the template editor. Hard to describe, but I needed some way to make the grouping of fieldsets a little easier to see in the asmSelect list in the template editor. Here's a screenshot which describes it better than I can: 2. The InputfieldCheckboxes field now supports columns. This would typically be used if you had a Page reference field using the Checkboxes input. When editing the field, you'll see a new option on the 'input' tab where you can specify a number of columns you want it to use. This is just a way to tighten things up for when you have lots of short-labeled checkboxes (see bottom of screenshot).

Great question, not a silly one at all... Agree with the points above - any CMS has a bit of a learning curve especially if you're new to the concept, but having used quite a few CMS before I think ProcessWire (PW) is not overly demanding and easier than some of the best known systems; especially once you get past the basics. I only have pretty basic PHP skills but so far I've been doing fine with PW; as Ryan has pointed out elsewhere, the PW API is very friendly - so the complexities of PHP are hidden from you in most cases, to the extent that it's no more complicated than the proprietary template tagging systems used in other CMS. However, the advantage is that you're learning a universal language with transferable skills and lots of online and offline learning resources to help you out - plus further down the line you have the full power of PHP at your disposal if you really start growing your ideas. PW doesn't have as many ready built modules at this stage but then I actually think this puts you in a better position further down the line since you will understand what you build and be able to maintain it yourself. If you go for a system with lots of 'plug and play' modules then often you run into issues later if these aren't compatible with the CMS when it gets upgraded, your client requests a tweak which you can't code yourself, or the module is abandoned by it's author at some point. ProcessWire is as much a framework for building things as a CMS - so the further you need to push it the more you will appreciate not being boxed in by someone else's ideas - which is often the case if you go for a lightweight CMS (easier to set up in the first instance but much more likely to impose limitations later on). Well good luck and look forward to more questions