inconsistent frontend

[jesseyu1984918]

It occurs to me that there are multiple frontend co-existing now and sometimes I'll get tumble one and only if I use incognitive tab it will get me to the latest one, is this expected?

[Rezanmonis]

We are looking for a frontend developer as our teammate for our edtech project [email protected]

[Shinusagi]

I just realized there are few issues with the new frontend so far:

It gives an error when creating/editing some Part/Stock because the verification check of "Allow this change" is not being shown and I assume it is disable by default usually, so it will prevent the registry creation/change.

There is no option to see which Parts you are subscribed to, and thus organize your notifications over them.

The first one is a really annoynig error TBH.

[SchrodingersGat]

It gives an error when creating/editing some Part/Stock because the verification check of "Allow this change" is not being shown and I assume it is disable by default usually, so it will prevent the registry creation/change.

What do you mean by "allow this change"?

There is no option to see which Parts you are subscribed to, and thus organize your notifications over them.

Good point, I'll raise an issue so we can track this

[Shinusagi]

In the old interface if I try to change the count on something I see this:

As you can see there is the "Confirm stock adjustment" option which until enabled won't let save the changes, once you do that everything works fine... however in the new interface:

There is no option and you can click directly on "Submit" but if you do you get this error:

I've seen this issue even creating new parts or stuff, so I thought it was because this setting:

Then tried again and I don't need confirmation on the Old Interface but in the New Interface I still get an error so maybe it is unrelated, not sure what is the issue then but that is the reason I am not using the new interface, sorry.

[SchrodingersGat]

What version are you running? The error in the "count stock" form should be fixed in the most recent version. It is not related to the "confirm" button

[Shinusagi]

0.16.1