Profile: comichael

  • 25

As far as I understand it is not possible to combine filtering on product specification attributes and manufacturer.

I think this feature is wanted and will be appreciated by many stores.

Thursday, July 11, 2019 1:34 PM

We're discussing how to have "assembly" as an option when customers buy our products.

Example: Customer buys 4 tyres and 4 rims. Assembly is optional - checkbox, adding price 100 x 4 = 400

How would you go on to implement this? Any suggestions are highly appreciated.

Wednesday, June 26, 2019 10:36 AM

Thx, we'll try that solution.

Monday, June 17, 2019 9:49 AM

Do you have any suggestions how to show environmental tax in Orders / Payments?


Base price: 40 €
VAT: 10 €
Environmental Tax: 1 €
Total Price: 51 €

Saturday, June 15, 2019 12:31 PM

Thanks. We have a programmer dedicated to create a plugin to set tier prices via API, but I think tier prices is very crucial for a multi-store setup, so I just added this suggestion:

Tuesday, May 21, 2019 11:54 PM

POST /odata/product('id')/SetTierPrice

"StoreId": "5cbd689806606e0001165210"
"Price": 123

Ignore these:
"CustomerRoleId": null,
"Quantity": 0,
"StartDateTimeUtc": null,
"EndDateTimeUtc": null

Tuesday, May 21, 2019 11:26 PM

Thanks a lot, I'm impressed how quick u found & fixed that.

Thanks for great support as always!

Tuesday, May 21, 2019 11:56 AM

Hi.  We’re trying to use Web API method /odata/product('id')UpdateStock, but StockQuantity in ProductWarehouseInventory is not updated.

For the product we are testing, UseMultipleWarehouses is set to “true” and has existing inventory like this:

"ProductWarehouseInventory": [{"_id": "5cc3cdeb06606e00011f0532", "WarehouseId": "5c6697183945712d04312fc8", "StockQuantity": 10,             "ReservedQuantity": 0}],

We are sending the following body, and receive  HTTP/1.1 200 OK.  {"WarehouseId": "5c6697183945712d04312fc8", "Stock": "123"}

However StockQuantity is not updated for this product.

More info:
ProductID: 5cc3cde406606e00011f03f8
API REQUEST = POST TO http://[webstoreurl]/odata/product('5cc3cde406606e00011f03f8')/UpdateStock
API RESULT: = HTTP/1.1 200 OK {"@odata.context": "http://[webstoreurl]/odata/$metadata#Edm.Boolean", "value": true }

Do you have any suggestions why this fails?

Tuesday, May 21, 2019 4:38 AM

| create a simple widget, which changes what you want. Without changing the application core.

Been looking at this 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?

Saturday, May 11, 2019 10:59 PM

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

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.

Friday, May 10, 2019 1:10 AM