It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by apmuthu
Closing the dummy year will forward the closing balances to the new years' opening balances.
Please note that all partial transactions will be abridged into the opening balances unless the dummy year had details of individual transactions that were to be finished in the new year.
Restart webserver if php.ini settings were changed.
Optimise your database and introduce some indexes for certain fields used in the report query.
export out your database and recreate it by importing it into a new structure.
Check if negative values are allowed in the settings.
Check the MySQL and PHP and Apache error logs.
Increase the number of max_input_vars in the php.ini apart from max memory size.
Perplexity.ai and Duck.ai are frontends for the AI chat engine. Just type in your question briefly and you will get the answers.
Check your PM where I answered your queries.
Google search:
https://stackoverflow.com/questions/54126343/how-to-fix-unchecked-runtime-lasterror-the-message-port-closed-before-a-respon
Generally a problem with some browser extension.
Search for the code where the amount comes in as red and prevent it from making an invoice there.
The Credit Limit is set in the table #_debtors_master.credit_limit and the credit_status field therein shows the ID of the record where #_credit_status.disallow_invoices field has the binary switch.
There is a similar field as #_suppliers.credit_limit too.
This is more of a soft cap for credit limit that you can exceed at will. The first time it did not show as the previous balance was under 10K you had set. This is more a server side validation for prompting (red) of the exceeded state.
Check if you find something in red in such an invoice when the amount is reached.
Ask in the Job offers board.
Check out the tutorials from IIT Mumbai - Spoken-Tutorial
Use the Indian CoA and place the file in the FA Webroot/sql folder and create your company with it from the derfault company.
only reporting/rep107.php lines 86-90:
//-------------code-Descr-Qty--uom--tax--prc--Disc-Tot--//
$cols = array(4, 60, 225, 300, 325, 385, 450, 515);
// $headers in doctext.inc
$aligns = array('left', 'left', 'right', 'center', 'right', 'right', 'right');lines 192-199
if ($Net != 0.0 || !is_service($myrow2['mb_flag']) || !$SysPrefs->no_zero_lines_amount())
{
$rep->TextCol($c++, $c, $DisplayQty, -2);
$rep->TextCol($c++, $c, $myrow2['units'], -2);
$rep->TextCol($c++, $c, $DisplayPrice, -2);
$rep->TextCol($c++, $c, $DisplayDiscount, -2);
$rep->TextCol($c++, $c, $DisplayNet, -2);
}You will find an array of column widths and heading names and variables from some sql that you can comment out or delete.
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 = 1000To this (removing the semicolon which is commented out)
max_input_vars = 4000Will need to restart the webserver thereafter.
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?
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.