Search options (Page 175 of 246)

First of all the UK Chart of Accounts is broken if taken from the official pkg repo. After installing it from there, just update the en_GB-general.sql file from my GitHub Repo. Just upload the said sql file overwriting the one in the sql folder and then create your UK company. Let your default company be created with the en_US-new.sql and your actual company be created with the new UK sql file.

When entering your items, just choose Tax Exempt for now. When you get to qualify for VAT, then change the settings to Tax in the items. All the old invoices will remain in their Non Tax state.

Look at what broke in modifying the report - use a diff tool like say WinMerge - mostly syntax errors, missing variables/objects, missing arguments, scope, etc. Check the apache error logs and the FA error logs as well.

There are quite a few placed where D is hard coded in the core and in the extension files.

A brief history of mb_flag changes:

2014-09-12: Removed redundant mb_flag 'A'.
2009-05-18: Added mb_flag 'M' in demand checks
2009-05-17: Removed obsolete 'K' mb_flag checks.

Extensions having mb_flag and referencing 'D' or 'S':

Extensions/api/sync_db.inc : Lines 393, 418, 1069, 1109, 1152 => D
Extensions/import_items/import_items.php : Line 246 => S
Extensions/import_items/readme.txt : Line 111, 163 => S

Core files having mb_flag and referencing 'D' or 'S':

includes/data_checks.inc : Line 333 => D
includes/manufacturing.inc : Line 27 => D
includes/db/inventory_db.inc : Line 114 => D
includes/ui/ui_lists.inc : Lines 915, 924 => D
manufacturing/work_order_add_finished.php : Line 139 => D
reporting/rep301.php : Line 113 => D
reporting/rep307.php : Line 40 => D
reporting/rep308.php : Line 70 => D

@joe: Shall we change the core - what of the community and existing users data?

If only the 32% display on the label side is erroneous, it can be just clubbed together into a string like "All VAT" if the sum of the taxes is correctly displayed on the right hand side in the summary.

Just check to see the number of database queries you need to display the average page. Placing frequently used menus that do not change often into the database can cause problems when the db hangs or gets bogged down with too many requests - practically on every page refresh or re-construct.

The very appeal of the standard FA menus is it's familiarity and ability to see all links on one page without clicking on any dropdown menus.

Check if your choice of default theme allows you to use FA in an intranet not connected to the internet.

Where in the wiki should we indicate this fact. Should a translatable string be used in FA 2.4?

You can leverage the Non Field DB Data functionality for this purpose but will have to manually update the old price in the item's long_description field with something like "OldPrice#31.23" as part of it in a space separated manner.

Alternatively, you can have a new price history table and make an extension for it in FA.

Extending the core FA tables will render upgrades untenable and make it only manually upgradeable.

Replace 4 with 3 or 2 in the first and last lines of Lines 149 to 152 in reporting/includes/header2.inc:

        $this->fontSize -= 4;
        $this->Text($ccol, $Addr1['title'], $icol);
        $this->Text($mcol, $Addr2['title']);
        $this->fontSize += 4;

Do you want to cocatenate the line memo with the transaction memo? Would that not exceed the space for line items in reports?

The proper way would be to correct the offending line in the dashboard theme / extension where the $result originated - not to call the function if it was false!