176

(11 replies, posted in Reporting)

I am out of office. Will check this when I am back on Thursday. In the mean time you could help me and tell where to change it.

Joe

I am running php 8.0.12 without any problems here. However changing this have no influence on other installations, so this has been fixed and pushed to repo.

/Joe

178

(7 replies, posted in Fixed Assets)

Fixed and committed to stable repo.

A fixed file can be downloaded here.

/Joe

I am investigating.

Joe

This has been fixed and committed to stable repo. Thanks for reporting this.

/Joe

Thank you guys for discussion this. It seems like a good fix. Will do a core fix.

Joe

Fixed and committed to stable repo. Thanks.

Joe

Hello again. I was quite tired when I did the analysis of the Bank Transfer. It turns out that only 2 files had to be fixed for this. This has now been done and committed to stable repo.

The fixed files, /gl/bank_transfer.php and /gl/includes/db/gl_db_banking.inc can be downloaded here and here.

Please download the files and replace on your server.

@advocaat.pollet
Please test this and report back.

/Joe

I have been analysing these bank transactions. It seems to be a lot of background transactions into the bank trans from both sales, purchasing, production and so on.
At first it looked easy to implement, but even if the bank_transfer table is prepared with dimensions, all the other traffic will be an update in many places.
I wil need a lot more time for doing this.
But please, in the meantime, use the Journal Entry for those transactions. It should work for you.

/Joe

I understand. The dimension should not be booked on the bank transaction but on the underlying gl balance account. There should be an option to select a dimension. Or 2 dimensions should there be 2.

In the mean time, I guess you can use the Journal Entry.

I will have a look at this later.

Joe

Fixed and committed to repo.

/Joe

Fixed and committed to stable repo. Thanks again.. The dimension sort fix is included.

Please note that there can be some minor differences from the Reports 102 and 202 and the dashboard aging.
This is due to that the foreign currency rates, if any, are calculated for the end date and in the dashboard we are using the rates from the records.

The new file can be downloaded here.

/Joe

Ok, will fix.

Joe

This has been fixed and committed to stable. Also some problems on the supplier side fixed. Thanks for reporting this.

There still might be some minor differences in the Aging due to currency exchanges and roundings.

A new and fixed dashboard.inc file can be downloaded here and replaced on your server.

/Joe

Hi, thanks for detecting this. Fixed and committed to stable.

You can download a file for replacement here.

/Joe

191

(3 replies, posted in Translations)

@unilla

Unfortunately I haven't got any email from you to my email. I sent you a mail about what email address to use.

Please send the package again to my email address (can be found in the Forum User List).
After that I will upload it to the repository.

/Joe

Hi, You might try to do a search in the forum to see some more explanations. Otherwise I will try to make a more detailed  instruction about how the fiscal year closing is functioning in FA. Thanks for the discussion.

Joe

There is an  error in your explanation.

Where did the 20k in 3400 come from? We haven't done the closure yet.
This account should first be filled by the closure routine.
Well it is ok to make the closure manually by balancing the accounts before the closure routine.
If the balance accounts are already balanced, then FA is not doing any bookings.

Joe

There are several ways of doing the Year end Closure. This is the way we are doing it.

At the year end, after closure all balance accounts should be in balance (assets - liabilities should be 0).

An example just before closure (a very simple illustration):

Balance accounts 
Assets           Liabilities 
  1000                   500 
                           X
----------------------------
 
P/L accounts 
Cost                  Income 
 800                    1300
   X
----------------------------

The annual year result (x) is debited the P/L accounts and credited the  Balance accounts (Retained Earnings).

Now all accounts are in balance.

And doing it this way we can use the P/L transactions for accumulated project P/L statements.

Joe

Fixed and committed to stable.

Joe

Hi FrontAccounting,

Congratulations! FrontAccounting has just been recognized with the following awards by SourceForge:

Community Leader
Community Choice
Open Source Excellence
SourceForge Favorite

These honors are awarded only to select projects that have reached significant milestones in terms of downloads and user engagement from the SourceForge community.

This is a big achievement, as your project has qualified for these awards out of over 500,000 open source projects on SourceForge. SourceForge sees nearly 30 million users per month looking for, and developing, open source software. These award badges will now appear on your project page, and the award assets can be found in your project admin section.

To recognize FrontAccounting’s achievement, we’ve awarded you with the aforementioned awards, which you can see  here.

Now that FrontAccounting is an official winner of the these awards, you have express permission to use the award badges wherever you’d like.

Feel free to proudly display the awards on your personal or organizational website, social media, or anywhere else you’d like.

Congrats again on winning and keep doing amazing work because SourceForge and our users appreciate it!

Thanks,

The SourceForge Team

Fixed and committed to stable. Thanks.

Joe

Fixed and committed to stable.

Thanks for finding this.

/Joe

Hello guys,

Thanks for reporting this issue.

I have asked Itronics to look into it and fix something.

Joe

Please upgrade to 2.4.11. These isues have been fixed in this release.

Joe