Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Tyguy7

    (@tyguy7)

    Hey everyone!

    Thank you so much for your interest. I really do want to complete this project. I’ve been slammed the past month, and I don’t see any breaks coming in the near future. I can’t see this happening soon unless I get some collaborators. Consider this a call to any developers out there. I would love to push this all to github and start an open project. Please respond if you would like to be a part of it.

    Here’s a list of working features so far.

    Create custom product filters via drag and drop interface.
    -Create single sliders for zero to x ranges in values
    -Create dual sliders for x to y ranges in values
    -Create checkboxes for lists of values (strings)
    -Create collapsable sub menus for filters( I call them togglenodes )
    -Store multiple versions of filters while setting a single filter as active (allows you to easily revert to old filters or test user response to different versions)

    View attribute and custom field stats per category. (Helps you to see percentages of custom fields and attributes assigned per category, so you can determine what you should and shouldn’t filter by)

    Return results via AJAX

    Works in tandem with search results pages to narrow search by things such as price, color, weight, custom field, etc.

    Caching system that stores numeric ranges for each category to speed up queries. Admins can cron the cache process or run it manually in wp-admin

    Copy and paste entire filters (as serialized arrays) between various categories or wordpress installations.

    There are a few more notable features that I’m forgetting, but this is the majority of the important ones. Please respond to this thread if you are an interested developer.

    Thanks!

    I ended adding a catch for is_search() in wp-pagenavi’s get_url function. Just forced a new param to the end of the url “page” = $paged…

    I am having a similar issue. All pages except page 1 return a 404 error. Previous versions of relevanssi had a paged=pagenumer url argument to control pagination. Now it uses a prefixed /page/pagenumber before the search params in the url. This does not work with my site for some reason. Please help!

    Thread Starter Tyguy7

    (@tyguy7)

    Thank you everyone for your responses! I’ll keep this thread going if I start to develop a public version. It looks like it might be worth the extra effort if enough people are interested

Viewing 4 replies - 1 through 4 (of 4 total)