Search options (Page 226 of 245)

@pierre whilst your change works, it is the non standard way and will get overwritten on updates. The preferred way is to make a copy of the lang/new_language_template/LC_MESSAGES/empty.po file and edit lines 10438-10439 to be:

msgid "INVOICE"
msgstr "TAX INVOICE"

and compile it with gettext as lang/en_SA/LC_MESSAGES/en_SA.mo and make an entry in the list of available languages and see that the locale is properly implemented. Refer Wiki.

GL Account Groups have a parent child relationship that can be used optionally.
Read the Wiki on Account Classes and Groups and Parent Ledgers.

The file purchasing/includes/po_class.inc has the class definition for the class po_line_details which refers to the default Quantity / Price - check the defaults in the table schema as well.

FA core is okay as it is. Make extensions for peculiar (country specific / rare legal) needs. The programming paradigm - KISS - is well protected here and that is why most non-programmers have found it easy to fathom the code. Extending the COA is inadvisable - porting from other accounting systems / fa versions, inadvertant switch flag type fields, backward compatibility issues pervade.

[RANT]:
Non Accountants and Non Programmers must be able manage FA without having to bother with Government - businesses need simple acounting info / capability for day to day operations. Most countries have begun to question the need for Statutory Audit - Self Audit is being encouraged. In the aftermath of Enron / Arthur Anderson / and other major corporations / audit firms / banks fudging accounts, Governments too will soon have automatic billing systems in their countries from which their VATs will be auto-calculated instead of summary submissions each month/quarter/year! There seems to be little trusted data on countries printing / creating money and providing huge windfalls to select individuals of choice - insurance, subsidies, rights.

{NICE]
If you do not sell in currencies (debt denominator) issued by governments - you do not need to pay tax! Corollary - no one pays any taxes for using FA! No one's paying Joe/Janusz any monies for coding and preserving the FA source! Yet FA users will look after you (tax free) when you visit their countries.....People like them are the real assets worth preserving.

Make one like Shipping at the bottom of the invoice or make a service item called, say, VAT Ajustments, with no tax and use it as a free form value.

Caveat: Must remember to do it each time one is needed.

Wow! That's a nice way of managing translation of labels and moving into form fields at the same time! For this to work, we need to have an "id" for each label and it's correspondig form field to be suffixed with a common number something like:

<p>
  <span id="formfieldlabel_001"><?php echo _"(&Name"); ?> :</span>
  <input type="text" size="40" id="forminputfield_001" name="name_field">
</p>

Only then can a generic js included in each form be able to generically do the trick.

In empty.po as well for relevent mods to be ported to other languages if used.

Better still, create a new table called, say, customer_images and link it on a 1 : N relationship with the debtors_master table and have a timestamp field in the new table as the date of last update and use the latest photo in it to display in the invoice form. Possibly have and show a signature field as well to have their scanned signatures for verification.

debtor_id INT AUTOINCREMENT NOT NULL PRIMARY KEY
lupdate DATETIME
Picture BLOB
PictureType enum ('Photo', 'Signature')
IsDeleted TINYINT DEFAULT 0

This way, when there is an FA Upgrade, your table will not be affected.

Place the custom reports in the company/#/reporting folder to survive upgrades and be specific to the company!

Where are we storing Customer's pictures?

You will need to clear any browser cache left over.

I only looked into one report listing the assets. Can you list the assets correctly as a report? This extension uses functions and triggers and hence your MySQL database user must have the necessary privileges.

List each issue and what file / url shows up on the browser for each issue and what menu click sequence brought up the issue. This will help replicate and resolve the issue.

Since the extensions are not in a repo for public to refine it over time and are just packed up into pkgs with magic glue it is a little difficult for the community to contribute and appears designed to help only coders.

I am planning a git repo for the extensions from where users can manually upload extensions outside of the magic web interface - any takers? Maintaining a repo over time is time consuming and requires great commitment - the folks at FA are already doing the best they can under the circumstances and it will not be fair to burden them any more.

Whilst Charts of Accounts, Languages and Themes get updated fast, extensions take longer to get updated when they do.