zyON

Teppo, Thanks!

What is the best way to define the default search fields for the Admin search (right now it's set as title and body)? Thanks.

@ryan, Thanks a lot for the explanation and example. This should come in handy very soon...

A little bit far from Portugal, but it's not impossible. Never visited Switzerland so it's another good reason to do it .

Wanze, Thanks for your help. Ryan has answered my question for this topic (that I mentioned on the original post for this question) here.

Ryan, That's exactly what I'm looking for. That's a clean and more efficient way (as mentioned in Soma's PW Cheatsheet, the count() method has less overhead as it doesn't load the pages). You are right, each product under /catalog/men/suits/ has a brand and a collection as a page reference. Now about the after hook, that made me really curious and maybe it's a bit soon for my current level of PW hacking but if you can spare some time to give me some basic instructions or point me in the right direction I'll be really happy . Thanks.

Yes, both brand and collection are to appear on the URL. I've them set up as Page Reference Fields, what I'm looking for is a good way to get for example in site.com/products/man/brand1/ All the Man collections of brand1. But I only want the display the collections that have products in them (some can be defined but empty or with products from another category). A product can only belong to one brand and collection.

kongondo, Thanks, l was reffering to another topic where I discuss that hierarchy. Anyway its somehting like this: - Products -- Brands -- Collections -- Man --- Product1 --- Product2 -- Women --- Product1 --- Product2 So in this case, A product (like product1) is displayed like: site.com/products/man/brand/collection/product1 In this case, brand and collection are shared categories.

I've been working with ProcessWire in the last few weeks trying to come up with this kind of structure and getting used to the way PW works. I must say I'm pretty impressed with it... The flexibility and ease of use that it provides is mind boggling. Picking up on this example and the suggestions of how to structure all of this in PW, I've went with way of creating BRANDS and COLLECTIONS as stand alone pages that can be reused with Page selects within the PRODUCT templates. Now, as I'm not defining BRANDS and COLLECTIONS as children of the Categories like MEN or WOMEN whats the best way to get the used BRANDS and COLLECTIONS within those Categories? Ex: /catalogue/men/suits/ All the BRANDS and COLLECTIONS are available under: /catalogue/brands and /catalogue/collections How can I get the used BRANDS (brands that are assigned under /men/suits) and only those? I guess I could use selectors to get 2 page arrays (one with the men suits and other with all the brands) and then compare and extract only the used ones, but that seems kind of costly... Is there another simple way to do it? I know that I can also use straight SQL but before jumping on that I just wanted to get some opinions from the experts . Thanks.

Moved to this topic. I've been working with ProcessWire in the last few weeks trying to come up with this kind of structure and getting used to the way PW works. I must say I'm pretty impressed with it... The flexibility and ease of use that it provides is mind boggling. Picking up on this example and the suggestions of how to structure all of this in PW, I've went with way of creating BRANDS and COLLECTIONS as stand alone pages that can be reused with Page selects within the PRODUCT templates. Now, as I'm not defining BRANDS and COLLECTIONS as children of the Categories like MEN or WOMEN whats the best way to get the used BRANDS and COLLECTIONS within those Categories? Ex: /catalogue/men/suits/ All the BRANDS and COLLECTIONS are available under: /catalogue/brands and /catalogue/collections How can I get the used BRANDS (brands that are assigned under /men/suits) and only those? I guess I could use selectors to get 2 page arrays (one with the men suits and other with all the brands) and then compare and extract only the used ones, but that seems kind of costly... Is there another simple way to do it? I know that I can also use straight SQL but before jumping on that I just wanted to get some opinions from the experts . Thanks.

Replying to my own question, I think I've found the way: Edit Template > Family > Allowed Template(s) for Children

Is there a way to restrict the use of a specific template when creating a new page in the control panel? I've now a hierarchy set up for a product catalogue and several templates for each type of product. The idea is when someone is creating a new product, and it chooses the location of that product in the page hierarchy, it doesn't display the template select box but chooses the appropriate one automatically. PS: I guess you could use Diogo's Admin Custom Pages Module, but I'm too newbie to PW right now :/

Yes, I'm aware of that, but this was important to grasp the concepts in a real scenario.

renobird, Thanks, I wasn't really expecting such a compreehensive reply. It really helped me to understand the relationship between the pages, templates and url segments. Really put me into the right path. Again, brilliant piece of software, great community. Exciting.

Wow. Thanks a lot. I'm trying to wrap my brain around the template concept as defined by PW, and what is still confusing me is if you define the template to handle the URL segments only at the product level, how will you handle the requests for example like this: site.com/catalogue/brand1?

Renobird, Yes, it makes sense. So for example, I could have something like: - Shoes -- Brands --- Brand1 --- Brand2 -- Types --- Type1 --- Type2 -- Collections --- Collection1 --- Collection2 -- Man --- Product1 --- product2 -- Woman --- Product1 --- Product2 And then have a template setup for "Shoes" that will filter out the URL segments to handle addresses like: site.com/catalogue/man/brand1/ or site.com/catalogue/man/brand1/type2/collection2/ The only problem I see (other than the implementation of the actual template that will handle the "hard work") is that you need unique field values to display the products as they will all be under Man or Woman... so the client will not be able to have (or at least to visualize it on the list) products with the same value like "32" for a product that is a man shoe of type1 and from the collection1 and a man shoe of type1 from the collection2 (This actually happens, different collections having similar reference names for a specific product). Of course we could implement an internal referencing system, that would not be a deal breaker.

Renobird, But is there a way to hide those pages (Brands and Collections) from the Page hierarchy? Because it's somewhat confusing to the user to see products listed under man or women but no products under any brand or collection. (Newbie mode now engaged).

Diogo (Nice to see another portuguese user around here), Yes, that's exactly what I need, I wanted to try to keep the url segments like the catalogue structure in the backend, I think thats a really user friendly way. My question is how do I keep that structure without creating pages? (If I use Page fieldtypes like Renobird suggested). Renobird, Yes, I think that's a really good approach, but how do I keep the brands / collections on the URL structure with page fieldtypes?

Hi, First of all, let me say that I was really surprised by the amount of replies and the discussion that was started. Soma was right! This is really a healthy community built around a brilliant piece of software (and I'm still only scratching the surface of it). Thank you all. Now, to complicate things (!) let me try to explain a bit more what I'm trying to achieve: On my original post I mentioned the following hierarchy: Shoes>Brand1>Men>Collection1>Product1 Shoes>Brand2>Men>Collection1>Product1 Shoes>Brand1>Women>Collection1>Product2 (...). But the structure is a bit more complicated, and it's more like this now: Shoes>Men>Brand1>Casual>Collection1>Product1 Shoes>Men>Brand2>Sport>Collection1>Product1 Shoes>Women>Brand1>Fashion>Collection2>Product1 Shoes>Women>Brand3>Casual>Collection3>Product3 But this should also be reflected in the URL itself so it's possible to get a specific product by going to: http://sitename.com/shoes/men/brand1/casual/collection1/product1 or get All the products of a specific Men Brand like this: http://sitename.com/shoes/men/brand1 or even get all the men shoes at: http://sitename.com/shoes/men/ Also the same kind of structure is applied to other products like, say, hats: Hats>Women>Brand1>Collection2>Product1 In the backend, I don't see a real problem not having this hierarchy reflected in the pages but the problem is that I needed the possibility of the client be able to create another brand, for example or another category (like sport, casual, etc). I hope I explained this in a understandable way.

Hi, First of all, I'm starting digging into Processwire after a long search about what CMS to use to tackle this project I need to develop. I'm really loving it. My question is related to this product catalogue I'm trying to develop and just need some info on how to handle it properly. I have a large catalogue of products that a part of those products are related something like this: Shoes>Brand1>Men>Collection1>Product1 Shoes>Brand2>Men>Collection1>Product1 Shoes>Brand1>Women>Collection1>Product2 (...) You get the picture. Now, what's the best strategy to handle this when I want to be able to also get results like this: Shoes>Men (Any Brand) Shoes>Brand2 (Men or Women) Thanks in advance