26

(5 replies, posted in Reporting)

You will find an array of column widths and heading names and variables from some sql that you can comment out or delete.

27

(5 replies, posted in Reporting)

Just blank the headings and displays in the rep107.php file.

Looks like the extensions too must have the function trigger_error replaced by fa_trigger_error too.

osc_orders/osCommerce.php

    $result = mysqli_query($osc, $sql) or trigger_error("Query Failed! SQL: $sql - Error: ".mysqli_error($osc), E_USER_ERROR);

api24/sales.inc

    if ($can_process['passed'] == false) {
        trigger_error(var_export($can_process, true));
        api_error(412, $can_process['message']);
        return;
    }

The commit at: https://github.com/FrontAccountingERP/FA/commit/7092ac6864fd902b61d2c01ba694c4b5dba703fb
solves this issue for the core.

Additionally, the original function trigger_error() could have been retained for those using older extensions with older PHP versions and code.

Refer the wiki

is E_USER_NOTICE available in older PHP versions say 5.x ?
Any best practice for safe degradation?

Just take a backup of your web installation folder of FA for the remote host. I trust you will be doing a windows based local hosting on your desktop. If not suitably modify accordingly.
Match the PHP / MySQL and the respective ini file values to your local environment.
Unpack the web remote web folder backup into your local web setup.
Take a full FA MySQL backup from within the FA remote installation (if data is limited) or a phpmyadmin backup if otherwise.
Then restore them to the local web server re-creating the MySQL databases along with their collation and content.
Make any changes to your FA config.php file in your local install as appropriate.
You should be good to go.

That will be in reporting/rep707.php.

The relevant code is:

function print_profit_and_loss_statement()

The loop is in line 288 within which the elements will need to be alphabetically arranged:

while ($accounttype=db_fetch($typeresult))

Line 273:

$classresult = get_account_classes(false, 0);

too could be checked out.

The lines 40-41 in function display_type

    $result = get_gl_accounts(null, null, $type);    
    while ($account=db_fetch($result))

may need to be sorted for your needs.

A modified version of the rep707.php could be made into an extension to serve your needs. Anyone game?

Change this in php.ini file

; max_input_vars = 1000

To this (removing the semicolon which is commented out)

max_input_vars = 4000

Will need to restart the webserver thereafter.

Reference

Where? In the report? Which report?
Will this sort affect groups' child entries?

Will NULL solve the issue especially if it is to be the field's default?

Using Perplexity.ai

Compile and install PHP 5.6.40 from scratch. What is the linux version on your old and new computer? As MySQL versions too would have changed, check out the differences between the installs.

Your link has expired.

39

(4 replies, posted in Modules/Add-on's)

Updated my unofficial extensions repo at:
https://github.com/apmuthu/FA24extensions/tree/master/Extensions/barcode_sales_helper
with the commit at:
https://github.com/apmuthu/FA24extensions/commit/781630bc4dbb96b25939bc5a91b74cd39e64ff21

Whitespaces synched with core file
Screenshot updated

Kindly update your fileset with this commit.

DB Schema changes can be gleaned from DB Structure backup (phpMyAdmin, SQLyog or any MySQL Client) of old and new installs and compared say using WinMerge, Diff, ExamDiff, etc.

Check for "Deposit Processing" and "Control Accounts" strings in the core module files.

Try to install PHP 5.6.40 in the new one and see if it works.
https://askubuntu.com/questions/761713/how-can-i-downgrade-from-php-7-to-php-5-6-on-ubuntu-16-04
https://stackoverflow.com/questions/59781992/how-can-i-downgrade-or-use-php-7-2-without-uninstalling-php-7-4-is-it-possible

Use the bleeding edge FA v2.4.18+ available at:
https://github.com/FrontAccountingERP/FA/archive/refs/heads/master.zip
as it has the latest fixes.

Check your PHP versions across the installs.
Check the DB Structure changes since then.

Also checkout the fixes in the Import Transactions extension module files from
https://github.com/apmuthu/FA24extensions/tree/master/Extensions/import_transactions

42

(4 replies, posted in Modules/Add-on's)

Is the line 798 (global ...) necessary in:
https://github.com/apmuthu/FA24extensions/blob/master/Extensions/barcode_sales_helper/sales_order_entry.php#L798

@joe: is this a real issue?

44

(4 replies, posted in Modules/Add-on's)

@boxygen: Thanks.
Added it to the unofficial extensions repo with credits to you at:
https://github.com/apmuthu/FA24extensions/commit/cce7361a0973b55e613150196315f85842aadfc2

@joe: test and add to core.

Provide Transaction and Dashboard screenshots.
Is the transaction inquiry displaying correctly?

The integration of all changed strings for the Persian install lang po file and compiled is attached here after updating it in Transifex.

@trafficpest: there was 1 untranslated string in your po file.

@joe: You may add this into the install/lang folder in the core.

My Github link for install lang file:
https://github.com/apmuthu/frontac24/commit/2b014172c6acc1ae741a44254e79cdaa1404cd65

My Github link for the core language file:
https://github.com/apmuthu/FA24extensions/commit/01a0572b921b9d61357fac06f792e7a526fea99a

47

(6 replies, posted in Report Bugs here)

Very good troubleshooting.
Kudos @trafficpest.

@joe: are there any other scripts that will benefit from this?

The core translations for fa_IR are the same as provided in the previous post (no. 8).
The Install translations are slightly different for a few strings from transifex (post no. 7) and in Post no. 8.
Also I have chosen to use fa_IR as that was available in transifex and it has been retained in post no. 8.

Will attempt to synch the install translations soon and provide credits to Nazir in it.

All links provided by Nazir have been downloaded and attached to the respective posts.

As the USD / IRR (Iranian Riyal) exchange rates down due to sanctions, the actual invoicing may exceed the column width of the amounts unless the values are truncated to 1000s and decimals discarded.

The USD / AFN (Afghan Afghani) is twice as bad due to even more sanctions and the same would apply here as well for column widths of amounts.

Contact forum user @smjazayeri1986 from Iran for further collaboration.

Spoken Tutorial for FA in Persian from IIT Bombay.

Welcome to Farsi (Persian) users of FrontAccounting ERP!

The install/lang file for fa_IR is attached herein.
Native speakers may provide edits.

@joe: Maybe you can add it into the core?

Compiled version for fa_IR

You can also make your Chart of Accounts at:
http://www.apmuthu.com/fautils/make_coa.php