FrontAccounting forum — Some 2.3RC1 issues

Re: Some 2.3RC1 issues

null@example.com (itronics) — Fri, 19 Aug 2011 08:56:02 +0000

Check Extensions System section in System Diagnostics page under Setup tab.
Janusz

Re: Some 2.3RC1 issues

null@example.com (littlez) — Thu, 11 Aug 2011 03:01:04 +0000

Is there a fix for this problem?
i have the same problem under themes and extension.
When I click add extensions or themes it just says "Release file in repository is invalid, or public key is outdated."
I am using FA 2.3.5
Suse 11.4

Re: Some 2.3RC1 issues

null@example.com (sbasurto) — Thu, 14 Jul 2011 23:04:08 +0000

I start with a new fresh installation an it is sending the same message in the step 3
--------------------------------------------------------------------------------------------
Release file in repository is invalid, or public key is outdated
FrontAccouting ERP Installation Wizard
Step 3: User Interface Languages Selection
--------------------------------------------------------------------------------------------

Re: Some 2.3RC1 issues

null@example.com (itronics) — Fri, 24 Sep 2010 12:48:39 +0000

The remote_ur.inc is new file and should be placed under includes folder in root FA dir.
Yes, you can reverse the changes - the new files should work with any php configuration.
Janusz

Re: Some 2.3RC1 issues

null@example.com (avb3) — Thu, 23 Sep 2010 16:12:17 +0000

Janusz:

OK... I installed a phpinfo.php file as my php.ini was hidden .

I edited it, and now the parameters that report back are as you suggested, in other words, the allow_url_fopen is set to "ON" (actual command line is allow_url_fopen = 1).

This did not help. I logged out, closed browser, cleared my cache and tried again.

I found the new files in Mantis, and was able to find the locations for the gl_db_rates.inc and packages.inc, however, I can not find where the remote_url.inc should go... I assume that is a new file.

So two questions, where does the remote_url.inc go, and can I change my php.ini back to get rid of the allow_url_fopen, as there has been some suggestion there may be security concerns with it being "on".

Thanks in advance.

Re: Some 2.3RC1 issues

null@example.com (itronics) — Thu, 23 Sep 2010 07:46:01 +0000

This is system configuration file, so it is not distributed with FA. I don't know what system are you using - php.ini location depends on it. It is usually placed in /etc/php5/apache2 on Linux using Apache www server.
Janusz

BTW I have just reported this issue in mantis - you can download fixed files attached to report 248.
J.

Re: Some 2.3RC1 issues

null@example.com (avb3) — Wed, 22 Sep 2010 22:27:12 +0000

Hmmm... I don't see a php.ini file in any of my Frontaccouting instances, whether it is 2.x or 2.3RC1. I do have php.ini files in some of my other databases I am running, and they all work fine.

As I can't seem to see the php.ini file in the 2.3RC1 download, could you refer me to where I could get one to d/l?

Re: Some 2.3RC1 issues

null@example.com (itronics) — Wed, 22 Sep 2010 21:22:30 +0000

Regarding first point I have no idea. Have you any error messages in error log? You can set $go_debug=1 as usually to see additional error messages.

The problem with theme installing can be related to your php.ini setup. If you have access to server php configuration try setting allow_url_fopen to 1. This issue is fixed in CVS and the patch will be available in next 2.3 release.

Janusz

Some 2.3RC1 issues

null@example.com (avb3) — Wed, 22 Sep 2010 20:04:31 +0000

Not sure what other feed back your getting (I don't see these issues when I do a search), but the following happened today:

1) I tried installing 2.3RC1 to use as a test bed. On the first attempt, once the install showed as complete (to this point everything looked OK), I tried running index.php and all I got was a blank screen.

I deleted all files on the server, re-installe 2.3RC1, and this time the only difference was that I did not ask the additional COA's to be included.

It worked the second time.

2) I tried to install Themes (I really like Exclusive theme just released) and got the following message: "the Release file in repository is invalid, or public key is outdated."

I got the same message for installing COA's.

Any thoughts?