Skip to forum content
FrontAccounting forum
It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 71 of 97)
Topics by itronics User defined search
Posts found: 1,751 to 1,775 of 2,419
Maybe you have invalid settings in Accountant role access setup. When you have 'Manual journal entries' set off in your role setup you cannot edit Journal Entries.. When you have 'GL postings view' set to on - you can view GL transactions. Thats all.
If you have upgraded your system from 2.1 version, the roles are automatically imported from old settings, but as the 2.1 setup was not consistent enough, the new roles need some fine tuning in Access Setup page to be more consistent.
Janusz
What do you name as 'remittance' ? Is this simply a statement how the payments/credits were allocated to supplier invoices?
Janusz
'GL postings view' gives only read access to GL postings and GL inquires. The only directly editable GL transactions in FA are those entered via Journal Entry, and there is another security area defined for it. GL postings generated by other type of transactions (invoice, GRN etc) can be changed only by edition of related transaction. Any transaction can be deleted via Void Transaction page, but this is special function with its own security area setting.
Current security scheme basically allows choosing from three options: none, read or full access to any type of transaction.
Sometimes more fine grained scheme would be useful (e.g. differentiate entry/edit/delete access), but this is rather rare case, and the price would be both bigger code and difficult to maintain, much longer list of access role options.
Janusz
When you upgrade any minor release you can safely copy files, preserving installed modules/themes. But when new major release (next is 2.3) arrives your old extensions can be not compatible after changes in core code, so no guarantee in this case.
Janusz
Ubuntu seems to me a little weird not allowing root logins, but surely they have some idea beside this. Thank you for clear instructions how to make it right.
Janusz
Interesting. There is no expression which could cause this error in line 6193 tcpdf.php in current FA 2.2.2 nor unstable CVS code. What FA version you have?
Janusz
Yes, I think so. No special upgrade process is needed.
Janusz.
There was a couple of bug fixes since 2.2.1., so the best you can do (if you have plain, not customized FA installation) is to download 2.2.2 tarball from sf.net and unpack in your FA directory. The exact file related to this issue was most likely /includes/ui/allocation_cart.inc, and maybe /sales/includes/cart_class.inc (see stable branch CVS Changelog and/or mantis reports)
Janusz
Hello Tom,
You can use sucurity area codes starting from 100 for extension module.They are anyway rewritten during installing extension, and you will never use SA numeric codes directly, only string security areas identifiers like 'SA_OSCIMPORT'.
All this is explained in FrontAccounting access control system basics article. If some info is missing feel free to update the documentation.
Janusz
Please update your FA sources to 2.2.2 version to fix the problem.
Janusz
I guess you are using FA version 2.2.1 or earlier. Please update your FA instaation to latest (2.2.2) version, and all should work right. No changes in database or reinstallation is needed.
Janusz
As for now there is no universal interface to cooperate with third-party software, but we have several FA extension modules for importing CSV data, mainly for GL postings. They can serve as reference when implementing extension module for manufacturing data import.
The idea of 'watchdog' directory seems to be interesting, but to be used some CSV importing have to be implemented anyway.
What operations would you like to have available as a part of API for conecting with third party MRP software?
Janusz
If you are using linux you have to install indonesian locales to enable indonesian translation. You can check it with command: locale -A.
Janusz
I think you can achieve this scheme creating members as customers, creating customer groups (for various member kinds) and then defining recurrent invoices/sales orders with 1 year recurrency period for every group.
Janusz
Well, good that it works for you now. But what write permissions setting (AFAIK non effective at all as for now ) have to do with session? Who knows...
Janusz
Give us a note when you will check session configuration and you will find something strange.
Janusz
Seems something is wrong with session variables. Clear your cookies in browser and try login again.
Janusz
Well, I think it was implemented as simplest lazy solution . There is a couple of another ways applicable here like restricting price changes when anything on order was delivered, or using per line item restrictions. I think current way is equally safe, but we can consider another choices.
Janusz
Set $go_debug=1 in config.php file in main directory and eventually switch on error logging (see config.php again). This enables additional diagnostics which should result with error messages instead of blank page when something goes wrong.
Janusz
As far as I understand you can login, menu screen is displayed and every click on menu options moves you to the login screen again? If this is the case seems there is some problem with session handling. Cookie based session have to be also enabled on server side - please look into session related php.ini settings, especially session.use_cookies.
More here: http://pl.php.net/manual/en/session.configuration.php
Janusz
Seems you have cookies disabled in your browser?
Janusz
ebayram wrote:I need my codes and suppliers codes together, because supplier need their codes for prepare my orders. Also supplier need my codes because they prepare barcodes for my item one by one.
You can put both codes together in Purchasing Pricing option under Items and Inventory menu.
ebayram wrote:I cannot put supplier codes item description because i have 5 suppliers for one item. Is there any way to fix this problem, like file change.
But you can. You can entry different description for every supplier at this screen. So what is the problem (beside need for entry data for every supplier here) ?
You can of course try to change report rep209.php to be more suitable for you.
Janusz
Yes, it do. Please look into our 2.2.1 demo. Here you can experiment with purchasing data and how it is displayed on reports. E.g. look into first PO - it use supplier's uom and item name for first item line. This is how Joe has explained.
Janusz
If you delete purchasing data records for given supplier your internal codes and names will be printed on PO.
Another solution is to add your codes together with any description in purchasing data.
Janusz
Please report bugs on mantis. This is primary place for bug reports, and bugs reported on forum tend to be forget.
Janusz
Posts found: 1,751 to 1,775 of 2,419