led24ee

Just to inform. If You have category with slash (/) in name and You try to import products with the slash(/) in category name (the same name that already exist, then result is category with name before slash and subcategory with name after slash. Really annoying.

Preferences - General - Round mode Preferences - General - Round type Preferences - General - Numbers of decimal

Try this : Translation - Installed modules - Beesblogrecentpost

Why do You need to delete it at all ? Just mark not in use.

This is common mistake when many people are writing about on thing. My worst case was 15+ yeas ago with some phone station manual. It takes many hours to understand that station, extension, client and port actually are exactly the same, but different people call it with different name. PS is not free from this. And since TB is based on PS then this can be here too. Maybe this will help somebody.

Yes it is working. Check Your CSV file value separator. In TB You can even set the right separator. There are problems with Client and address importing and also when You try import the same thing in many languages. But products importing in one language works well.

This is fixed in Bleeding Edge. (This is almost like a new version.) Some info in this and in this Hope this will help.

What version are You using ? There were some version with problems.

Some will also understand that nothing is eternal and will be able to determine their next steps based on it. But some are hoping that maybe this current situation will be forever.

I don't understand. You really think that some things will last forever ? Some things was replaced by better items, some are deprecated. It's called evolution. And this simply exist, You like it or not.

It is not easy. But at the moment yes. I need to do most listings again. I ask it because I still hope that this feature will be useful.

Well, looks like I'm only who is interested of this feature. Let's hope there is somebody more. What I find out so far. This system is designed pretty bad. I'm talking about this case when You need to use ASM and product combinations. You just can't. You can't have stock quantity for combinations. You can have only products quantity. The problem is that this ASM adds all combination to related product ID, but combinations share all one ID. I have no idea how to improve this. One solution is to redesign this ASM system. Maybe it is possible to redesign combinations system so that you can put together different products, which have all its own ID. Third possibility is also. I completely didn't understand ASM. In further, this previous designer has something like zero knowledge about price, about FIFO, about weighted average. And thanks to this all the statistic based on prices is also wrong.

This one section was really annoying in the beginning, this wasn't so in PS. Now I'm accustomed. I think these buttons are better to rename. Simplest can add some words like "this section"

Is there any news with ASM ?

Is there any news or plans for release ?

For radio-button issue you can fix this manually or You can use TB1.1 Bleeding Edge. https://github.com/thirtybees/niara/pull/12/files

Thank You.

I know these places. Even if I remove that check in validate.php and change this varchar length in ps_cutomer table I still got warning that ape length must be 5 and can't save longer value.

Somebody knows where is control for $ape length ?

I just tried this and with clean install You can't buy less than minimum. Even if You try to change the amount later in cart then "-" is inactive. I have no idea what happens when You put this minimum up exactly this time when someone put this in cart when there wasn't minimum.

Well. In my shop this "Number of decimals" does exatly what asked. When I put this on 2 there is two places after dot. When I place this on 1 there is still two places after dot, but it is rounded. So there is 123.50 instead of 123.45 And if there is 0 then it is 123.00 instead of 123.45 (TB1.1-Bleeding ...., Niara)

Yes, it is. Preferences -> Round mode, Preferences -> Number of decimals.

Problem with product picture names. I use estonian and english. If I change picture name in one language for only one picture, then in other language all names comes to this what is for first picture. The language stays right, only picture name changes. In both direction, this mean that there is no difference with language I use. In other language there will be always only one name for all pictures. Can anyone confirm ?

In TB depth is like length, at least I use it like this. I have no idea why this is so. Looks like this is similar to "lift" and "elevator" thing.

Height and depth are the same. Just try to imagine that in one case you start measuring from down to up and in other case vice versa.