Laurent Destailleur

> As a little note: I just came across the problem of dispatching virtual products. Since in this case warehouse locations are managed by sub-warehouses for each item, the components...

Oops i forgot to set the flag to say an enhancement/protection is expected in this method.

It seems this PR was set with "Discussion" or "PR to fix" tag, but no answer nor correction was provided since a long time. So request is automatically closed. Please...

Ok for first point. For the second point, "Second thing if our product status batch was batch, we'll no longer be able to choose serial number, because Dolibarr doesn't know...

the change will break the balance between dol_get_fiche_head() and dol_get_fiche_end(). Musr have 1 end for each head so seems wrong so i close the PR

Still travis errors

@ptibogxiv can you fix the syntax error reported by travis ?

It seems this PR was set with "Discussion" or "PR to fix" tag, but no answer nor correction was provided since a long time. So request is automatically closed. Please...

I did a comparison with how the reception works. Add a new table will make things too different than reception. For reception, detail per batch/warehouse is stored into the table...

A lot of pending PR related to shipment edition were submited with different philosophy and different feature. But all of them was doing a different implementation so were in conflict....