In the meanwhile, run your own PMWiki with the level 1 pages in the attachment. Beware of Latin1, Unicode and other glitches.

Yes, the source renders okay.
Try: https://frontaccounting.com/fawiki/inde … ion=source.

It was the smart quotes and dashes and ampersands, although where they came from or why they have come into play I don't know.

All links lead to logout after logging in.

@joe: any updates? Was the server changed?

Any results?

Manually deleting such Journal entries should not cause imbalance..... but you will be blind to it later!

1,705

(11 replies, posted in Reporting)

Voucher numbering is a delicate issue needing utmost care as to whether they are primary keys or have other fields as primary keys and what linkages exist with similar numbered ones during the change process.

The WIKI has been hacked / broken - most likely the latter.

The links on the left till and including Working with FA logout the user displaying a blank page.
Looks like some namespaces issue.

Should there be any change in the 0_refs table as well?
Also the wo_requirements costs are listed as 0 for WO # 1.

The type field in the gl_trans table too needs to be set to 29:

UPDATE 0_gl_trans SET `type`='29' WHERE `counter`='13'; 
UPDATE 0_gl_trans SET `type`='29' WHERE `counter`='14'; 
UPDATE 0_gl_trans SET `type`='29' WHERE `counter`='15'; 

and lines 908-910 in en_US-demo.sql should be:

('13', '29', '1', '2017-05-05', '1510', '1 * iPad Air 2 16GB', '-400', '0', '0', NULL, NULL),
('14', '29', '1', '2017-05-05', '1510', '1 * iPhone 6 64GB', '-300', '0', '0', NULL, NULL),
('15', '29', '1', '2017-05-05', '1510', '1 * iPhone Cover Case', '-20', '0', '0', NULL, NULL),

At the moment, any zero amount item (like Support in the WO #0) will be treated as Work in Progress and have it's amount set to total value of all inputs and later contra-ed on finished product receival. See Anatomy SQL in previous post. Wonder what happens when there are more than one zero cost input items!

Even after the last commit, there is however no change in the WO_Production Costs for WO #1 shown in the attachment in the Post #2 in this thread. Everything still remains in the finished product receival part of the view instead of the input items being part of issues.

The complete anatomy of an Assembly Work Order is listed here and attached as well.


The time of entry is available only in the audit_trail table.
The amounts are not rounded off in the stock_moves and wo_requirements tables.
The amounts are rounded off in the gl_trans and stock_master tables.
The stock_master.material_cost field is computed as the weighted average of existing stock quantity and value and those of the currently produced item (or any other chosen programmed means).

In the same vein, shouldn't the other entries be type=29 (ST_MANURECEIVE) instead of the current type=26?

001/2017 can be of different types.
In this case it is type=26, a WorkOrder.
Check to see if it has been voided - No, it is not.

Attached is the default Demo data of Work Order and a new work order's entries for comparison.

@joe: does the Demo Data need any change?

1,711

(5 replies, posted in Setup)

Here are some FrontAccounting YouTube videos - they do not directly refer to taxes but you can search therefrom.

https://www.youtube.com/watch?v=V3JAinekq5A
https://www.youtube.com/watch?v=GpriCbSqEEk
https://www.youtube.com/watch?v=AVnG8lj3oS0
https://www.youtube.com/watch?v=pwSz2H0otnA

1,712

(1 replies, posted in Reporting)

The file reporting/includes/doctext.inc has 9 instances of the string "Your VAT no". They are assigned as translated keys in the array $aux_info and used in reporting/includes/header2.inc in lines 167-175:

        foreach($aux_info as $info_header => $info_content)
        {

            $this->row = $iline2 - $this->lineHeight - 1;
            $this->TextWrap($col, $this->row, $width, $info_header, 'C');
            $this->row = $iline3 - $this->lineHeight - 1;
            $this->TextWrap($col, $this->row, $width, $info_content, 'C');
            $col += $width;
        }

You can selectively delete the offending "Your VAT no" element or skip over it in the loop above.

Map the JSON / XML output to the FrontAccounting table fields / computed fields in English using the Standard US chart of accounts.

1,714

(1 replies, posted in Installation)

Looks like you have a symlink to the public folder inside the public folder itself that gets called recursively.
Your cPanel's specific version parameters for FA installation may have some relative path somewhere. Contact your hosting provider.

The Error 500 is that there is some other process using the required port.

1,716

(10 replies, posted in Setup)

The lack of edit for transaction reference prefix is that there may be other transactions using it. Use with care manually.

1,717

(5 replies, posted in Setup)

Refer the Tax setup pages in the wiki.

1,718

(6 replies, posted in Modules Add-on's)

Where is it hosted?

1,719

(6 replies, posted in Modules Add-on's)

Will it not be better to include the SlimAPI files and do away with composer so as to make it self-contained?

1,720

(1 replies, posted in Fixed Assets)

Read the Fixed Assets Wiki.

Fixed Asset Categories.

1,721

(6 replies, posted in Modules Add-on's)

Do let us know if you intend to make it free of composer.

1,722

(4 replies, posted in Announcements)

For those intending to upgrade from FA v2.4.2 directly to FA v2.4.4, the changed files zip is attached herewith. The FA 2.4.4 post release fixes will have to be added on separately afterwards from previous post. Take note of DB changes in the charts of accounts and those that pertain to fixes in the addon modules apart from the new entries in the config.inc.php (refer config.default.php changes) / sys_prefs table entries.

Check if the error still occurs in a FA 2.4.4+ (GitMaster) install.

1,724

(9 replies, posted in Announcements)

Place the files from the 2.4.2 to 2.4.3 changed files in a folder. Now overwrite them with the files from the 2.4.3 to 2.4.4 changed files and then take the files from the Post 2.4.4 release changed file set and overwrite as well. Now you will have the complete set of files that are needed to bring your FA v2,4,2 up-to-date with Git Master codebase that you can use to overwrite your FA 2.4.2 install with. Any changes in the standard chart sqls can be ported to each of your companies. Mostly records in the sys_prefs table.

Refer this post.

Do not forget to consider that the document number will be checked only in the core tables and not in the extra tables. You may land up accumulating "yet to be approved" entries in the new table - possibly all with the same document number!