itronics wrote:

There is no right place here to explain all the nuances  of the license, so in short words:
. FrontAccounting can be sold providing all GPL license requirements are fullfiled;
. The result product have to be distributed on GPL license too;
. If the result product is distributed, it should be done in source form, so no code obfuscation is allowed;
. We do not give permissions to remove any licensing info from application
files; Any changes done in sources should be clearly stated as made by modification author;
. We retain rights to make license changes in future;

We do not agree on shameless usurpation of FrontAccounting authors work anyway.
FrontAccounting LLC

Thanks very much for your reply and clarification, i will "PM" you the details of the issue, as well as the outcome which i am glad to say has been resolved amicably.

Hi Guys, this is a question of legality of a person re-branding front accounting, then selling it as their own product (either as a standalone product or SaaS).

I've read through the GPL3 license here, however there is no real answer on whether this is allowed to remove logos and change the product name or not (but there is mention to comment all modifications, and that you are allowed to sell for any price etc):

http://www.gnu.org/licenses/gpl-3.0.html

The reason for this question, is that i have been contacted by a company who has blatantly rebranded FA, and are attempting to sell this to end users....and i dont think its right.. so i am conducting research before approaching them about it.

any help and advice on this issue would be much appreciated... thanks!

3

(12 replies, posted in Installation)

Hi,

we're having similar issues as well.. have a look at the following thread for some things that you can try:

https://frontaccounting.com/punbb/viewtopic.php?id=2523

you may want to try replacing the session.inc file as per the thread (mantis.frontaccounting.net --> bug 0001173).. although it didnt work for us.. you may have different results..

cheers

4

(16 replies, posted in Installation)

itronics wrote:

Addendum: patched version 2.3.8 works right also on Ubuntu 11.04 just installed on my laptop.
Janusz

Are you able to try and upgrade from an existing 2.3.7 installation with existing companies, and verify if all is okay?
i can also confirm that clearing browser cache doesnt work.

5

(16 replies, posted in Installation)

ahh, for a minute i thought it was just me experiencing these issues.

@joe, sure i wouldnt mind helping trace this.. the only problem is that there isnt much verbosity happening with the errors even with debug flags set to 1.

6

(16 replies, posted in Installation)

Hi All,

We're experiencing an issue when trying to upgrade to 2.3.8 from 2.3.7. The webserver im using is Debian 5 x64, with apache 2.2.9 and PHP 5.2.6.

When i overwrite the files on the webserver with the new version (to upgrade it), the site just gives a blank white page when you visit the URL. However, in the apache error_log, i get the following errors:

[Wed Nov 16 15:38:00 2011] [error] [client 196.44.*.*] 0::session.inc:297: Non-static method SessionManager::sessionStart() should not be called statically
[Wed Nov 16 15:38:00 2011] [error] [client 196.44.*.*] 0::session.inc:28: Non-static method SessionManager::validateSession() should not be called statically
[Wed Nov 16 15:38:00 2011] [error] [client 196.44.*.*] 0::session.inc:31: Non-static method SessionManager::preventHijacking() should not be called statically
[Wed Nov 16 15:38:03 2011] [error] [client 196.44.*.*] 0::session.inc:297: Non-static method SessionManager::sessionStart() should not be called statically
[Wed Nov 16 15:38:03 2011] [error] [client 196.44.*.*] 0::session.inc:28: Non-static method SessionManager::validateSession() should not be called statically
[Wed Nov 16 15:38:03 2011] [error] [client 196.44.*.*] 0::session.inc:31: Non-static method SessionManager::preventHijacking() should not be called statically

I have found bug 0001173 on mantis.frountaccounting.com, and have tried the new session.inc file, which does not make a difference, and you just get a blank white page...however, the PHP errors above, do not appear in the error log.

I have turned on PHP display_errors, and have set $go_debug to 1 in the config.php..but no errors come up at all. i have double checked file permissions on the server, and i can confirm that the site does work when i restore the 2.3.7 files into webroot folder.

any help would be much appreciated.

Hi,

not sure if you have resolved this.... but you may need access to the webserver error logs to see what is causing the issue..usually these kind of errors dont make sense on the front end, but will have a greater explanation in the error log.

depending on your server configuration (or webhost) the error log would be, for example, located on a debian linux server in /var/log/apache2 directory and the error log would be called 'error.log'

the first thing i would do is check the file owner and permissions of the front accounting files you moved across from your previous server. some webhosts do not allow .htaccess files.. so maybe try renaming .htaccess to just 'htaccess' and see if the error goes away.