Adapt for user attributes vs page attributes?
Permalink Browser Info Environment
I'm setting up a radius zip code search using attributes applied to a user (vs. a page).
Any suggestions on where to start with modifying your add-on? I'm thinking I can point it at the user attributes vs. page attributes, and modify the results page to reflect that.
I appreciate any assistance you can offer.
Any suggestions on where to start with modifying your add-on? I'm thinking I can point it at the user attributes vs. page attributes, and modify the results page to reflect that.
I appreciate any assistance you can offer.
| Type: | Discussion |
|---|---|
| Status: | New |
Unfortunately it won't be that easy, although of course, everything is possible.
At the time I wrote the Search Tools, the PageList model was really hard to extend, if not impossible, so I pretty much copied it to my own class and did my changes there. In your case, you'd have to do the same with the UserList model (concrete/models/user_list.php). Once you apply the right modifications there (either by extending the model, re-writing it in another class, or hacking the core) then in theory you could as you say, just re-point the search tools to use your new UserList rather than the AdvancedPageList.
Any of this makes sense?