Attached is the latest en_IN-new.sql Indian Chart of Accounts. It is committed in my FA24extensions repo.
@joe: can update the pkg repo.
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
Attached is the latest en_IN-new.sql Indian Chart of Accounts. It is committed in my FA24extensions repo.
@joe: can update the pkg repo.
The check must be called before displaying the page so that any alerts can be shown in it. It should degrade gracefully on no suppliers.
Does this happen for attempting a new sales Direct Invoice when there are no customers?
That code and info is for a dated version of FA 2.3.x and needs to be modified for FA 2.4.x. That file was available for fallback purposes in FA 2.3 and stands renamed as
includes/lang/gettext.inc
(the earlier php extension was changed) in FA 2.4. You can alter the include file in the extension to refer to it accordingly. The said file is included in
includes/lang/language.inc
(also so renamed from FA 2.3).
You can export out your invoices in CSV format and import it into FA using the Import Transactions module.
Some REST APIs are listed in the Wiki.
To use any REST API (Simple REST API) for live Invoice synch you need to locate the Direct Invoice page and identify the fields needed. Then acquire those equivalent field values for each invoice in your DOT NET and post it to the REST API or with the necessary pre-requisite credentials and hidden field values (CSRF token), you can post directly into FA. This post may be of interest.
The efforts of the last few weeks that led to this release is fantastic.
The forum activity has been summarised and attached.
The forum continues to receive spam (40% of all email verified registrations) and timely manual monitoring and quick remedial intervention on the part of the devs and conscientious users have kept it relatively clean.
12% of all downloads from SourceForge in the last 3 months are from India as on date. The Spoken Tutorial project's FA Videos and Workshops in India have contributed to it's gaining popularity in India.
Thank you one and all for keeping the FA flag up and waving.
See this post and this wiki page.
In FA 2.4, the lines are 120-122 in reporting/includes/class.pdf.inc.
FA 2.4.x now has a few hidden fields in the login form apart from the ones listed in @elax previous post:
<input id="ui_mode" name="ui_mode" value="1" type="hidden">
..
..
<input name="_focus" value="user_name_entry_field" type="hidden">
<input name="_modified" value="0" type="hidden">
<input name="_confirmed" value="" type="hidden">
<input name="_token" value="iwyLHJUcoMkfRv8-ZpBQVwxx" type="hidden">
The _token field will come up on calling the login form and must be parsed out and submitted with the field values in cURL.
TOKENCODE=`curl -c my_session http://localhost/frontac24/ | sed -ne '/name="_token"/s/.*value="\([^"]*\)".*/\1/p'`
The following would log you in where your admin user's password is "secret":
curl -c my_session \
-F 'user_name_entry_field=admin' \
-F 'password=secret' \
-F 'company_login_name=1' \
-F 'ui_mode=1' \
-F 'modified=0' \
-F 'confirmed=1' \
-F "_token=${TOKENCODE}" \
-F '_focus=user_name_entry_field' \
http://localhost/frontac24/ > logged_in_page.txt
The file "logged_in_page.txt" will contain the html code for the FA's logged in page.
To study the parameters required for the Sales Summary Report:
curl -b my_session \
-F 'Class=0' \
-F 'REP_ID=114' \
http://localhost/frontac24/reporting/reports_main.php > report_form.txt
To get the Sales Summary Report:
curl -b my_session \
-F 'REP_ID=114' \
-F 'PARAM_0=01/01/2015' \
-F 'PARAM_1=10/31/2017' \
-F 'PARAM_2=0' \
-F 'PARAM_3=AutoSalesSummaryReport' \
-F 'PARAM_4=0' \
-F 'PARAM_5=0' \
-F 'Class=0' \
http://localhost/frontac24/reporting/rep114.php > Sales_Summary_Report.pdf
Now to logout:
curl -b my_session http://localhost/frontac24/access/logout.php? > logged_out_page.txt
The "logged_out_page.txt" will contain the html code for the logged out page.
All themes and extensions have been updated with the __construct() syntax.
$module_name property of the hooks extended class in each extension has been made the extension folder name uniformly and used in the menu path formation.
@barbarian: Thanks.
Committed.
The following files too will need to be checked in the extensions:
./auth_ldap/hooks.php:1
./auth_ldap/lib/Ldap.php:1
./auth_ldap/lib/ldap_authenticator.php:1
./hello_world/helloworld.php:1
./hello_world/hooks.php:1
./import_items/hooks.php:1
./import_multijournalentries/hooks.php:1
./import_paypal/hooks.php:1
./import_transactions/hooks.php:1
./import_transactions/includes/import_sales_cart_class.inc:2
./osc_orders/hooks.php:1
./repgen/hooks.php:1
./repgen/includes/repgen.inc:2
./rep_tax_cash_basis/hooks.php:1
./requisitions/hooks.php:1
./sgw_sales/generate_recurring_invoices.php:1
./sgw_sales/hooks.php:1
./sgw_sales/includes/common/DataMapper.php:1
./sgw_sales/includes/controller/GenerateRecurring.php:1
./sgw_sales/includes/db/GenerateRecurringModel.php:1
./sgw_sales/includes/db/SalesRecurringModel.php:1
./sgw_sales/vendor/composer/autoload_real.php:1
./sgw_sales/vendor/composer/autoload_static.php:1
./sgw_sales/vendor/composer/ClassLoader.php:1
./zen_import/hooks.php:1
and these theme files as well:
./exclusive/xpMenu.class.php:1
./exclusive_db/xpMenu.class.php:1
The class renderer in each theme do not have any constructor presently.
Check if it denotes Credit Note from Supplier, otherwise try a negative amount.
Journal Entry should be able to credit / debit just about any account isn't it?
Journal Voucher / Debit Note
Arabic Install Wizard translations are fully done.
Arabic, Hindi and Tamil Install Wizard files are attached.
The set of files that can be used to overwrite their counterparts in an existing FA 2.4.2 installation to update it to FA 2.4.3 is attached herewith.
Tamil, Hindi and Arabic languages stand fully translated in the FA24extensions repo.
Tamil, Hindi and Arabic have their install wizards fully translated too in my repo.
See this post for details and downloads.
Post release commits are listed here.
Anyone upgrading from FA 2.4.2 to this version will need to manually apply the database fixes to every company as detailed in this post.
The core translation strings for Arabic, Hindi and Tamil have been fully translated for FA 2.4.3 as per this commit.
Hindi and Tamil Install Wizard translations too are complete.
Should it not be part of the table then and use just 1 sql file?
@notrinos: You have an update.sql and a similar update2.sql file in your module with the former having an extra line:
ALTER TABLE `0_gl_trans` ADD `payslip_no` INT(11) NOT NULL DEFAULT 0;
What is the reasoning / usage?
Commissions off the books or amount set aside for possible contractual reasons / bullying the supplier!
A special tax called "On Hold" can be made and on every such purchase invoice it can be credited to a special "Payable Account" from where it can be paid out to the real beneficiary.
@itronics: Even when checking as opposed to activation ($check_only), shouldn't the error possibility be notified atleast in the logs / screen?
FA24extensions repo synched for auth_ldap. module.
Yes, you're right. The devs are now focussing on basic PHP 7.0 compatibility whilst ditching all pre PHP v5.3 class constructs.
These suggested workarounds will have to do for now
- recurrent editing of a single Sales Order and continued deliveries based on it by adding more line items
- Voiding and Re-creating a new Sales Order to match desired delivery bunching
- Export and Edit CSV, Void and Import CSV back the original transaction.
@joe states that the development to inculcate this feature has been postponed to a later minor release.
Edit php.ini file and remove the semicolon comment character preceding the extension for OpenSSL dll file in windows or the .so file in linux and restart the webserver.
The $stock_item is an element of $purchase_order->line_items. The $purchase_order object gets populated from the function read_po() defined in purchasing/includes/db/po_db.inc. The stock_master table provides only the units field in the sql in the function read_po_items it calls therefrom. Extend it by appending long_description and use it where you want.
Alter line 210 in purchasing/includes/db/po_db.php:
$sql = "SELECT poline.*, units
to be:
$sql = "SELECT poline.*, units, long_description
and then use it in the view_po.php file.
What extensions did you install?
Try them one by one alone and see which ones give the error.
Should it not be:
$sql .= " AND s.mb_flag='M' AND (
(m.qty > 0 AND m.type <> " . CUSTCREDIT . ") OR
(m.qty < 0 AND m.type = " . CUSTCREDIT . ")
)" ;
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.