Search options (Page 76 of 246)

The commit has not appeared as yet in the GitHub repo.

@Rmendez confirms that this commit solves his issue.

The screenshot is self-explanatory. The concerned file is sales/sales_order_entry.php. Whilst the max length of the form field allows 35 characters, the displayed form field is restricted to 10 characters.

In the DB tables, the field sizes are all normally VARCHAR:

reflines.pattern - 35
refs.reference - 100
sales_orders.reference - 100
debtor_trans.reference - 60
purch_orders.reference - TINYTEXT
supp_trans.reference - TINYTEXT
supp_trans.supp_reference - 60
stock_moves.reference - CHAR 40
workorders.wo_ref - 60
wo_manufacture.reference - 100
wo_issues.reference - 100
suppliers_supp_ref - 30 (***less than general form field max of 35***)
cust_branch.branch_ref - 30 (***less than general form field max of 35***)
journal.reference - 60
grn_batch.reference - 60
dimensions.reference - 60
bank_trans.ref - 40

@joe: are there an rationalisations needed amongst these fields and field types.

There are no BEGIN ... COMMIT raw blocks in FA core codebase and possibly not even in any official Extension.

However, local SQL wrapper functions begin_transaction() and commit_transaction() exist and have such a check for non negative values as defined in includes/db/sql_functions.inc.

@joe: Committed

vTigerCRM community edition is free.

vTigerCRM is one way to go where FA's account codes can be inserted into it and the CRM's member id can be inserted into  the chart_master.account_code2 field.

You can change it to whatever you want but remember that easily guessable filenames can be avoided using good entropy as obtains here. Rename it on file download to suit your needs. Consider how the files would stack up when mixed up with similar reports of different companies and / or different fiscal years in the same folder.

The filename for storage is computed in lines 971-974 in reporting/includes/pdf_report.inc:

            // do not use standard filenames or your sensitive company data 
            // are world readable
            $fname = $dir.'/'.random_id().'.pdf';
            $this->Output($fname, 'F');

Mail attachments and inline display will bear the file name provided in the 2nd parameter in the "new FrontReport" class instance's constructor as seen in line 73 of the same file:

    function __construct($title, $filename, $size = 'A4', $fontsize = 9, $orientation = 'P', $margins = NULL, $excelColWidthFactor = NULL)

and instantiated in each repXXX.php file.

The Payment Allocation generates a transaction entry for it in each instance. Hence the Balance Sheet AR/AP part of the Trial balance will only change and not the P&L or it's part of the Trial Balance.

The Rep702 - List of Journal Entries is in report format and is already arranged by Date, but several vouchers are in each page to conserve space.

The "Banking and General Ledger/Journal Inquiry" is a screen display and you can print them one by one.

If you want to print the latter as one per page then just copy the URLs to a file and run a batch file on them and then print them all in one go.

I too am uncertain of what would happen if such data is exposed in the URL and whether it can be used to hijack the session even though my last attachment works. This is so even if the backwards compatibility is not even there and for PHP 5.6+ itself.

Now that these fixes have been rolled back, those who still want this functionality of using the back button on the browser instead of the back link on the FA page and then returning to the page to where they left off, can partake of the consolidated fixes attached herein.

Await @itronics words of wisdom....

There are 2 audit tables.

The audit_trail table is for recording all transaction references where certain NULL fields will indicate what was superceded. It is also used when closing a fiscal year and purging it.

The sql_trail table is to record all sql accesses as set in the debug parameters in the config.php file.

Thanks for the feedback on how you solved your issue. Will make for a good reference for yourself and for all users as well.

This project is maintained by @joe with valuable coding by @itronics, both sys admins of the FA project. They certainly deserve the donations to keep this project going. Your mite will join others in sustaining this project. Thanks once again.