Jump to content

fuzenco

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

5 Neutral

About fuzenco

  • Rank
    Newbie
  1. Yes, I can imagine it would be complex. I think ExpressionEngine did it by means of an inline group-by. For instance: <li class="whatever" groupby="datacolumn"> And then there was a sort-by also: <li class="whatever" groupby="datacolumn" sortby="whatever">
  2. Generally, this would be a shared template as the homes all contain the same content blocks (title, description, number of bedrooms, number of bathrooms, picture gallery, etc.). The only difference really is the classification of homes. Years ago, I used to work with the CMS Expression Engine which would allow for this type of grouping. I can’t remember how it did it, but it was was useful.
  3. I’d love to learn. I would pay for a tutorial like this.
  4. It’s been a while since I developed a new project with PW, but I have an upcoming client/project that could certainly use SearchEngine. I have a question about search results: Is SearchEngine able to return results into groups? For instance, the client is a home builder/seller. If a user performs a search, it would be nice to return the results as sets. In their case, single-floor homes; two-story homes; etc. That’s just an example. The bottom line is that their homes are divided into categories, so it would be nice if users could see results grouped as such. Is this possible?
  5. What would be awesome is if Form Builder had built-in support for creating Edit and Create ProcessWire page forms that mirrored the back-end forms. I haven't used the module in some time and am getting ready to use it for a new site, but as I understand it: you create fields that are independent of ones already present in back-end forms. The holy grail would be to spit out front-end forms that match the back-end forms exactly. And/or these features: 1) Restrictions on who has access based on member/permissions level. 2) An option to lock down editing of a form to the user that the form data belongs to. 3) Ability—when not exactly mirroring a back-end form—to designate which ProcessWire page should populate a given field. Then have the form update or create those Processwire pages upon submission of the entire form. I know this is crazy stuff I'm rambling about here, but something along these lines just exponentially opens up a whole new world to non-developers. We could create sophisticated apps in much the same manner as we already can on the back-end. Being able to update not just one page, but multiple instances throughout ProcessWire would be mind-blowing.
×
×
  • Create New...