php_include problem with 2.21 under Ubuntu 18 / apache

Get help from other users here.

Moderators: Developer, Contributor

Post Reply
tvleavitt
Posts: 3
Joined: 13 May 2019, 23:07

php_include problem with 2.21 under Ubuntu 18 / apache

Post by tvleavitt »

I downloaded the tar.gz file and copied the contents to /var/www/html... but when I attempt to run the admin/install.php, I get an error 500 message, and this in the apache server error.log:

[Mon May 13 13:57:10.821777 2019] [php7:error] [pid 24252] [client 10.0.1.121:56976] PHP Fatal error: require_once(): Failed opening required '/var/www/html/mantisbt-release-2.21.0/vendor/autoload.php' (include_path='.:/usr/share/php') in /var/www/html/mantisbt-release-2.21.0/core.php on line 91

Now, of course, I could just bypass this and add the install directory to the php include_path directive, but that seems to defeat the purpose of having it in the first place, and it's my understanding that you shouldn't have "include" directories in web-accessible directories... so, what do I do? All the install walkthroughs blithely assume everything works at this point.

This is a stock installation of Ubuntu 18.04 and apache with php-fpm enabled. Nothing else installed on the box, no additional customizations made (although I've disabled access via http and only permit access via https) using the default-ssl.conf file (this is one a private network).
atrol
Site Admin
Posts: 8366
Joined: 26 Mar 2008, 21:37
Location: Germany

Re: php_include problem with 2.21 under Ubuntu 18 / apache

Post by atrol »

I assume you did not download from official download page https://www.mantisbt.org/download.php
Please use Search before posting and read the Manual
tvleavitt
Posts: 3
Joined: 13 May 2019, 23:07

Re: php_include problem with 2.21 under Ubuntu 18 / apache

Post by tvleavitt »

I downloaded it from the GIT repo, yes. Not sure how I wound up there in the first place, Google search of some sort. Some kind of warning that installing from there won't work due to missing pieces would be nice, or better error messaging indicating what's missing. Most folks will assume that the code in a git repo that matches the stable version will work.

After I figured out what the problem was, I was able to get it working (with minor pains).
Post Reply