1,001 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,002 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,003 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,004 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,005 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,006 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,007 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,008 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,009 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,010 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,011 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,012 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,013 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,014 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

1,015 Reply by joe

(23 replies, posted in Report Bugs here)

The report is in the file /reporting/rep308.php.

You see the algorithms here. Can you advise me how you would implement this report in detail. As I told I didn't create this report. So I would appreciate if you will help.

Joe

Go to forum: Report Bugs here

1,016 Reply by joe

(13 replies, posted in Report Bugs here)

Hello again Alaa,

In the file
/reporting/includes/class.graphics.inc

I have increased the font size with 2 pixels. And the space between works has been replaced by two spaces .

Was the font too big or is it ok? And was the space between words better now.

The php GD library doesn't support RTL languages, so we had to fix the strings to do so, but we could not change the graphics itself.

I guess this is the best we can do for now. Maybe there are some skilled developers that can help us in the future. This can always be worked on between releases. It doesn't require any database update.

Please replace the file /reporting/includes/class.graphics.inc with this one.

/Joe

Go to forum: Report Bugs here

1,017 Reply by joe

(13 replies, posted in Report Bugs here)

Hello Alaa,

I see you are using the Arabic language and this is good test for me.

A couple of years ago I helped another guy with Arabic language to get a suitable font to be used in the Graphics.
We found some, but I had to fix the leadings and other things with the fonts. I did that and we got some usable fonts.

In the config.php file, there is a variable called
    $UTF8_fontfile    = "FreeSans.ttf";
This fontfile doesn't work with the Arabic language. I have listed some utf8 fonts that can be used with the Arabic language.

Will you help and test them and give me a high five (1 - 5) character of the usability of the fonts?

Remember to spell the font names exactly. The smaller the file is the better, but it should be usable of course.

I will then incorporate one of the fonts in the default package, and change the variable in the config.default.php.

/Joe

Go to forum: Report Bugs here

1,018 Reply by joe

(23 replies, posted in Report Bugs here)

Hello again,

I didn't create this report. So I had to go into the source code.

As I can see, the rate is based on
1. Initial values is based on the rate on the beginning date.
2. Incoming values are based on the average rate during the period.
3. The same for outgoing values.
4. The end values are based on the average values for the whole period.

The guy who wrote this report are not reachable at present.

Can you use some of the other reports if this is not adequate.

Joe

Go to forum: Report Bugs here

1,019 Reply by joe

(12 replies, posted in Reporting)

Please use this link for customer balance.

https://sourceforge.net/p/frontaccounting/git/ci/unstable/tree/reporting/rep101.php

Abd this link for supplier balance

https://sourceforge.net/p/frontaccounting/git/ci/unstable/tree/reporting/rep201.php

Please be aware that these links are for 2.4

Joe

Go to forum: Reporting

1,020 Reply by joe

(23 replies, posted in Report Bugs here)

Ah, I see. 2.3. Will have a look into this.

Joe

Go to forum: Report Bugs here

1,021 Reply by joe

(23 replies, posted in Report Bugs here)

Are you referring to 2.3 or 2.4 or maybe both?

Joe

Go to forum: Report Bugs here

1,022 Reply by joe

(12 replies, posted in Reporting)

This has now been fixed in both the 2.3 stable repo as well as the 2.4 unstable repo.

In the allocated columns a correct - sign is shown for credit allocations and the summations are now also correctly done.

/Joe

Go to forum: Reporting

1,023 Reply by joe

(12 replies, posted in Reporting)

The allocated column should only be seen isolated for each record.
The mistake here is, that the column has been totalized. This should not have been done. Or it should show a minus sign for payments so the totalisation would be correctly presented.

Will fix this.

Joe

Go to forum: Reporting

1,024 Reply by joe

(2 replies, posted in Accounts Receivable)

No this is not a duplicate code. This is an outgoing and an ingoing stamp with writeoff reference. These 2 transactions is not seen in the stock movements transactions.

So you will not see anything in the stock movements. Only when looking into the database.

This has been changed slightly in 2.4.

Due to no sideeffects in 2.3 as it is now, we will not change anything here.

/Joe

Go to forum: Accounts Receivable

1,025 Reply by joe

(9 replies, posted in Announcements)

@infotechaccountant

Glad to hear that you are back. I guess that you was the father of a chart of account based on the IFRS standard.

We are about to release a final 2.3 release and shipping the new 2.4.0 release.

We are just fixing some bugs that have arisen during the release candidate period.

Great to do some creative work with you.

/Joe

Go to forum: Announcements