| Redisplay Messages: Compact | Brief | All | Full Show Messages: All | Without Replies| Author: | qwertyboy  | | Posted: | Feb 18, 2024 22:44 | | Subject: | Re: Adding Canada to my store | | Viewed: | 36 times | | Topic: | Shipping | |
| In Shipping, 1001bricks writes:
| | Much more; our TGV fast train tracks (200 MPH) would be incompatible with all
yours snail trains LOL!!!
|
Mwah. Looks like the French can't even build new trains that are compatible
with their own infra...
https://time.com/108252/france-trains-too-wide/
Niek.
|
 |
| Author: | qwertyboy | | Posted: | Feb 6, 2024 11:39 | | Subject: | Re: Massive refund error | | Viewed: | 48 times | | Topic: | Technical Issues | |
| In Help, 1001bricks writes:
| | In Help, Ziegelmeister writes:
| | In Help, 1001bricks writes:
| | Nubs_Select talked about this.
It's a bug I see since the Refund page exists.
When you've input any amount in the "Refund amount Buyer will receive"
field, then using your mouse to scroll either up or down will increase or
decrease the value by increment of 1 (ex: 12.37 = 13.37, 14.37, etc)
Which can also lead to negative numbers.
But a few times I was to validate a refund which in the end was 1 or 3€ more
than what I typed because of this. Of course it's more difficult to notice
if you've a non trivial number like 12.37 which can become 13.37 without
you to notice.
In short, after clicking "Review refund" CAREFULLY double check the amount,
it may have changed since you typed it 
Note it's the same in a Shop page, you may type 4, scoll down, and buy 2...
|
... But... When I tried to replicate this after Nubs mentioned it above, I
scrolled up, down, left, right, expanded, contracted... nothing changed.
|
Depends the position of your cursor, the rotation speed or start time, many things...
Here I can make it happen 100% of the times.
Confirmed to happen here on Firefox and Nubs on Opera IIRC - at least, didn't
try other browsers.
|
The behavior of the mouse scroll wheel updating the contents of a "number"
input field is the default behavior on most browsers. This can be disabled with
a small tidbit of JavaScript (you can disable events generated by the scroll
wheel with a "blur()" override).
For devs: please let me know if you need more specific info.
Niek.
|
|
| Author: | qwertyboy | | Posted: | Feb 2, 2024 16:04 | | Subject: | Re: Bricklink API - Update Store Inventory | | Viewed: | 52 times | | Topic: | Technical Issues | |
| In Technical Issues, ErwinNL writes:
| | The fix is to specify the "description" field.
{"quantity":4, "description":""}
Works fine and fixes it as far as I can tell.
|
I can't help but think someone at BL was a bit overzealous. With the merging
changes, the advice from BL was to put some text in the "description"
field to specify mold differences. Maybe this was construed as "now everything
needs a description", so the API was changed to now require a "description"
field...
Niek.
|
|
| Author: | qwertyboy | | Posted: | Feb 2, 2024 10:12 | | Subject: | Re: Bricklink API - Update Store Inventory | | Viewed: | 58 times | | Topic: | Technical Issues | |
| In Technical Issues, BigBBricks writes:
| | In Technical Issues, qwertyboy writes:
| | In Technical Issues, minithings4life writes:
| | Admin Russell, you did not understand what BrickFreedom was posting.
The API that updates inventory by a quantity (+ or -), is intermittently breaking
on part numbers that are not within your 4 changed parts.
This will break every piece of software that relies on updating Bricklink store
inventory using the API method.
|
I concur. The last failed update on our end was for
There were no other parts involved in this update attempt.
Niek.
|
Same error, did you happen to have a sale on BO for those four items?
|
Yes.
Niek.
|
|
| Author: | qwertyboy | | Posted: | Feb 2, 2024 00:06 | | Subject: | Re: Bricklink API - Update Store Inventory | | Viewed: | 54 times | | Topic: | Technical Issues | |
| In Technical Issues, minithings4life writes:
| | Admin Russell, you did not understand what BrickFreedom was posting.
The API that updates inventory by a quantity (+ or -), is intermittently breaking
on part numbers that are not within your 4 changed parts.
This will break every piece of software that relies on updating Bricklink store
inventory using the API method.
|
I concur. The last failed update on our end was for
There were no other parts involved in this update attempt.
Niek.
|
Next Page: 5 More | 10 More | 25 More | 50 More | 100 More
|
|
