Search options (Page 20 of 97)

The Report Generator module code has been adopted as FA extension long time ago despite it contains many design issues. We have provided it anyway, to give some base for better solution development to any interested third party programmers.

Keep in mind, that in current state the module should never (it means NEVER) be used on FrontAccounting installations working in not fully trusted environment.

Treat this warning seriously: due to still existing vulnerabilities this extension should not be installed on any servers accessed from external net. This warning has been included in extension package info, but better safe than sorry, so I have added the info to wiki too.

Janusz

As you can see this issue appears occasionally on some unidentified configurations, while all works right for all other users. We cannot reproduce this problem on our testing configurations, so you are probably on your own.

No.

This will be made in 2.4 release.
Janusz

Thanks. The path will almost always differ from the real path. Those are only handy comments for translators, to recognise context of the translated text.
Janusz

I don't think so. Branch setup contains much more parameters than those visible on new Customer screen in auto mode. Anybody who want to have full control over branch settings during customer/branch creation will have the switch set to off.  This is how the application was used over the years from the begining.

Janusz

The installed_extensions.php file is properly created during installation. Nevertheless I have found small bug in system tests (main FA folder was not tested properly whether it is writable or not). Fixed for next release.
Janusz

I have fixed a couple of issues in Requsitions module and the package in repository has been updated. Now all the functionality implemented by Dennis Gichangi should work right, also some small changes were made in the code which should result in a little better user experience.

Unfortunately there was also installation bug found in core FA, which results in non intialized database after installation. The bug was already fixed in Hg repository, but the new minor FA version is not planned until next year. Therefore to make use of the new module version  you have to do following steps:
. make backup of your company database
. uninstall requisition module in Create/Install Extension page
. install it again from the repo (on the same page)
. read module description - you will find important warnings here
. open your company database in phpmyadmin and import /modules/requisitions/sql/update.sql file.

Now the requisition module should be usable. Keep in mind there is a little non-standard interface implemented by author.
Entering requisition is not complete until you select Details link, enter a couple of requisition lines and select Complete link finally.

Janusz

I guess you have attached not execactly what you wanted to. The zip file contains no changes beside report title (not taking into account changed original author's info).
Janusz

I'm not sure what are you talking about ? The flush_file is potentially damaging function, which delete entirely the selected folder and all its subfolders recursively. This is not part of any library, just the FA function declared in current_user.inc file
Janusz

Please send the fixed files back to contributions mailbox with terse change description, then we will pack it and make them availbale from repo. If you wish to use the changed files only locally, you do not need packaging at all.
Janusz

Processmaker is not free/open source software, nor it is especially popular, so I guess you will have to find a developer and pay to make the integration for you.

Janusz