1

(11 replies, posted in Report Bugs here)

Thanks Janusz!

I did a:

# pwd
/var/www/fa/company
# mkdir -p 1 2 3
# chmod -Rv 777 *

Then logged into FA as admin and deleted company 2 and 3 no problem. Company 4 is now effectively company 2 using the /var/www/htdocs/fa/company/1 directory.

That did the trick. Of interesting note is that what was previously company 4, which had the table prefix 3_, still has the same prefix (Like you said it has nothing to do with the ...fa/company/ directory tree naming scheme), and after deleting company 2 and company 3 it still retains the same table prefix, which I believe is what you were trying to explain in another post above.

Once again,

Thanks smile

2

(11 replies, posted in Report Bugs here)

itronics wrote:

Nothing has changed in this matter so far, answer to your question you can find in second post in this thread.
Janusz

Okay I saw that there was one file there that wasn't chmod'd 777:

-rw-r--r-- 1 apache apache  147 Nov 28  2011 installed_extensions.php

So I set it 777. When that didn't work I:

root@hammer:/var/www/htdocs/fa/company# chmod -Rv 777 .

And I still got the same error when trying to remove a company.

So finally I set everything from the DocumentRoot of the FA installation (/var/www/htdocs/fa) on down as 777 and still I'm receiving the same error.

Everything in the entire FA installation, all directories and files, to 777

What should I look at trying next?

Thanks )

Hi, I'm getting the following errors when trying to install a new extension:

Security alert: broken package 'http://anonymous:password@repo.frontaccounting.eu/2.3/extensions/import_paypal-2.3.10-1.pkg' in repository. Please inform repository administrator about this issue.Package 'import_paypal' not found.

I'm logged in as admin and running FrontAccounting 2.3.9

Is there something wrong with the repo? I can offer dedicated repo hosting/mirroring if it is needed out of my datacenter at One Wilshire smile

Thanks, and looking forward to hearing back at your earliest convenience.

4

(11 replies, posted in Report Bugs here)

I'm getting that same error:

Broken company subdirectories system. You have to remove this company manually.

This is what my directory tree looks like with 4 companies:

root@hammer:/var/www/htdocs/fa/company# ls
0/  index.php*
root@hammer:/var/www/htdocs/fa/company# ls 0
backup/  images/  index.php*  installed_extensions.php  js_cache/  pdf_files/  reporting/
root@hammer:/var/www/htdocs/fa/company# ls -la  
total 16
drwxr-xr-x  3 root root 4096 Nov 27  2011 ./
drwxrwxrwx 23 root root 4096 Nov 28  2011 ../
drwxrwxrwx  7 root root 4096 Nov 28  2011 0/
-rwxrwxrwx  1 root root   43 Nov 24  2011 index.php*
root@hammer:/var/www/htdocs/fa/company# ls -la 0
total 36
drwxrwxrwx 7 root   root   4096 Nov 28  2011 ./
drwxr-xr-x 3 root   root   4096 Nov 27  2011 ../
drwxrwxrwx 2 root   root   4096 Nov 28  2011 backup/
drwxrwxrwx 2 root   root   4096 Nov 28  2011 images/
-rwxrwxrwx 1 root   root     43 Nov 24  2011 index.php*
-rw-r--r-- 1 apache apache  147 Nov 28  2011 installed_extensions.php
drwxrwxrwx 2 root   root   4096 Jun 10 00:05 js_cache/
drwxrwxrwx 2 root   root   4096 Nov 28  2011 pdf_files/
drwxrwxrwx 2 root   root   4096 Nov 27  2011 reporting/

I only see one directory there, and I'm running FrontAccounting 2.3.9.

Shouldn't there be a company/1, company/2, and company/3 directory?

What's the next thing to look at for manually removing a company?

Thanks smile

5

(9 replies, posted in Installation)

If your intention is to run a serious production system, I wouldn't think that would be particularly well served by using the ubuntu distribution.

You should probably look at Slackware, Debian, or CentOS, if you're looking for a stable server platform upon which to base your business operations. FreeBSD, OpenBSD, DragonFlyBSD, and Solaris 10 are also good (and free) enterprise platforms to choose from too.

We have installed bases of FA on all of the server platforms I mention above, and it runs flawlessly on them, but I wouldn't even consider using an ubuntu for serious mission critical operations.

Setting and flopping such permissions is actually very commonplace with database driven, secure, web-based applications.