1

(0 replies, posted in Announcements)

Announcement

This is a 2.4.20 stable release with improved PHP 8 compatibility and a couple of usability and security bugfixes.
Therefore please consider urgent upgrade of your installation to this version, to keep your FA instances safe.
This is especially important in not fully trusted environments like publicly accessible installations (demos or other installations accessibly by not fully trusted users).

This release fixes some problems on php versions 8.2 to 8.4. The following versions has been tested: 8.0.0, 8.0.7, 8.0.12, 8.1.6, 8.2.0, 8.3.2, 8.4.13 and 8.5.5.

Please report any bugs/problems found via our Mantis Bugtracker at http://mantis.frontaccounting.com.
Download instructions

In Sourceforge FrontAccounting (http://sourceforge.net/projects/frontaccounting), select
Files -] FrontAccounting 2.4 -]2.4.20.

For Windows users select the zip file. For all other users select the tar.gz file.
Security

FrontAccounting should NOT be used via unsecure http protocol. If you really need this - change SECURE_ONLY constant in /includes/session.inc to false (comment in the file added). Unfortunately this option cannot be added in sysprefs/config.php because the settings are not available before session is started.
Common

● Multiply cleanups/security fixes in attachments editor.
● Database procedures in reports fixed to be compliant with codebase rules.
● Bug [0005737] Attachment editors: fixed input field width to underlying db field size.
● Attachments should be deleted when related document/entity is deleted. Fixes [0005757].
● Bug [0005750] Fixed hangs in barcode generation.
● Feature [0005712] Added fast date input edition with keyboard shortcuts (CtrlAlt-Arrows).
● Install/Activate Extensions: fixed deprecation warning on php ]=8.2.

Sales

● Feature [0005738] Customer/Supplier Allocation Inquiry: changed default sort order to ascending by Due Date.
● Feature [0005752] Customer Statements Report: added customer reference column.
● Feature [0005751] Customer Payments, Supplier Payments: added contractor reference for easier allocations.

Purchases

● $trans_no was missing in purch_order definition class. Fixed.
● Feature [0005738] Customer/Supplier Allocation Inquiry: changed default sort order to ascending by Due Date.
● Feature [0005751] Customer Payments, Supplier Payments: added contractor reference for easier allocations.

Bank and General Ledger

● Added two XRPL Payment Links. By Leslie Proud.
● Changed Bank Account Reconcile to sort descending.
● New exchange-rates organisation update. Can also fetch historical rated.
● Fixed safety issues in bank and audit reports.

This has been fixed and committed to stable repo.

Joe

Fixed and committed to stable repo. Thanks @boxygen.

joe

Cool @boxygen,

I will fix this asap too smile

Joe

This has been fixed and committed. The stable repo is updated.

Joe

I will fix this asap.

Thanks for detecting this!

Joe

Please check that the gd extension is enabled in the PHP.

Joe

This has been committed to stable repo.

Joe

I will have a look into this.

Joe

10

(3 replies, posted in Announcements)

Announcement

This is a 2.4.19 stable release with improved PHP 8 compatibility and some minor bugfixes.

This release fixes some problems on php versions 8.2 to 8.4. The following versions has been tested: 8.0.0, 8.0.7, 8.0.12, 8.1.6, 8.2.0, 8.3.2 and 8.4.13.

Please report any bugs/problems found via our Mantis Bugtracker at http://mantis.frontaccounting.com.

Download instructions

In Sourceforge FrontAccounting (http://sourceforge.net/projects/frontaccounting), select
Files -> FrontAccounting 2.4 ->2.4.19.

For Windows users select the zip file. For all other users select the tar.gz file.

Security

FrontAccounting should NOT be used via unsecure http protocol. If you really need this - change SECURE_ONLY constant in /includes/session.inc to false (comment in the file added). Unfortunately this option cannot be added in sysprefs/config.php because the settings are not available before session is started.

Common

  • PHP 8 bug converting string-float in number_format2. Fixed

  • Some troubles with installation on PHP 8. Fixed.

  • Attachments (more than one) do not follow the transaction after edition. Fixed.

  • Spacing adjustment for report Annual Expense Breakdown, rep705.php.

  • Fixed deprecation warning when user error is triggered on php >= 8.4.

  • Fixed deprecation warning logged when sysprefs object is created on php >= 8.2.

  • Mantis Issue 5753: The company logo cannot be set. $padding in TCPDF class must be inside class declaration.

Sales

  • New feature. Copy Delivery/Invoice from Customer Transactions Inquiry.

  • Mantis Issue 5738. Additional search options for sales order (delivery date, excluding auto) and quotation (valid
    until date) inquires.

  • Mantis Feature 5740: On prepaid Sales Orders, Have a "Receive Customer Payment" option on screen following order
    placement. Fixed.

  • Mantis Issue 5594: Combo box to Customer Credit Note and Supplier Credit Note references. Fixed.

Purchases

  • Mantis Issue 5745: Supplier Credit Note Issue: Stock Move Price Overstated Due to Included Tax.

Items and Inventory

  • Mantis Issue 5745: Supplier Credit Note Issue: Stock Move Price Overstated Due to Included Tax.

  • Mantis Issue 5748: Voiding location transfer results in an increased material cost. Fixed.

This item has been fixed and committed to repository.

Joe

I will have a look into these problems with missing declarations of members in some classes.
We will have to declare them inside the classes.

Joe

Hi, thanks for this.
I have detected the same problem in 8.4 when working in an nginx container with php 8.4.5. I will just contact @itronics to see if he like this idea.

Joe

I cannot reproduce this. Entered a single value on a cash invoice and a bank payment on a 0-date, and both values are correct reported.

So please other users make a simple test for this and report back.

Joe

I guess I will ask janusz to look into this. He wrote these routines, i.e. customer_list_row. Combined with search functions.

Joe

Hi again. Can't find any user with these credentials. Sorry.

Joe

Spam folder? It might have landet here.

Will have a look at this. Thanks.

Joe

This is a fantastic improvement for translators. Thanks Rafat

Joe

Hard to tell. It has to be investigated. The $go_debug variabel should give us some clues. Please continue.

Joe

I will ask Itronics to fix this.

Joe

22

(15 replies, posted in Installation)

Thanks, this item is fixed and closed

Joe

Ok, maybe some other users can give some ideas how to do this. I am out of ideas right now.

Joe

Hello again,

Instead of all these operations why not just setup the Credit Card as a Bank Account.

Use the Credit Card Bank as the default bank on your suppliers.

Just Invoice and pay from the Credit Card.

When paying the Credit Card, use the Bank Transfer to transfer the money from the Checking Account to The Credit Card bank account.

And you are done. Fewer transactions etc.

It is possible to fix your wishes, but the risk for side-effects are enormous and not desirable.

I would avoid the change and use this approach instead. What do you think?

Joe

@jcunning

The problem is that the COGS account for the CC_Payment is an account with an underlying bank account. This is the first time this has happened.
So using a COGS account with an underlyng bank account will not work. The amount will not be posted to the bank account.

Of course this should work, but we will need a check for bank account here and do the transaction.

Will be back.

Joe