Search options (Page 15 of 247)

Post Release Fixes attached.

CHANGELOG

Github Master (Bleeding Edge) Download Link

These fixes can be applied to (overwrite) the release version to be fully functional.

The following when run on your file may suffice to change backslashes to forward slashes:

cat empty_bs.po |  tr '\\' '\/' > empty_fs.po

Further "if" can be introduced to restrict it to lines that start with "#".

Attached is the empty.po for the core. Please verify where "\\n" string is there as they are from js files which have not been parsed but taken from the pot files.

Inadvertently, the install/lang strings got injected into the core empty.po file during the release of 2.4.13.

1 string is changed between the older core and the current one:
" overdue Purchase Invoices"
is now
" unpaid Purchase Invoices"

It is better to re-create the core empty.po file and make for a re-release.

There is really no new strings in the empty.po other than the changed string listed above.

Here is a quick 'n dirty script to extract all gettext strings in FA:

find /var/www/frontac/ \( -name "*.php" -o -name "*.inc" \) ! -path "./tmp/*" | \
sort -bdf | \
xargs xgettext \
--default-domain=myapp \
--output=myapp.pot \
--language=PHP \
--indent \
--no-wrap \
--sort-output \
--omit-header

The --omit-header can be omitted along with the last back slash for comparison purposes like in WinMerge.

As these strings will be sorted, it will be easy to compare *.po files between versions. Comments can be stripped with:

grep ^'^#' sourcefile.txt > output.txt

Can this make it to the core or a flag for it company wide?

The core FA code has certainly been modified as otherwise you will not be able redirect standard transactions to your table intervention. When FA code changes affecting these tables scripts, you will have to keep on updating your code changes into these scripts as well. Rather than have such a nightmare, it is best to elegantly make it a part of FA by just having a transaction status field and change the code once and for all in the core.

The Approval system is good and needs to be incorporated into the core. How many tables does it entail? One for Approval Roles and another for the approval / rejection status of the transactions unless the core FA tables are altered to add in the new status fields.

stk_code is a valid field

It is a field in the 0_sales_order_details table

This version now has new translatable strings:

Enter direct &Invoice

"Debits" instead of "Charges" only in reporting/rep101.php:137 and reporting/includes/doctext.inc:247 but remains "Charges" in reporting/rep201.php:115

"Invoice %s from %s" instead of "Invoice %d from %s"

Invoiced so far:

New Payments

Existing links work okay and direct linking too works.

@joe?

First get FA 2.3.22 (2014-09-29) to FA 2.3.26  (2017-05-23) the last in that series.

Then get it to FA 2.4 or directly to FA 2.4.11+.

All difference files are in the Announcements sticky topics.

Attached is the v2.3.22 to 2.3.26 changed files.