Remove the service product type.
Fixed a bug in
lino_xl.lib.ledger : when the
Account.common_account was updated via the web interface, Lino did not
“realize” this until the server process was restarted.
lino_xl.lib.vat.InvoicesByJournal did not display the right
sorting order. It was using [‘-id’] instead of the order defined in
The detail view to
lino_cosi.lib.contacts.Partners was there,
but there was no detail link in combo boxes on partner fields.
Added a detail view to
lino_cosi.lib.contacts.Partners. While this
view is irritating in applications without accounting, for Lino Così it is
irritating to not have it.
The chooser for
lino_xl.lib.vat.VatDocument.vat_regime had a typo bug
TypeError: get_vat_regime_choices() takes from 0 to 2
positional arguments but 3 were given when user tried to change the vat regime
of a voucher.
Using Ctrl+x on a voucher to run
lino_xl.lib.ledger.Voucher.toggle_state() changed the voucher state but
did not actually register the voucher (i.e. create movements, compute totals,
Show the field vat_id in the “Accounting” Panel for partner and company.
Add a new ‘partner_ref’ field for
store how this partner refers to us. And add this field to the “Accounting”
Released Lino Cosi 19.4.0 to PyPI.
Released Lino Cosi 19.3.0 to PyPI.
A Lino Così application no longer has a default VAT declaration plugin. To
get VAT declarations, you must add something like the following to your local
def get_installed_apps(self): yield super(Site, self).get_installed_apps() yield 'lino_xl.lib.eevat'
lino_book.projects.pierre project now has no VAT declarations at
lino_book.projects.apc has standard Belgian and
lino_book.projects.cosi_ee standard Estonian declarations. Simplified
Belgian VAT declarations is in
lino_book.projects.lydia demo project.
vat_regime field was missing in the detail layout of persons and
2019-02-12 (v 19.2.0)¶
We released 19.2.0 (released 2019-02-12).
Products now inherit from
lino.mixins.refs.Referrable. Because at
least previous TIM users want a
ref field per product. And I imagine
that other users might do so as well. The field is not yet visible in the