Leaderboard

Hi vigilante, welcome to the forum! There is a blank profile http://modules.processwire.com/modules/processwire-blank-install/ A site like this will be more complex to build with any tool. If pages are very different, one way is to have almost a template per page. if there are things in common, you can use the same template and use includes or functions on a common file. If the differences are minimal, you can do simple checks inside your templates for the page ID or any other characteristic this page may have that differentiates them from the others (a field. or the person that is looking at it, or the language, or whatever) You write it on template files, but has I told above, you have to be a bit clever about doing it. If the site really asks for it, either because of each page needing different fields, or because the code just need to be too different for each page, you can also go the 1 page / 1 template route of course I've seen that Joss and Kongondo also answered already, but still didn't see their answers. I bet they are loooooooooooooooong!!!! edit: I was right about Joss. Kongondo is not in a good shape today

Damienov, Just a word of encouragement -- Anyone who hand-codes HTML and CSS and can set up a website on a server should pick up PW pretty quickly, especially since there are many code examples in the API docs you can copy. I never wrote a line of PHP before coming to PW. While my code is quite basic and certainly not elegant, with a few conditionals and foreach loops I can build pretty much anything I want. I'm coming from Textpattern, WordPress and Drupal and, while I love Textpattern, I am continually delighted to use PW. You can tell it was designed by a man who understands workflow, best practices and security and it's just a joy to use (you see that word over and over in these forums). Plus, the support is second to none. Enjoy ProcessWire! Cliff

If you need to sort by some other field (Say you have first_name and last_name fields assigned to your user template) Use the "Custom selector to find selectable pages" option. template=user, sort=last_name

This has been asked before and you're unlikely to get an answer - not because rates are trade secrets, but because it depends on so many things. Experience is subjective, but which country and which city in which country also makes a difference. New York developers will charge more than rural developers. The short version rate you charge should be based on what you can live off plus some additional to cover times when there's not as much work on, plus extra for how much you think your experience is worth. It's not as clear as "what's the average" and it should be more about "what do you want to charge". If your rate is set and you're getting no customers then you need to re-think it, but essentially it's about your variables more than what anyone else charges. All that said, if you really want an answer then you can type this sort of thing into Google - "web developer rates in X city". Hope that helps a bit.

One more addition to answers above: you should take a look at Hanna Code module. It allows you to pull snippets of arbitrary PHP code into pages. This is what I've used to solve more complex needs, pages that need weird snippets etc. Typical issue with Hanna Code is that you won't be writing the code as files, so they won't be in your version control system etc. One way to solve this is to create Hanna Code snippets that include code from files and/or actually render pages. There's quite a lot that this little beauty can do, actually. Many of us "long-time PW users" have developed our own ways to work with PW. I'm using something similar to Zend Frameworks approach, with controllers, view scripts and partials, for an example. This is both a curse and a blessing with extremely flexible system like ProcessWire; you can create your own way to work with it, but especially if you're working on more complex stuff you'll also pretty much have to do that

Hi Vigilante, Welcome to PW an the forums... Adding to what Joss said, if you know your PHP, you will absolutely love PW...but you only need the PHP basics to work with the system... Think of templates as controllers and template files as views...You can even have one template, one main template file and several other .inc or .tpl to help with views. See this thread: http://processwire.com/talk/topic/740-a-different-way-of-using-templates-delegate-approach/ All your PHP code goes inside template files. A page is mostly something abstract...it just helps you to input content which you can later retrieve.... Very important to remember in PW - it is very flexible; there is no one coding style! So, if you look at different "profiles" - see modules section, as well as the default install, plus other examples on the forums, you will notice differences! Blank profile: http://mods.pw/19 Sorry, the above is somewhat erratic. You being a programmer, I'd say, get the basics of PW first. If you get this - http://processwire.com/api/ - you can do anything....I'd even dare to say, forget the videos for now...you are a coder, so look at some code..., try things. PW gives you the tools to accomplish a lot, easily, fast and consistently... -------------------- I'll probably edit this post in the morning

Just teasing you guys http://atom.io/

For those interested, this one http://zedapp.org/ that works as a chrome app and is a quite an interesting project.

And roles=<role name> ex: roles=admin if you need to only show certain users in a given role . Yep ProcessWire is that Awesome. And the people in the forums are the best

Just wanted to chime in here and clarify what I have found on the PHP Manual. Following the short discussion on PHP shorthands. I searched the manual and found the following: From PSR-1 (Basic coding standards) From PHP Manual So even after PHP 5.4 becomes the norm, only the short-echo tag should be used. Hope that clarifies the current situation (and probably explains Ryans preference). Please note, the manual also has this to say on use of tags in production code. Sorry if this is an old subject, and clarified somewere else. Just wanted to bring it to the attention of others, following my own confusion on this matter.

Oh, sorry - you probably got the impression that the composition took a long time. I did it in 5 hours. I had to sit on it for a week so he thought it took me longer. Hence why I was so pissed off he thought I had bought the track in ....

Hi and welcome Its easier to sort of go through this in a very boring way ProcessWire has a fairly basic construction: Fields > Templates > Pages As you would have already noticed. Firstly, it is important to realise that Templates and Template Files are not the same thing. Templates are your way of grouping fields together and template files are for markup for displaying pages. PW has no practical limits for the amount of fields, templates, template files and pages you create, so really you can do as many variations as you need - it really wont matter. The API in ProcessWire allows you to manipulate the field data associated with either the page you are currently viewing ( so $page->title, for instance) or it allows you to get or find fields from other pages or groups of pages. One of the most important areas for you to look at in the API is probably the section on selectors as this will give you a lot of details about relationships and retrieving field data. So, looking at Profiles for the moment. You might create a file in sites > templates called profile.php Then in the backend, you would create a new template - it will show that profile.php is available as a template file and you would choose that, obviously, then give your template a name - profile would be good! You now create a bunch of fields that you want to use for the profile. In some ways this is a bad example because there is already a template in the system for users, but we will pretend for the moment there isn't! However, when you create a template in the backend, after you create it you can associate other template files with it, should you wish. Add your fields to the profile template and you are half way there. From this point on, it is simply a case of using PHP and the API in profile.php to create what you need - and it is much simpler than starting from scratch. The API is very powerful and will do a lot of the work for you, while leaving you to do whatever layout you wish. That template and template file combination can now be used for creating thousands of profiles. When you link to one of those profiles, it will use the template and associated template file to render the data. The template file can be used for both displaying data and for creating input forms for editing data. (Other people can give you more of a lead about that). Now, with other pages, if you need to create completely different templates for each page because they are all completely different, then that is what you do. Not a problem. Though remember that any field can be used in any template. So, if all your templates need Title, page_meta, mani_text and so on, then you can reuse field as you wish (note, you can only have one instance of each field in a template, for obvious reasons - so if you need two textareas, you will need to create two textarea fields) The point with PW is that apart from following the relationship between fields > templates > pages, it is flexible enough for you to work however you wish, more or less and very fast once you get the hang of it.

@Damienov: by documentation of specific modules, are you referring to core modules (those shipped with PW itself) or 3rd party modules (most of the stuff in modules directory)? What kind of things would you expect to find from such a documentation? Asking because I'd be more than happy to provide better docs for my own modules, but I've no idea where to start, what would be generally useful etc. I'm a "screw your docs, just give me the code" kind of guy myself

Well MODX has been around longer than PW and it has a bigger crowd...I used MODX before..In fact, I wrote a documentation for WayFinder... Seriously though, yes, there is need for better documentation about some things in PW but we are working on it....and it is a community effort. At the moment, PW has specifically focused documentation that will help you understand the system quickly. That's the API docs and the cheat sheet.. Documentation about modules is still limited. Have a look at the wiki though for a start....and the HelloWorld module...Some modules like ModulesManager, Batcher, etc have their documentation within the read me. Also, "Markup Simple Navigation" has excellent documentation. What module were in interested in specifically? I am not getting you about how to "achieve the create button"? PW has methods that will help you easily create markup; mostly used by people making modules, but can also be used for your frontend needs. But, I would focus on understanding PW first. If you get that, then understanding how to create modules will be a smoother road. How comfortable are you with PHP? You will also need that to get to know how things work, especially behind the scenes. Back to the blog profile, if you read it's support forum, you will see it is also a "demonstration" about one of the many approaches things can be achieved in PW. There is also an explanation within the Blog Profile pages itself how it works! Did you read that? Besides that, it is dead easy to make a blog in PW without using the Blog Profile. You just need to understand the basics of PW - page, templates, template files and fields - and of course some PHP, HTML and CSS... There is no one method to coding in PW. That makes PW very versatile and powerful, but also a source of frustration for some who are used to being directed on how to do things (e.g. WordPress crowd)...I hope that came out right; I don't mean to offend...

I like being verbose! If this { do that } or else { do this } or if not { do this } ok go on then { do this instead } Much cleaner

clsource, You may already know this, but created and modified data is already saved as part of the page. $page->createdUser $page->modifiedUser

I'm having a difficult time imagining a scenario where templates/pages wouldn't be flexible enough to accommodate anything. It's really a matter of the logic in your templates. You can setup your templates to be as DRY as you like. There's no need to duplicate markup. Take a look at the delegate approach kongondo linked above. You may also want to check Ryan's blog profile for some ideas. There is also this discussion that may be of interest. When I first starting using ProcessWire it did take a bit to get used to the idea that there is no set way to do things. I think you'll find it's incredibly flexible, and can accommodate almost any approach. Oh, and the community here is exceptionally friendly and generous.

The links on this page may be of use: http://stackoverflow.com/questions/7508800/is-there-any-good-ical-vcal-parser-in-phplibrary but there's nothing built into ProcessWire that I know of that would give you a headstart. At the end of the day it's less about how it would work in ProcessWire and more about learning what the requirements are to get one built in PHP without ProcessWire, then applying that knowledge by building the necessary fields and templates in ProcessWire to get the job done.

Great post you linked to there teppo - even makes my example seem too cheap I know of a company that used to charge £10k for a large-ish site in static HTML and several hundred a month for support. I can now see why they set the initial price so high (though not the support - that seemed a bit much to me since they didn't do that many updates ever and an hourly rate would make more sense there I feel) as it was a large site to rebuild, but if I had just a couple of those a year I'd spend a heck of a lot more time making sure everyone was happy and doing an amazing job instead of the reality where they were landing lots of large clients and not giving any of them their full attention and trying to push them out of the door quickly.

@r2d2: for quick figures you'll probably want to find existing articles and discussions from Google. ProcessWire developers are not a special group when compared to, say, Drupal developers. Except, of course, that they're using a far superior platform This little post was something of a wake-up call for me: http://speckyboy.com/2013/07/08/turn-your-web-design-agency-around-by-raising-rates/. Things like that, of course, depend entirely on what kind of projects (and clients) you're interested in, what can you do for them that's worth their money etc.

Back to the "experience" bit, I always used to feel bad charging much for websites because, whilst I'm reasonably good at it, I enjoy it and it always used to feel like a hobby. Now compare this to any tradesman. In the UK an electrician to re-wire your house might charge £60 an hour and take a week (big house huh? ). That's £2400 for an 8 hour day, 5 days a week and the results of the work last a really long time and are effective as soon as the work is complete. A web developer is also a skilled tradeperson with experience built up over the years. The website might take two weeks for a non-standard site that's not overly-complicated. Like the electrician, my work is of immediate benefit to the client and will last a really long time (unless I did a really bad job). On top of that, my work will generate new customers and income for them. If I was to take two weeks and charge the same rate would you be offended by a £4800 price tag? Should you have a reason to be offended given the examples above? Of course because there is often other work on, some tradespeople (and web developers) will have to split their time and the project takes longer, but the hours are still the same so the longer the project takes to complete doesn't necessarily equate to more hours charged, but you get the idea. Anyway, these aren't what I charge, but I feel that the example is relevant - and also that I also might have pinched bits of it from some of the 37Signals books Something else to remember is that if your prices are right then you can afford to have fewer clients giving you more work than more clients giving you sporadic work. A lot of it is about building relationships as much as finding the right prices.

No problem. PW is incredibly flexible - more so than probably any other CMS/CMF, but it does require that you learn at least some basic php. Mostly foreach and if/else will get you going. I would definitely recommend googling a few tutorials on the possible options/rules for these statements so you can better understand the syntax. It can seem a little confusing at first, but once you get a handle on the basic rules, it really is pretty easy!

2.4 should probably still run on 5.2.17, just not officially supported. http://processwire.com/talk/topic/5543-processwire-24-possible-to-run-on-php-533/?p=54099 Maybe try contacting renobird (from that post) about his setup with 5.2.17. Also, this from Ryan: PS You can always get an older release of PW here: https://github.com/ryancramerdesign/ProcessWire/releases

Easily insert any complex HTML, Javascript or PHP output in your ProcessWire content by creating your own Hanna code tags. This module is based loosely on the WordPress Hana Code Insert plugin. A Hanna code tag looks like [[hello_world]]. A Hanna code tag with attributes looks like [[hello_world foo=bar" bar="foo]] using HTML style attributes or [[hello_world foo=bar, bar=foo]] using ProcessWire selector style attributes. After installing the module, you define your Hanna codes in Setup > Hanna Code. These Hanna codes that you define can then be entered within your body copy (or other text where you allow) and they will be replaced with the values defined or generated by your Hanna code. A common use case is to embed scripts or other bits of HTML or codes that would usually be stripped out by an editor like TinyMCE. However, Hanna codes can be more than just static snippets--they can be dynamic PHP or Javascript that outputs different things according to the request. PHP-based Hanna codes have access to the entire ProcessWire API. Hanna code accepts named attributes in the tag that can be passed as variables to PHP and Javascript Hanna codes. These attributes can be specified either in HTML attribute format or ProcessWire selector format. In either case, quotes should be used around the attribute value when the value contains whitespace or a comma. How to install Place the module files in /site/modules/TextformatterHannaCode/ In your admin, click Modules > Check for new modules Click install for TextformatterHannaCode Now to go Setup > Fields and locate the Textarea field(s) that you want to use Hanna codes with ("body" for instance). When editing the field, click the details tab, and select "Hanna Code" as the Textformatter. Save. Now go to Setup > Hanna Code and start defining your Hanna Codes! You may want to use one of the examples from this document to get started. Tag format Below is a Hanna code tag named hello_world with no attributes. If you pasted this into your body copy, you would get whatever the replacement value is that you defined. [[hello_world]] Below is a Hanna code tag named hello_world being passed attributes of foo, bar and foobar. If this were a PHP-based Hanna code, it would receive the variables $foo, $bar and $foobar: [[hello_world foo="bar" bar="foo" foobar="foo bar"]] Below is the same Hanna code tag as above, but with attributes more like ProcessWire selectors. You can use whatever format you prefer. Just note that unlike regular ProcessWire selectors, quotes (single or double) are required around any value that has whitespace. [[hello_world, foo=bar, bar=foo, foobar="foo bar"]] How to use Please make sure that you have completed the How to install section first. Then in your admin, go to Setup > Hanna Codes. Each Hanna code that you add has a type of either: Text/HTML, Javascript or PHP. The Text/HTML type is literally self explanatory in that your [[custom-tag]] is replaced with exactly the text you paste in. Anywhere that you type your [[custom-tag]] in your body copy will be replaced with exactly the static text you defined. More power opens up with the Javascript and/or PHP types of codes. These codes execute at runtime and thus can contain specific logic to produce different results. In fact, PHP Hanna codes have access to the entire ProcessWire API and are executed in the same manner as template files. Your PHP-based Hanna code should simply "echo" or "print" the replacement value. PHP example Create a new Hanna code with the name "children". Select "PHP" as the type. Paste in the following for the code: foreach($page->children as $child) { echo "<p><a href='$child->url'>$child->title</a>"; } Now go and edit a page that has children. In the body copy, enter [[children]] in the place where you want the output to appear. View the page, and you should see the rendered list of links to children. PHP example, part 2 Now lets take the above example further... Go back and edit your "children" Hanna code, as we are going to modify it to respond to a "parent" attribute. Change the code to this: if(isset($parent)) { // If $parent is an ID or path, lets convert it to a Page $parent = $pages->get($parent); } else { // otherwise lets assume the current page is the parent $parent = $page; } foreach($parent->children as $child) { echo "<p><a href='$child->url'>$child->title</a>"; } Go back and edit the page where you previously inserted the [[children]] tag, and change it to: [[children, parent=1]] (specifying the homepage) or [[children, parent=/path/to/some/parent/]] if you want to try something else. View the page and you should now see it showing the children of the homepage (or of another parent you specified). Please see the Javascript and PHP usage notes on the Hanna code entry screen. Security There are major security implications with a tool that will let you enter unfiltered text and code from your web browser. As a result, Hanna codes are meant for definition only by superusers and we recommend keeping it that way. Download Download the Hanna Code module from the ProcessWire modules page or from GitHub.

Just wanted to share what I recently used to create forms in modules and in frontend using the API and Inputfield modules PW provides and uses on its own. I think many newcomers or also advanced user aren't aware what is already possible in templates with some simple and flexible code. Learning this can greatly help in any aspect when you develop with PW. It's not as easy and powerful as FormBuilder but a great example of what can be archieved within PW. Really? Tell me more The output markup generated with something like echo $form->render(); will be a like the one you get with FormBuilder or admin forms in backend. It's what PW is made of. Now since 2.2.5~ somewhere, the "required" option is possible for all fields (previous not) and that makes it easier a lot for validation and also it renders inline errors already nicely (due to Ryan FormBuilder yah!). For example the Password inputfield already provides two field to confirm the password and will validate it. De- and encryption method also exists. Or you can also use columns width setting for a field, which was added not so long ago. Some fields like Asm MultiSelect would require to also include their css and js to work but haven't tried. Also file uploads isn't there, but maybe at some point there will be more options. It would be still possible to code your own uploader when the form is submitted. Validation? If you understand a little more how PW works with forms and inputfields you can simply add you own validation, do hooks and lots of magic with very easy code to read and maintain. You can also use the processInput($input->post) method of a form that PW uses itself to validate a form. So getting to see if there was any errors is simply checking for $form->getErrors();. Also the $form->processInput($input->post) will prevent CSRF attacks and the form will append a hidden field automaticly. It's also worth noting that processInput() will work also with an array (key=>value) of data it doesn't have to be the one from $input->post. Styling? It works well if you take your own CSS or just pick the inputfields.css from the templates-admin folder as a start. Also the CSS file from the wire/modules/InputfieldRadios module can be helpful to add. And that's it. It's not very hard to get it display nicely. Here an code example of a simple form. <?php $out = ''; // create a new form field (also field wrapper) $form = $modules->get("InputfieldForm"); $form->action = "./"; $form->method = "post"; $form->attr("id+name",'subscribe-form'); // create a text input $field = $modules->get("InputfieldText"); $field->label = "Name"; $field->attr('id+name','name'); $field->required = 1; $form->append($field); // append the field to the form // create email field $field = $modules->get("InputfieldEmail"); $field->label = "E-Mail"; $field->attr('id+name','email'); $field->required = 1; $form->append($field); // append the field // you get the idea $field = $modules->get("InputfieldPassword"); $field->label = "Passwort"; $field->attr("id+name","pass"); $field->required = 1; $form->append($field); // oh a submit button! $submit = $modules->get("InputfieldSubmit"); $submit->attr("value","Subscribe"); $submit->attr("id+name","submit"); $form->append($submit); // form was submitted so we process the form if($input->post->submit) { // user submitted the form, process it and check for errors $form->processInput($input->post); // here is a good point for extra/custom validation and manipulate fields $email = $form->get("email"); if($email && (strpos($email->value,'@hotmail') !== FALSE)){ // attach an error to the field // and it will get displayed along the field $email->error("Sorry we don't accept hotmail addresses for now."); } if($form->getErrors()) { // the form is processed and populated // but contains errors $out .= $form->render(); } else { // do with the form what you like, create and save it as page // or send emails. to get the values you can use // $email = $form->get("email")->value; // $name = $form->get("name")->value; // $pass = $form->get("pass")->value; // // to sanitize input // $name = $sanitizer->text($input->post->name); // $email = $sanitizer->email($form->get("email")->value); $out .= "<p>Thanks! Your submission was successful."; } } else { // render out form without processing $out .= $form->render(); } include("./head.inc"); echo $out; include("./foot.inc"); Here the code snippet as gist github: https://gist.github.com/4027908 Maybe there's something I'm not aware of yet, so if there something to still care about just let me know. Maybe some example of hooks could be appended here too. Thanks Edit March 2017: This code still works in PW2.8 and PW3.

Guide to installing ProcessWire on the OpenShift PaaS. Create an account at http://www.openshift.com.'>http://www.openshift.com. Next, select Create Application at the top of the screen and PHP 5.3. Once that is done, add a MySQL 5.1 cartridge to the PHP application. You'll get the following info from creating the PHP app and MySQL cartridge. Setup local Git repository Clone the application's Git repository to your local machine with following command. git clone ssh://51d12b59500446e0df000118@processwire-example.rhcloud.com/~/git/processwire.git/ Fetch the ProcessWire source and code and add them to the php on the local repository with these commands cd processwire git clone https://github.com/ryancramerdesign/ProcessWire'>https://github.com/ryancramerdesign/ProcessWire mv ProcessWire/* php/ mv php/htaccess.txt php/.htaccess rm -rf ProcessWire Push to the Openshift server Commit and push to the Openshift server with following commands: git add . git commit -m 'Setup ProcessWire' git push Complete the ProcessWire setup Acesss and complete the ProcessWire setup at your application's URL: http://processwire-example.rhcloud.com Use the IP address for the MySQL DB, in this case, 127.7.170.2 instead of the environment variable, $OPENSHIFT_MYSQL_DB_HOST

I didn't know this one Shortest way to echo a variable only if populated (using pw fields of course ): echo $page->field?:''; and: echo $page->field ?: "field is empty"; // echoes field content echo $page->empty_field ?: "field is empty"; // echoes "field is empty" or even: echo $page->field1 ?: $page->field2 ?: "they are all empty";

Hi all, we lauched this big website for a festival last week, and pout a lot of work and love into this. Check out: boomfestival.org Hope you like it! and it has been received very well so far.. ( 60 000 visits in less then 1 week) It uses processwire as CMS , and I must say awesome decision to replace Wordpress we used the last editions, processwire is highly superior to wordpress as CMS . I even managed to import a lot of content from Wordpress with the Processwire bootstrap API and JSON and the help of this forum Content is loaded all with Ajax , and still backbutton does work and everything can be deeplinked . Ryan ProCache module has helped very much with Site speed and our high traffic server load If I find the time I might do a case study here...as this ajax approach moight be interesting for other developers

This is already old news to many of you here, but I finished writing up the full announcement today so figured I should post it (click the link below). Numerous upgrades and refinements make ProcessWire 2.4 our most friendly and powerful version yet! ProcessWire 2.4 is focused on listening to the feedback from of our users and answering with the best CMS experience for web designers/developers and their clients. Read the full announcement. For those upgrading from a previous version of ProcessWire, please read all of the upgrade instructions. Hope that you enjoy this new version! A huge thanks to Avoine for sponsoring the Field Dependencies feature new to ProcessWire 2.4!

Thanks Soma, This issue is a party killer.

Btw with my brillant memory I remembered this one https://github.com/ryancramerdesign/ProcessWire/issues/358

That was not meant to be a solution...."in the meantime...." I said... ....anyway, back to topic; sorry I digressed and sort of hijacked this thread..

foreach($page->children("sort=DMCContact_Country") as $child) { $class = $page === $child ? " class='on'" : ''; if($child->DMC_represented!=0) { echo "<li> <a$class href='{$child->url}'> <span class='label label-default'> {$child->DMCcontact_Country}</span> {$child->title}</a></li>"; } }

Well, technically speaking, not at the same time, but immediately after changing the general settings. A bit more infos would be nice. How do your current selector / API calls look like? What's the relation? Is there a hierarchy (parent -> children), or just "all pages with template X"? What does your logic for the frontend look like? A simple way would be to create another field in the parent (if you have a hierarchical structure) acting as a flag. If your admin wants to override all pages with a general setting valid for all pages, that flag would be changed from 0 to 1 (or whatever you choose). In your frontend / tpl logic, you'd first read that flag value, and only respect individual page settings if it's set to 0.

I assume you are talking a front-end form using the API? You can make it transparent to the front end user. Have your form processing code save the page using whatever field you want for the title/name of the page, then $newpage->save(), then process the rest of the form fields including the file upload and then save again. Does that make sense?

Thanks! One of the things with writing music is that I have become hardened to people not seeing value. Mostly when a client signs off and I do the final arrangement and vocals, I get no feed back at all. They just pay the bill and use it. I have no idea whether the end client (I deal with stations or agencies) was in love with it or just thinks it is doing the job. The very rare occasion I get a client phone up and say nice things is therefore a huge bonus - though cash would also be nice! Interestingly, I did get that recently on a set of sung commercials I did that I wrote in the style of a West End musical. That one they did bother to comment on. Its at the front of my recent show reel (and a second version at the end): http://dancingbear.co.uk/site/assets/audio/showreels/DancingBear-Feb2014-recent.mp3 I did once get annoyed about it - I had written and produced this 3 minute orchestral piece with a big vocal over the top; I was very pleased with it. The client liked it but asked "where do you source your tracks to sing over?" I have no idea what he thought the £3000 he had just paid me was for!!!

Thanks to Apeisa I'm currently doing some work in UIKit and loving it. They all come with a certain amount of baggage, but I'm finding that compared to Foundation UIKit is a bit more straightforward and, well, if I had the time and expertise it's probably how I would have built a framework. Plus it looks nice.

Thank you very much!!!! All works.

Not exactly sure what you are still having problems with, but this line: if $page->parent->name=categories { needs to be: if($page->parent->name=="categories"){ Same goes for the years if statement. Does that fix things for you, or are there other problems?

@adrian: http://processwire.com/talk/topic/2942-or-in-pw-selectors/?p=29001 On a mobile so I'll be very brief, but just wanted to add that the original issue is exactly what error message says: id field and %= can't be used together. You could use a combination of two finds (fetch two PageArrays and merge them) to achieve this, though someone might know better way too..

That kind of selector isn't supported yet, see roadmap for 2.5: http://processwire.com/about/roadmap/ (either-or)

To be honest I haven't actually used that module until now. I am also having issues with the selectors you are trying, but the following all work fine: path=/about/ id=1,path=/ path%=/about/ I think it is logical that %= wouldn't be supported for id, although I can see the issue when you're trying to combine OR's like that. Not sure if that really helps, but I am sure Ryan or someone else more familiar with that module will chime in soon.

this is also interesting: https://www.yootheme.com/component/blog/2013/08/13/how-big-is-uikit

Many thanks. Have installed it.

Just deployed a new PW site for a contemporary classical composer: http://www.jonathandawe.com/ AIOM Formbuilder ProCache Redirects MapMarker ImportPagesCSV MarkupSimpleNavigation Hanna Code Version Control Audio plugins used: Soundmanager2, 360 player with visualizer Fancy Music Player And thanks to the combination of AIOM, Procache and Cloudflare, the site seems to be very fast, gets a yslow of 96-98; Homepage Here is the sm2 circle player example with vis, overlaid on a relevant image: [goodbye joomla....!]

Just stumbled upon this: http://typequest.org/ Type in web is maturing! --- ps: I will watch Porto playing against the club from my second city now

Thanks a lot, hoping we'll see a 2.4.1 soon with a few fixes.

Filed an issue, as I was able to reproduce this. https://github.com/ryancramerdesign/ProcessWire/issues/358

You'll want to test ahead of time, but I think it'll still work. There are some bugs and security issues in PHP 5.3 versions prior to 5.3.8, which are good reasons for nobody to use those versions. That's the main reason I set 5.3.8 as the minimum. But the reality is that it should still work fine in any 5.3. Chances are it would still work fine in 5.2 as well, but I want to take that monkey off our back so we can move forward.

Hi Joss, Why not design it from scratch? I understand that BS and Foundation are fast starting points but don't they just complicate things by having to sift through all their code to work out what does what? Not to mentioning loading code you never use. BTW on your Stony site there's a typo in the footer: Site Design ©2012 Stony Webistes