Closed V1ck3s closed 5 months ago
Hi,
I think these appear on newer PHP versions (or FPM). It should be related to an older syntax used in the script which is being deprecated in newer PHP versions.
I'm assuming you also updated PHP with the nginx update? Also, if possible, could you give me your PHP version, just to confirm that you're using a fairly new version?
I'll see if I can get this fixed soon. It should just be a matter of updating the syntax to a newer PHP standard on the affected lines.
Yes, you are right. I have updated a docker image, that's using PHP-FPM 8.2 & Nginx 1.24
Can we have a new release with this fix ? Thank's
Can we have a new release with this fix ? Thank's
I'll see if I can do that soon.
In the meantime, you can also build it yourself by cloning the repository, editing the build.options.json if needed, and building:
git clone https://github.com/sixem/ivfi-php
cd ivfi-php
npm install
npm run build
Can we have a new release with this fix ? Thank's
I'll see if I can do that soon.
In the meantime, you can also build it yourself by cloning the repository, editing the build.options.json if needed, and building:
git clone https://github.com/sixem/ivfi-php cd ivfi-php npm install npm run build
I'm not a JavaScript developer and don't want to install npm, but thanks. It would not be possible to do a workflow for release when there is a commit on master branch ?
I've added a workflow that builds the project and produces a downloadable artifact on any changes now.
Describe the bug Deprecated messages after updating nginx.
To Reproduce If relevant, the steps to reproduce the behavior:
Expected behavior No deprecated messages
Information If possible, fill out the data:
Errors
Additional context I'm using the standalone php file.