1,001 Reply by joe

(16 replies, posted in Reporting)

I think I will commit these files now. I have tested them without any problems.

/Joe

Go to forum: Reporting

1,002 Reply by joe

(1 replies, posted in Report Bugs here)

Please set the variable, $go_debug, in config.php to a value of 2 to trap some errors.

Joe

Go to forum: Report Bugs here

1,003 Reply by joe

(1 replies, posted in Report Bugs here)

Yes, you are right. The internal variable was not zeroed out before use in the Suppliers. Thanks for detecting this.

It will be committed asap to 2.4 stable repo.

In the meantime you can download the /includes/dashboard.inc and replace it in your setup.

/Joe

Go to forum: Report Bugs here

1,004 Reply by joe

(16 replies, posted in Reporting)

@nashirbadu

Did you get the time to test these 2 files. It would be nice to commit them asap.

/Joe

Go to forum: Reporting

1,005 Reply by joe

(16 replies, posted in Reporting)

The implemented algorithm is the fastest way of doing it. In C/C++ these check are internally converted to assembly instructions of one line.

Still, I am waiting for test result before committing it to 2.4. And as told, it is possible to use the files in 2.3.X also as the code are the same in both releases and files. Only you will have to replace the files yourself.

/Joe

Go to forum: Reporting

1,006 Reply by joe

(16 replies, posted in Reporting)

@apmuthu

No, the dates are correctly displayed in the excel report, and that is the main issue smile

And yes, it is possible to backport the files to 2.3.x, however we are no longer maintaining this version, so you have to do it yourself.

But just wait a while to hear if the files are ok for shipping!

/Joe

Go to forum: Reporting

1,007 Reply by joe

(9 replies, posted in Announcements)

@boxygen

You could look in the CHANGELOG.txt file. It will give an overview what has been changed and the files changed. You should go back and start at the 2.4 RC release and look upwards

For detailed changes, you can also look in the Git repo on Sourceforge.net, branch unstable.

Git repository

/Joe

Go to forum: Announcements

1,008 Reply by joe

(3 replies, posted in Reporting)

I guess you have missed something in the parameters list first in the report function.

/Joe

Go to forum: Reporting

1,009 Reply by joe

(16 replies, posted in Reporting)

@nashirbadu

I have included 2 files for testing of large files with more than 65535 rows. These files are only for testing, so DO NOT use them in production yet.

Will you download the files, rename Workbook.php1 to Workbook.php and replace the files in /reporting/includes folder.
Backup your original files during testing.

These files work with both small and large files with over 65530 rows. I have tested with 100000 rows without problem.
It will take some time with 100000 rows, about 2-3 minutes or more.
It works the way that when reaching the max row files, 65530, a new sheet is established and the rows roll over to this new sheet and so forth.

Please tell me if the files are ok.

In the file, excel_report.inc up at the top there is a define('MAX_ROW_SHEET', 65530);
You can, for testing, use a lower value, say 25,  and see the changing to a new sheet.

/Joe

Go to forum: Reporting

1,010 Reply by joe

(3 replies, posted in FA Modifications)

Hi,

These themes looks awesome. Very good indeed.

You could still use the default.css for common styles. Then you can call another style sheet inside the beginning of the body section. F.i. test for the rtl or arabic language and include the specific style sheet. And for other languages you simply include the other style sheet.

I am looking forward to see the final themes. Thanks.

Joe

Go to forum: FA Modifications

1,011 Topic by joe

(9 replies, posted in Announcements)

Announcement

This is a First FrontAccounting ERP 2.4.1 release.

This version provides a couple of new important features (in addition to all the
features merged from latest 2.3.25 and 2.3.26 releases), but main development effort was
focused on internal architecture changes and cleanups to make future FA development
easier.

At the time of release most of optional extension modules available from central
extensions repo has been also ported to 2.4 and should be mostly usable. Most Themes are
updated and many new Themes are available.

Please report any bugs/problems found via our
Mantis Bugtracker at http://mantis.frontaccounting.com.

Download instructions

In Sourceforge FrontAccounting (https:/sourceforge.net/projects/frontaccounting), select
Files -> FrontAccounting 2.4 ->2.4.1.

For Windows users select the zip file. For all other users select the tar.gz file.

Common

  • Fixed typos in installer translation files, fixed translations in dashboard procedures.

  • Fixed access control to tabbed dialogs in Items/Suppliers/Customers.

  • Fixed security check for last tab in tabbed_content.

  • Fixed broken html enities handling in longer TextWrap fields in reports.

  • Increased space for built in number columns etc. in reports.

  • Fixed problem with installing third party extension packages.

  • Bug submitting forms in FA 2.4.x when checkbox field not changed. Fixed

  • 0003658: Errors during reference line edition when no table prefix is used.

  • 0003733: Fixed php7 compatibility issue.

  • Improved entropy for report file urls.

  • Fixed problems with excel report generation.

  • Added a small Arabic font file, reporting/fonts/zarnormal.ttf, and improved the builtin DashBoard.

  • 0003789: Comments is cut off when actual invoice is printed. Maximized to 130 characters.

Sales

  • 0003816: Customer Credit Note (stand alone) does not restore inventory

  • Customer Balances Report | Allocated column not showing correctly. Fixed.

  • 0003780: Sales Invoice to partial delivery was improperly issued as final prepayment invoice.

  • Sales type bug in tax_included (persistent on). Fixed.

Purchasing

  • 0003585: 'Exclude from purchase' function not working in PO.

  • Dimension is missing in Supplier Invoice View GL Rows. Fixed a parameter bug in add_supp_invoice_gl_item.

  • Supplier Payment: by default bank account is selected to be the same as that used on the last payment for
    the supplier (if any, or default currency account otherwise).

  • 0003667: Fixed incomplete supplier payment link after entering supplier invoice.

  • 0003795: Fixed incorrect GL postings for cash purchase invoices.

  • Supplier Balances Report | Allocated column not showing correctly. Fixed.

tems and Inventory

  • Fixed A Bug in Item Sales Summary Report

  • Optimized Inventory Valuation Reports, 301 and 308.

Manufacturing

  • 0003761: Reorder email is not sent for items used work order (below reorder level). Fixed.

Fixed Assets

  • 0003862: Straight Line Depreciation value calculation is wrong

  • 0003863: Fixed Assets Valuation Report Includes inactive Items with Valuation

  • 0003864: Fixed Asset Sales GL Transactions were wrong. Fixed.

Bank and General Ledger

  • Fixed bug in bank account edition

  • Bloomberg Rate has changed their wrapper from span to div.

  • Fixed date checks in is_date_in_fiscalyears().

  • Minor bug in deleting fiscal years.

Go to forum: Announcements

1,012 Topic by joe

(1 replies, posted in Announcements)

Announcement

This is a final 2.3.26 bugfix release. The last release in the 2.3 series.

Common

  • Fixed typos in some installer translation files.

  • Fixed access control to tabbed pages in Items/Customers/Suppliers.

  • Fixed checkbox abnormalities in forms.

  • Improved entropy for report file urls.

  • Fixed problem with Excel report generation.

Sales

  • Cleanup in sales_invoice_db.inc (obsolete parameters in update_debtor_trans_allocation calls)

  • Customer Balances Report. Allocated column not showing correctly. Fixed.

  • Sales Type potential bug in tax_included (persistent on) on certains machines.

Purchasing

  • Dimension is missing in Supplier Invoice View, GL Rows.

  • Supplier Payment link after entering supplier invoice fixed.

  • Supplier Balances Report. Allocated column not showing correctly. Fixed.

Items and Inventory

  • Fixed a Bug in Item Sales Summary Report.

  • optimized Inventory Valuation Reports, 301 and 308.

Manufacturing

  • Reorder email is not sent to location for items used below reorder point.

Banking and General Ledger

  • Fixed bug in Bank Accounts edition.

  • Bloomberg Rate has changed their wrapper from span to div.

  • Minor bugs in deleting fiscal years.

Go to forum: Announcements

1,013 Reply by joe

(16 replies, posted in Reporting)

I found a PHP_XLSXWriter class here

https://github.com/mk-j/PHP_XLSXWriter

I will check if this class can be used. It handles 1048576 rows.

If it is ok, I will implement it during the 2.4 series. Maybe already the 2.4.2 release.

Joe

Go to forum: Reporting

1,014 Reply by joe

(16 replies, posted in Reporting)

There is a catch 22 effect in counting the lines. The report Title is printed before the eventual counting of the printed lines could be done.

I guess it is quite rare to have that many rows in a report  If we have, say 60 rows per page, it will result in over 800 pages!

I guess it is better to just wiki this as I said before and let some skilled programmer fix this during the 2.4 series.

/Joe

Go to forum: Reporting

1,015 Reply by joe

(13 replies, posted in Report Bugs here)

Yes, there was a bug. And it is fixed and committed to 2.4 unstable. You can download it here and replace in /includes/dashboard.inc.

/Joe

Go to forum: Report Bugs here

1,016 Reply by joe

(13 replies, posted in Report Bugs here)

I will have a look. Maybe we can test for that the menu is set.

Joe

Go to forum: Report Bugs here

1,017 Reply by joe

(16 replies, posted in Reporting)

I don't know how to do this. Maybe we could wiki it until someone can help. Will you apmuthu, please?

Go to forum: Reporting

1,018 Reply by joe

(13 replies, posted in Report Bugs here)

Hello,

I cannot reproduce this error. Can you tell me a little more detailed about it. I wonder if this is Theme based. Which theme are you using?

/Joe

Go to forum: Report Bugs here

1,019 Reply by joe

(1 replies, posted in Report Bugs here)

Yes, you are right. Fixed in unstable (2.4) repo. Thanks for detecting this. Also backported to 2.3 for safety.

/Joe

Go to forum: Report Bugs here

1,020 Reply by joe

(4 replies, posted in Reporting)

You could include the phone number in the address field on the customer/branch. F.i. separated with an enter character.

Joe

Go to forum: Reporting

1,021 Reply by joe

(23 replies, posted in Report Bugs here)

This has now been fixed and committed to 2.3 stable and 2.4 unstable repo.

Thanks for your participation, boxygen. You have made my day smile

/Joe

Go to forum: Report Bugs here

1,022 Reply by joe

(23 replies, posted in Report Bugs here)

Thanks boxygen.

Will look into this and optimize it. Forget my earlier files. Will remove them.

/Joe

Go to forum: Report Bugs here

1,023 Reply by joe

(23 replies, posted in Report Bugs here)

Hello boxygen,

There is a flag in config.php, called $use_costed_values that is set to 0 by default. In that case the standard cost set in the stock_master table (the last average standard cost) is used all over the period. This is only used in rep301.php

If this flag is set to 1, it will use the costed values all over the period, and the total will be the same as in the Costed Inventory Movements.

The reason for setting this variable $use_costed_values to 0 (default) is that this also can cope with manual changes in the standard costs.

I guess we use the same algorithms for Costed Values in both rep 301 and 308. Right?

/Joe

Go to forum: Report Bugs here

1,024 Reply by joe

(23 replies, posted in Report Bugs here)

Yes, I have been looking into this also tonight and think you are right. What you mean is to  use to the stock_moves standard_cost instead of calcutating from the purchase price, right?

I guess your idea is better. The question is if we should change rep301 too in accordance to this. What do you think?

I have changed the copyright to FrontAccounting LLC and inserted your name as the creator. I have also optimized the report.

Please rename the file to extension php.

Can I commit this report and also in 2.4?

/Joe

Go to forum: Report Bugs here

1,025 Reply by joe

(23 replies, posted in Report Bugs here)

The change in currency rates can change the value of the stock so that the value at the end is not the same as in the General Ledger.

To compensate for this you may enter a Journal Voucher.

This report gives you a more adequate value than the report on the average standard costs over time.

/Joe

Go to forum: Report Bugs here