FrontAccounting forum — Cannot install new extensions—"could not open"

Re: Cannot install new extensions—"could not open"

2014-03-30T08:45:56Z

I downloaded the files to the modules folder and edited the installed_extensions.php files. This appears to have done absolutely nothing. Nothing new appears on the UI and it does not show as a new tab or anywhere in the reports screen. It's entirely possible that I put the wrong thing in the installed_extensions.php files, because I am just looking at the documentation making my best guess at what the correct values are supposed to be.

Let's back up—rather than doing an end-run around the installer and probably making a mess of things, can we figure out why the installer isn't working? The installer provided should theoretically work, so can we get to the bottom of why we can't use that?

Re: Cannot install new extensions—"could not open"

2014-03-12T15:17:56Z

Take them from my GitHub Unofficial Repo - extension files.

Re: Cannot install new extensions—"could not open"

2014-03-07T12:22:25Z

Where should I get the module files from? The .pkg file I found appears to be incomplete. (There are no PHP files in them, for instance.)

In any case, if at all possible, I'd prefer to be able to fix FrontAccounting to install the extension the proper way rather than manually forcing it through—there's a lot of interesting-looking extensions listed, and installing them all manually sounds pretty tedious. If we can find out what's wrong, it may be useful to others with the same problem in the future.

Re: Cannot install new extensions—"could not open"

2014-03-06T14:41:59Z

Manually install the files from the module into the modules folder and update the installed_extensions.php files in both the webroot and the company # folders.

Re: Cannot install new extensions—"could not open"

2014-02-27T06:24:21Z

All of the named folders appear to be configured correctly. However, in checking that, I did find the errors.log file, which contains this:

archive.inc:381: is_dir() expects parameter 1 to be a valid path, string given
archive.inc:382: mkdir() expects parameter 1 to be a valid path, string given
archive.inc:411: touch() expects parameter 1 to be a valid path, string given
archive.inc:395: fopen() expects parameter 1 to be a valid path, string given
packages.inc:165: gzopen(../modules/_cache/rep_check_print-2.3.0-1/_init/config): failed to open stream: No such file or directory
archive.inc:462: gzopen(../modules/_cache/rep_check_print-2.3.0-1/_data): failed to open stream: No such file or directory

It appears to be accessing these files and not being able to because they aren't there. Could there be something that is stopping Apache from downloading the files? (I'm running on LAMP, specifically Fedora 20). What URL does it pull the files from; maybe that's down?

Re: Cannot install new extensions—"could not open"

2014-02-27T03:03:58Z

folder permissions issue - for the tmp folder, and installed_extensions.php files in the webroot and company folders

Cannot install new extensions—"could not open"

2014-02-25T07:48:53Z

I am attempting to install the check-writing module, and it displaying an error saying "Could not open". I have searched the forum for information, and checked all of the following: curl and xmlrpc are both installed and showing as active in phpinfo, and the modules and _cache directories are writeable.

I looked in the _cache directory, and it appears to be creating Charts.gz, Extensions.gz, and Release.gz, and creating the rep_check_print-2.3.0-1 folder, but there is nothing in it.

This issue is occurring with every module I attempt to install.