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 216 of 246)
Topics by apmuthu User defined search
Posts found: 5,376 to 5,400 of 6,142
Lines 363-370 of sales/includes/sales_db.inc:
$sql = "SELECT parent.*
FROM
".TB_PREF."$par_tbl parent
LEFT JOIN ".TB_PREF."debtor_trans_details trans
ON trans.src_id=parent.id
WHERE
trans.debtor_trans_type=".db_escape($trans_type)
." AND trans.debtor_trans_no=".db_escape($trans_no);
This file was last changed in 2011-02-14.
No significant changes since v2.3.14 (2013-01-18) in the sql schema for the US standard 4 digit Chart of Accounts.
What Chart of Accounts are you using? Compare with the current one and see if there is any significant difference that might cause this kind of trouble.
Take a backup zip of your company's database and check.
Try upgrading directly to v2.3.18+Git.
Just do not take them into stock at all and make it as a direct expense voucher.
Make sure that php5-curl and php-xmlrpc have been installed
check file and folder permissions within the company folder and for the temp and cache folders.
can be latin1_unicode_ci too or latin_swedish_ci - but keep all the string fields and db collations the same.
Number of boxes would be useful for rough and ready administrative counting even if apples boxes are added to oranges boxes - they are still boxes at heart!
Check in Firefox browser with java plugin enabled.
Also some temp or cache folder may not have write access by the webserver user.
Unfortunately, despite my having put up the code both here and in my personal repo, the official repo does not want to get update the package as it is considered vulnerable.... The rationale here is possibly to retain a non working package for users to hack it themselves rather than a partially hacked version that will still require hacking albeit a lot less and yet usable.
Check where the httpd.conf resides - in debian it is in /etc/apache2/sites-available/* from where it gets symlinked to /etc/apache2/sites-enabled/* when a2ensite sitename is executed or it can be manually done and apache2ctl restart issued.
The following is declared inside the function set_global_connection($company=-1) in includes\db\connect_db.inc:
$db_duplicate_error_code = 1062;
The said error is triggered when the $db_error matches the above in function frindly_db_error($db_error) in includes/error.inc. The phrase frindly is used here instead of the more intuitive spelling friendly.
The function frindly_db_error is called in function check_db_error also in the same file includes/error.inc, which displays all other errors than this duplicate error.
The textcart extension may be what you need.
What OS?
What WebServer?
Since you used TAR, assuming linux (example Debian/Ubuntu) and that you already have your MySQL and PHP and Apache2 running and have created your FA database and user and assigned access of the database to the user.
wget https:/sourceforge.net/projects/frontaccounting/files/FrontAccounting-2.3/2.3.18/frontaccounting-2.3.18.tar.gz
tar -xzf frontaccounting-2.3.18.tar.gz -C /var/www
chown -R www-data:www-data /var/www/frontaccounting
Make sure that your apache server has it's root folder as /var/www/frontaccounting ( edit the file at /etc/apache2/sites-available/default and restart Apache with apache2ctl restart )
Now browse to http://IP.or.FQDN/ and start the web install. Have your FA Database name and user and password handy.
Make the database and tables latin1 and the columns default collation as latin1_general_ci or latin1_swedish_ci but it should be uniform throughout. Alternatively, make everything utf8 and collation utf8_general_ci which is the default recommended type.
It might be easier to take a backup of the sql, edit the sql and then restore it. The database collation and charset must be done outside of FA.
If you are using only english, then it may be okay but make sure the collation is the same for all string fields.
Yes, it is because your initial install may not have proceeded correctly. Manually create it from the sql in the extension.
Try to use the files from:
https://github.com/apmuthu/frontaccounting/tree/master/extensions/Extensions/repgen
Mainly the sql file will be different.
check the error log and / or turn on $debug=1; in the config.php
Which version of FA are you using?
What is the Host OS (Windows / Linux), WebServer (IIS/Apache) ?
Have you created your MySQL user, database and assigned appropriate privileges to the user for the database and flushed privileges to make the changes visible / usable?
Did you install any of the sqls for company 0 manually or did you go thru the full install with proper file and folder permissions?
https://frontaccounting.com/fawiki/index.php?n=Main.Usage
https://frontaccounting.com/fawiki/index.php?n=Main.ExtensionList
https://github.com/apmuthu/frontaccounting/tree/master/extensions
Joe, will need to clarify on the FA comment in:
http://wiki.xtronics.com/index.php/Linux_accounting
FrontAccounting
weberp fork via openaccounting LAMP GPL - Same kind of usability problems - If you go to enter a sales order, and you happen to have a new customer, there isn't even a navigation button to take the detour. Source forge rank = 356
Just checked out your site and it appears some files (index.php, config_db.php, etc) are served from some other location and the database parameters too are taken from probably some default setting in the php.ini or from the host. Turned off the install folder and renamed the .htaccess file to be an invalid name. Now there is less of a time out occurring.
This is due to the fact that the site is in previewdns mode and probably, on proper hosting in the production environment (with proper dns assignment), this issue will vanish.
Info location:
The Wiki page has a screenshot link in the Procedure para.
Let me know where you searched and did not find - and where in the wiki you would like the info to be placed. The more intuitive the place, the less such questions for the forum.
Joe, must we just toggle the default?
The only changes done to the admin/backups.php file was in v2.3.15 (made the error string translatable) and then earlier in v2.3.6.
Scrutinize the file change diffs from the Official Git repo for the said file and see if it affects your browser in any way - very little or no chance at all.
Various Report Workarounds are Wiki-ed as well.
Check your apache error logs possibly from your GoDaddy cPanel.
Try to craete a file say phpinfo.php in your webroot with the following:
and execute it from the browser and you will see a wealth of info like session path and then you can contact your GoDaddy support to fix any PHP.ini issues.
Please remove the phpinfo.php file after getting the browser output.
If you are still stuck, email / PM me with server access details after creating temporary access passwords that you can revert on completion of the troubleshooting.
Posts found: 5,376 to 5,400 of 6,142
