Search options (Page 114 of 245)

The file I posted is the same as the one in the zip which had other changed files as well.

It appears you may have some browser cache issue - what browser and version did you now text on? As InnoDB tables are being used, some some tables having an auto_increment field will need to reset their auto_increment values after an insert depending on your version of MySQL (?) and PHP (?).

Credits (and brickbats too) for the latest code for this module goes to @braathwaate on Github.

Looks like you will have to overwrite all your import_transaction module files. Take it from the attachment.

You may not have applied the correct version of import_transactions/import_transactions.php.  Lines 63 to 68 of the said file should be:

all_delete($yes = false);
$js = "";
if ($SysPrefs->use_popup_windows) 
    $js .= get_js_open_window(800, 500);
$help_context = "Import General Journals  / Deposits / Payments / Bank Statements / Sales Orders / Sales Invoices  <a href='spreadsheet_headers.html'>Help: Formats</a>";
page(_($help_context), false, false, "", $js);

All modules must be unzipped into the <FA_WebRoot>/modules/ folder to be usable. When installed and activated, they must find an entry in the relevant installed_extensions.php files.

Clear the browser cache and try anew.

FrontAccounting is a copyright of this project's developers. It is advisable to register a domain that represents ecommerce, online accounting, etc and state that you support and host FrontAccounting. That way you will be able to represent a host of applications and integrate them together as well, say, like a Point of Sale (Open Source POS), osCommerce, etc. Your team can also fork the FA project on GitHub and then either send back pull requests or take a completely different development path. FrontAccounting itself is an early fork of the WebERP project.

There is ofcourse nothing to officially prevent you from registering a domain like frontaccounting.ph but it would be nice if you redirect users seamlessly back to frontaccounting.com - that way the Phillipino FA community will remain integrated with their world wide counterparts. You may also choose to provide a localised translation of frontaccounting.com in your frontaccounting.ph domain to enable easy adoption of FA in your country. Cybersquatters too will soon try to register such domains in their country extensions and mislead new users.

This is not available in standard FA. Edit location drop down box in sales/sales_order_entry.php file for hard-coded usage.

If you want to turn off this warning, then in your config.php file, set the variable:

    $check_price_charged_vs_order_price = false;

The function over_charge_allowance() (in the file includes/prefs/sysprefs.inc) returns the margin (default = 10%) using the per company variable po_over_charge in the sys_prefs table.

The sql in the function getTaxTransactions in rep709.php is responsible for the line entries under investigation. Try to debug the actual sql string and it's output on execution in the database and see what went wrong.

Are you using a customised Tax Report - reporting/rep709.php ?
The standard one used in FA 2.4.1+ is attached.

The Exempt line is there to show that there has been some inputs that bear no tax.

If you want the old behaviour, then make the line 106 in the said report file:

    $taxes[0] = array('in'=>0, 'out'=>0, 'taxin'=>0, 'taxout'=>0);

to revert to:

    $taxes = array();

Wonder what it would affect.

@joe: ?

Those using FA 2.4.1+ please provide feedback on the latest import_transactions module in the unofficial GitHub FA 2.4 extensions  repo - this is a "fixed" version of the pkg in the official repo. This contains the mods / fixes by @braathwaate cleaned up for whitespace and spaced indentations.

The config.php file's English wiki page has been updated for FA 2.4.x and the old one for FA 2.3.x archived. The various language translators of the wiki are advised to update them as well.

Which version of FA are you using - v2.3.x or v2.4.x?
What is your OS platform / MySQL / PHP for the server and version?
Which client browser and version are you using?

The said message emanates from Line 273 of purchasing/supplier_invoice.php.
If you want to brute force it then comment out the lines 266-279 in it.
Check the settings in your sys_prefs table / config settings for the real fix.