Saturday, May 25, 2019 9:26:25 PM
  • Posted: Monday, May 6, 2019 10:07 PM
  • 21
One of my requirements is that it is possible to select multiple specification values in the product filters search.

Example: Specification attribute "Tyre Dimension", should be able to select both "17" and "18".

I realize this can be changed in _FilterSpecsBox.cshtml (change from hyperlinks to html select list), and also controller code etc.

Question: Is it possible to apply changes like this, and still be able to merge future versions of GrandNode to our solution?  Do you have any suggestion how we should set up the structure to handle issues like this?
0
  • Posted: Tuesday, May 7, 2019 12:13 PM
  • Moderator
  • 244
Hi,

I didn't understand the question. Basically, now you are able to select both dimensions. If you select 17, it will appear in the bottom of the filters section, then you can select also dimension 18 and you will see products with the first and the second dimension. Correct me, if I'm wrong.

Best,
Patryk
0
  • Posted: Friday, May 10, 2019 1:10 AM
  • 21
Hi again Patryk, thanks for your reply.

You're right about the application logic, but I realize that the example I mentioned needs some explaining.

Requirements = Create a filter where each specification attribute is represented with checkboxes that can be turned on or off. This is similar to filtering in f.ex Booking.com.

This allows that the user  

1) can see the active filter in the same visual context where it was turned on
2) can turn off the filter in the same visual context

As mentioned, I realize this can be changed in _FilterSpecsBox.cshtml (change from hyperlinks to checklist + handle in code).

Is it possible to apply changes like this, and still be able to merge future versions of GrandNode to our solution?

SInce your software is open source: If we implement this, will you add it to the “core? I don’t know much about this, have never participated in any open source projects.
0
  • Posted: Friday, May 10, 2019 9:34 AM
  • Moderator
  • 244
Hi,

Thanks for explanation. I understand it now.

To be honest, the most easiest way to handle it, if you don't want to publish it globally, is to create a simple widget, which changes what you want. Without changing the application core.

You can always make that change in the core and create the pull request, if it will be ok, we will with pleasure add it to the project, without problems.
0
  • Posted: Saturday, May 11, 2019 10:59 PM
  • 21
| create a simple widget, which changes what you want. Without changing the application core.

Been looking at this http://docs.grandnode.com/widget-plugin but have to admit it's not easy to understand.

(I guess this would be easy if we had experience with nopCommerce, or if we knew the full architecture of GrandNode, but we don't.)

Could you show how to replace an existing feature using a widget plugin?

0
  • Posted: Tuesday, May 14, 2019 12:54 PM
  • Moderator
  • 244
We are working on the upgraded developer guides, for now you can check some existing widgets in GrandNode.
0