Hello,
The 2 core COAs have now been redesigned a bit and are now syncronized. Only that the demo variant has the demo data..
I have tested both of them, and it seems to work fine.
Committed to repo.
/Joe
It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by joe
Hello,
The 2 core COAs have now been redesigned a bit and are now syncronized. Only that the demo variant has the demo data..
I have tested both of them, and it seems to work fine.
Committed to repo.
/Joe
No, the dashboard tables should not be there.
Well if users make a backup they will see the '#' as a comment specifier.
Will make a rerun later.
Joe
Hello again.
Only en_US-demo.sql needed update of the 2 core. It was done by moving 2017 to 2018 (search and replace). Then creating a new year 2019-01-01 to 2019-12-31. And setting the Company to this year. Then a couple of transactions were made.
This is all we can do. Remember things are very close mingled in the database. But this is good enough.
The en_US-new.sql was ok as is. The fiscal year was set to 2018-01-01 to 2018-12-31. I think this is ok, for when you start a new company you will often make an opening balance on the end of 2018. And then create whatever new fiscal year you need.
All the other COAs from the repo only needs a new fiscal year, I guess.
But Janusz will do some adjustments to the 2 core COA's due to SQL security injections. And of course also to the repo COAs.
The new en_US-demo.sql has been committed to repo. Can be downloaded here if needed.
/Joe
I will fix it manually this time for the two charts we have in core, but if you are keen fixing it your way, you are welcome to try.
We do have a lot of charts that need update.
Joe
Yes, it is a matter of search and replace.
Joe
This has been fixed and committed to repo. A fixed file can be downloaded here.
/Joe
I don't know. Will have a look later.
Joe
You can also print the supplier Invoice View. The print option is to the left of the close link.
Joe
@apmuthu. I don't know yet.
You should address this question to @notrinos.
I don't have the complete picture yet.
Joe
This is fixed. My fault. Sorry. Thanks @notrinos. Committed to stable.
/Joe
There is no meaning in printing a Suppliers Invoice. You have got one from him, either hardcopy or softcopy. You can attach this document to the supplier Invoice record.
Best regards
Joe
Well, I see that this has never been updated for release 2.4. This must be a mistake, and I will fix this. But you can download the file included here. Unpack it and replace the files in /themes/elegant folder.
And you should be going.
Thank you for your nice words.
/Joe
Of course, I will have a look.
/Joe
Committed and new file here.
Joe
Ok I will roll it back in a while.
Joe
Yes, they should. These have only a few parameters. The rest is default.
/Joe
I think we will make a poll when @notrinos has presented his new theme.
Simply let the audience decide which should be candidates. We usually have 3 themes in the core, but the other can be set as extensions. I guess there are several old themes that can be taken away from the extensions.
The best one will be the default theme. Democratic, right?
/Joe
@kvvaradha.
Yes it looKs better. Still I think the icons is too dominating. Mayby it is the Material design. Of course it is a matter of taste .
Joe
This is fixed and committed to repo.
/Joe
Ok, I understand. I think I will just use your get_gl_transactions for now. To fix the timeout problem.
And put the extra null parameter in gl_account_inquiry.php.
We could then easily get more fix here later. Thanks for helping.
Joe
@braathwaate
Or do you want 2 extra input filters on the gl inquiry, person-type and person combo. In that case we should probably use som ajax-update when selecting.
/Joe
@braathwaate
Any change to parameters in the file gl_account_inquiry.php that calls get_gl_transactions?
This is the only file that are different in the new parameter list.
/Joe
@apmuthu or @Braathwaate,
Where can I find the specific variant of get_transactions?
/joe
Hello @kvvaradha.
I have choosen another approach. In login.php all the initial stuff are processed here. Then the theme login.inc file is called if such a file exists, mostly for the design part, and the final stuff is again processed in login.php. This approach will eleminate the risk of forgetting stuff in the theme login.
If no login.inc file exists a default login is used.
The problem is the catch 22 part. We don't know the user theme before the login is effective. But we will find a solution to this. Ii am working on that.
Then reset of the password file is almost a copy of the login.php file. It could be processed the same way. I will see if we can merge the reset password file and the login.php file.
Joe
FrontAccounting forum → Posts by joe
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.