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
All strings in your screenshot are already there in the po file and hence in the mo file. The official repo provides ar_EG v2.4.1-3 but my repo provides ar_EG v2.4.3-1. This will need to be changed in the lang/installed_languages.inc file as well if manually updated.
See attachment for all strings properly translated.
The ar_EG language is part of the Transifex translations from where one can take the latest translations.
Check scope and visibility of the variables concerned at the place where they should be available. Also check the case sensitivity of the parameters passed in for comparison.
Making translation changes to the .po file and then compiling the official FA strings into a .mo file and replacing them in the FA language folder will make the changes visible possibly after a restart of the webserver.
Have a look at the compiled versions in the FA24extensions repo for ar_EG.
The only Arabic translation in FA for now is the Egyptian version - ar_EG.
Unless the original string is in the empty.po, it is not referred to in the FA codebase.
empty.po should not be ordinarily edited.
A copy of the empty.po is taken and translated for each language.
If you are making a new module, then keep the language files for it in it's codebase and not in the FA core.
Must you have to urlencode the link?
There is no "Current Assets" (Google Translated الأصول الحالية) string in the official language template empty.po.
Set the following variable in config.php:
$help_base_url = null;This will suppress the Help link on the top right menu.
@joe: are we using a stale session here?
These are for CSS Styling classes. If the function argument is a scalar, then it goes into an array and if an array it is passed on as is.
@kvvaradha: good show. Try to make for paying up balances using a link on the POS listing.
Also can convert woff2 files to ttf if needed and make it locally available using:
https://everythingfonts.com/woff2-to-ttf
@joe: is it to be added in the core?
There is no Array to String conversion here. The heading elements are in the array and are iterated through for display.
includes/ui/ui_view.inc
Do not choose to inventorise the items used for service business. There are separate service business Charts (for USA / AU) in the FA24extensions repo.
# Booking the expense in 2018
2018-12-31: Commissions Payable Account Cr $1000 (a Balance Sheet Account)
2018-12-31: Commissions Expenses A/c - for the Year 2018 for Specific Salesman: Dr. $1000 (a P&L Expense Account)
# Making the decision to pay the commission if other conditions of service are fulfilled
2019-03-01: Commissions Payable Account Dr $1000
2019-03-01: Salesman A/c - Commissions due to Specific Salesman: Cr $1000 (a Balance Sheet Account)
# Making the payment from the bank account to the beneficiary salesman
2019-03-15 (or 01): Salesman A/c - Amount paid to Specific Salesman: Dr $1000
2019-03-15 (or 01): Bank Account - Check issued to Specific Salesman: Cr $1000 (a Balance Sheet Bank Account)Agents are Salesmen in FA.
Properties are product items for sale or use recurring billing for leases.
Rudimentary contacts CRM is available in FA. Create each customer and edit it to add contacts. Also look at pre-paid transactions, advances and allocations on billing.
Make a different set of BOM for your choice if alternate items can be used.
@joe: should this be included? Never seen such a date format in practical use though!
Which version did you upgrade from?
FA 2.3.x had a normal non-pattern plain numbering system. You may have to mimic the old numbering system.
@elax: awaiting the updated version.
The following should do the job:
sed -e 's/AUTO_INCREMENT=[0-9]* //g' -i sql/en_US-demo.sql
sed -e 's/AUTO_INCREMENT=[0-9]* //g' -i sql/en_US-new.sqlLine 1950 needs to be PRIMARY KEY:
UNIQUE KEY `record_id` (`record_id`,`tag_id`)Check in en_US-new.sql also.
@joe: Please check if line 1369 in en-US-demo.sql is necessary - it is dated in 2012:
('1', '0', '001/2012'),There are many long char fields that should actually be varchar.
All AUTO_INCREMENT=XXX strings can be removed.
The event date is "as on" that date. In your case, though the payment was due, it was actually paid later (hence use Feb 28th) as against if payment was made on the event date and was forgotten to be booked, then it would be Nov 30th..
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.