Too bad, it stopped working for version 5. After a quick check, I was able to make it work again within my version 1.0.1.
I've created two more versions to prepare the code base for upcoming php versions.
Within version 1.0.2, I have introduced composer and fixed the code quality by using phprector.
Within version 1.0.3, I have introduced php-cs-fixer to make the code look great again.
And of course, I have created a pull request to the source.
Thanks to my current employer giving me the opportunity to fix this issue during my working hours.
I wanted to install dolibarr on my arch linux machine.
The first steps are simple and I tried to stick to the official but little outdated aur package.
#as root
cd /usr/share/webapps
mkdir dolibarr
cd dolibarr
git clone https://github.com/dolibarr/dolibarr -b 14.0.1 .
cd ..
choown -R http:http dolibarr
sudo -u http touch dolibarr/htdocs/conf/conf.php
cat > /etc/httpd/conf/extra/httpd-dolibarr.conf <<DELIM
Alias /dolibarr "/usr/share/webapps/dolibarr/htdocs"
<Directory "/usr/share/webapps/dolibarr/htdocs">
AllowOverride All
Options FollowSymlinks Indexes
Require all granted
</Directory>
# vim: set ft=apache ts=2 sw=2 et:
DELIM
echo "#dolibar" >> /etc/httpd/conf/httpd.conf
echo "Include conf/extra/httpd-dolibarr.conf" >> /etc/httpd/conf/httpd.conf
systemctl restart httpd.service
After that, I wanted to open my http://<hostname>/dolibarr and it worked out quite well. The build in installation routine started and I was able to click to the next page to check the system.
Almost all went well but it took me hours to figure out why the installation routine complained about the conf.php file. It had the right permissions (u+rw) but the php built in is_writable is returning false for this file.
It wasn't a running selinux, it wasn't a wrong configured php open_basedir or php safemode. It really turned out, that apache http refuesed to allow writing to a file outside than the configured home path of /srv/http.
Even a softlink created in /srv/http linking to /usr/share/webapps/dolibarr was not working.
What was working is to mv /usr/share/webapps/dolibarr /srv/http and to adapt the httpd-dolibarr.conf.
We are running our monitoring solution zabbix on an arch linux system.
Arch linux tends to be "up to date" since it philosophie is "patch current code base, not legacy".
I've updated the monitoring system and with that, the php version jumped from 7.4.x to 8.0.x.
After that, a lot of "widgets" (boxes) in the zabbix frontend displayed me a lot of the following error.
I've researched it and found that the error exists in the DB.php class.
I've opened the issue Ticket ZBX-18984 and created the pull request 39 on the github source code.
Hopefully, this fix will make it quickly into the code. I've added a git patch file to the issue. You can download and apply it on your system.
I wanted to quickly develop something. I thought this is the perfect timing to migrate mentally from the insecure and almost dead docker to the alive and secure podman.
I went to the page of thecodingmachine and tried it with the following one-liner:
podman run -p 80:80 --rm --name php-bazzline -v "$PWD":/var/www/html thecodingmachine/php:7.4-v3-apache
Sadly nothing is working so I've created a feature request asking for podman support.