Leaderboard

Thanks guys! I started using thomas' suggestion when I read it, and it works great. It's not perfect but at least most of it is properly aligned. I guess I have to let it go and stop worrying about indentation. Although sometimes, I really have to, because I teach part-time and I want the students to be able to read my examples easily. And yes, I'm introducing processwire to my students, instead of joomla and drupal which other schools usually use to teach cms. So there's hope that future web developers would be using processwire more and more! Thanks again!

Okay, it seems I have some more reading and comprehension to do then. I really don't want a redirect, but after reading yellowled's response it then got me thinking about using a ("clone"?) template that could request a page fieldtype and simply pull all of its information. The only difficulty stemming from that would be requiring users to then manually find the original source to modify the content. ... but somartist might have a slightly nicer implementation (I'll have to look it over more carefully to see what it truly does). I'm about to leave for a 4 hour drive to visit family for an extended weekend, so I have not had a chance to fully grasp every one else's responses, but I wanted to drop in really quickly and say "THANK YOU!" as it not only shows the power of Processwire, but also the strong community support. You're all awesome. Hopefully Monday evening when I get back I can look this over and get a much clearer sense of it all.

Isn't word press printing technique? You know, you put words together from iron letters and then press it?

Hi all, Here's my first site using Processwire, a site for a friend of mine who is an illustrator. There's still a fair bit of tidying up to do but this is what I have so far... Feedback more than welcome. Processwire is an incredible framework, I'd use it again and again for projects now. Thanks for all of the hard work put in to making such a great tool. Anyway, here's the site: http://amberanderson.co.uk/ Thanks!

maybe store a json string in the description field?

http://www.washedashoredesigns.com/ Dont judge the minimal styling and papyrus font... All original art and craft things speak for themselves + the smallest css ever There is a css bug that occur when I moved my html and css from flat file mockup to process wire templates The border appears and dissappears at will, its almost like the image is a pixel bigger and overlapping it (possible?) Css: #feature img { border-top:thin; border-style:solid; border-color:#000; } Now on the front page image I can only see bottom border. Also can be observed on the gallery pages where bottom border appers to be the only one missing

'lead' => 'leading' 'iron' => 'ironing' ?

I'm running 21k pages on one site right now, and no difference in speed than if it was running a dozen pages. Though of course, I'm not doing anything that loads all those 21k pages at once (I don't think that would even be possible).

Not yet tested, but I will give a little test drive this weekend.

It's multi language domain translation function. Makes text in templates and modules and admin translateable. http://processwire.com/api/multi-language-support/

No its not possible. Kinda very special case. Well u could try making it max levels 3 and hide third level with css and open on click.

Another review in german: http://lukasepple.de/blog/2012/08/grundlagen-processwire/

There's different approaches to how it can be archived. I'm building a shop with products with multiple categories possible. I'll quickly show how it's done. Create template "category" only with a title field. Then build a tree structure that will be hierachical and serve as the navigation. The template need to have urlsegments enabled. That will enable to display products under a category. So the url will be something like /shop/category1/product1/ and in another category the same product /shop/category2/product1/. This will make it easy to have a highlighted navigation. The product template will have fields you need and create them under one separate tree. In that template you add a page reference field "categories" that has set the categories tree parent as parent, and a multiple select to browse and select them. Then this following php code will handle the navigation and rendering of the products. This is in the template for the category template. $prod = null; $nav = $modules->get("MarkupSimpleNavigation"); /* * * If on shop category pages * All category pages use "shop" template * "shop" template has url segments and page numbers enabled * So urlSegment is always the first (1) when browsing the categories * Once the page is of type "product" we use that information to output details * * This most easy setup with navigation and categries nested unlimited * and multiple categories per products * */ if($input->urlSegment1){ // the page is a product? if($pages->get("name=$input->urlSegment1")->template == "product"){ $prod = $pages->get("name=$input->urlSegment1"); $current = $page; } else { // else we get current page $current = $pages->get("name=$input->urlSegment1"); } } else{ // in case we are on a "normal" page, do different stuff $current = $page; } $root = $page->rootParent(); echo "<div style='float:left;width:30%'>"; echo $nav->render(null,$current,$root); echo "</div>"; echo "<div style='float:left;width:68%;margin-left:2%'>"; // detail page if($prod){ echo "<h2>$prod->title</h2>"; echo "<p>$prod->body</p>"; } else { // list page $prods = $pages->find("template=product, categories=$current, sort=title"); foreach($prods as $p){ echo "<p><a href='$page->url$p->name'>$p->title</a></p>"; } } echo "</div>"; There's variations how this can be setup, but this gives a very easy and flexible setup, with a navigation that is highlighted and can have multiple categories for one product.

If you would want to test this you can turn it off in your config.php /** * protectCSRF: enables CSRF (cross site request forgery) protection on all PW forms, * recommended for improved security. * */ $config->protectCSRF = false;

I wouldn't do it that way though if it's going to be the case that you have pages in multiple locations a lot of the time. Take for example your first structure - most ecommerce packages would handle this y creating the category structure, then adding products and ticking a box in a category lost to assign that product to multiple categories. When browsing the structure you would have a URL of vacuums/wet-vac-cleaning-solutions and under that it would list your product, but when you click on the product it would appear at a URL of something like products/super-clean-2000 I would suggest handling it this way as well, as I'd you use redirects you're essentially taking the user from one category to a completely different category which would make them a bit confused I think. As such, I would make the structure of your categories under a page called "categories" and create a template for those pages called "category". Then create a page called "products" and a template called "products" for it to use. The product template would need a field called "categories" that uses the Page fieldtype which is set up to allow selection of all pages under the category page. You then simply add products and select the categories they appear in When editing the front-end categories template to show the relevant products in that category you can simply use a selector to find all products that are in that category. Sorry, that's a whistlestop tour of how I'd recommend doing it and doesn't sound simple, but it is pretty easy in reality and not as daunting as I've probably just made it sound

A huge milestone for PW, thank you for releasing this to public. Agreed on comments above, very handy study material.

The necessity to include "virtual" pages in the page tree comes often from the customer. So you have no choice. Then <a href="<?=$page->get('redirect_url|url')?>"><?=$page->title?></a> instead of a redirect is preferable. But there is an other reason you might wish this "short cuts". If you expect external links to change frequently and you have them scattered over your site you would appreciate the benefit of changing them only at one well known place. So if you do some work on it, I suggest not to limit yourself to the menu.

Never heard of it.