swampmusic

HI, I have a newbie question, seem to have got myself into a twist trying to get related pages showing home- - destinations - continents - africa - country1 - country2 - country3 - hotels -hotel1 -hotel2 -hotel3 The country template has a title textfield that stores country name eg; France, Italy, etc.... It also has a page select field that retreives all the hotels using this code... so i can show some hotels on the country page. return $pages->find("template=hotel"); The hotel template has a page select field that retreives the countries for africa using... parent=/en/destinations/africa So each hotel has a country stored on its record using the page select field My problem is that in the php for the country template I need to filter the hotels for only hotels in that country... for example.., return $pages->find("template=hotel, hotel.country = this country.name "); the field filter above is psuedo code it's the bit i can't figure out how to work. Any ideas ?

Oof! that looks exactly like we need! Thanks. Will be in touch soon.

First up, a massive thanks to Ryan, the developers and community on this great CMS. We have spent the last 4 weeks looking at the best option for a client and it looks like ProcessWire will be the choice. We ignored the top 3 (Drupal, Joomla, WordPress) but spent a lot of time with Grav, Hugo, Concrete5, October and PimCore before we arrived here. I am not saying some of these are not great as well, but sometimes the best CMS is the one that matches your needs the most. I can't tell you how much of a pleasure it was to find your CMS and community So, one of the things we have seen that our client likes a lot is how many other systems handle Image and Asset Library. They like to be able to upload many 1000's of images, PDF's that get used on many different Pages. Content Editors can quickly find images from a tree/directory/tag structure and Drag and Drop over onto their pages. My question is anything like this on the roadmap ? If not, then does anyone in the community have a pointers or ideas on best practise to implement this ( a module? ) or is it something ( a use case ) that does not sit well with the way Processwire wants to be architected? Again, fantastic work folks, we are really enjoying Processwire and looking forward to looking at the ProDrafts & ProForms modules as well in a few weeks.