Question K 4.0.2 needs PHP 'fileinfo'

Is PHP extension 'fileinfo' realy needed?

Yes fileinfo is needed, it's provided in default php package. You have to enable it in your php.ini

that's the problem, until now it wasn't needed and the shared hosting that im using can't provide it on current plan witch i already extended for 2 more years 3 months ago

You revert this change in the K4.0.2 package : github.com/Kunena/Kunena-Forum/commit/6d...707e544117f99f49516e

in order to be able to install k4.0.2 but fileinfo is used to determine if the attachment is an image or not, i need to find an another to that to remove the fileinfo requirement

The PHP fileinfo extension is only required for people who want to use some of the additional functionality included by the Crypsis template. It is not required by Blue Eagle or by other templates derived from Blue Eagle.

For most users who use a shared webhosting platform, the ability to enable the fileinfo extension is beyond their capability. Enabling or disabling PHP features (in a shared hosting environment) is determined under the policy of the webhosting provider.

By requiring, in the K 4.0.2 pre-installation check, the need to have the PHP fileinfo extension enabled, this effectively means that people are unable to install K 4.0.2 on their websites. Of course, if people have complete control over their webhosting environment (because they use VPS or localhost (e.g. XAMPP, MAMP etc.) they can enable/disable PHP features as they like. However, VPS solutions are expensive and localhost environments are really only useful for local testing (that is, not for production purposes).

Since K 3.0.7 was released, there have been numerous problems with installation of Kunena on Joomla. As we are all aware, the Install by URL method had been impossible to use since the installation kits were relocated to GitHub. In the time since we began discussing the Install by URL method , we know that the Kunena upgrade guide has been changed .

The current K 4.0.2 installation package requires that the PHP fileinfo extension is installed and enabled on a user's webhosting platform. The pre-installation check is not required if people do not want to use the Crypsis template and it can be removed if that is what people desire.

Unless people have the ability to install or enable various PHP extensions, they will not be able to install or upgrade to K 4.0.2 while this pre-installation check exists. This probably means that 9 out of 10 people (who use shared hosting environments) will be unable to install or upgrade to K 4.0.2 while this dependency exists in Kunena. I think that's important and something people need to be aware of.

I would suggest that this topic be made sticky and allow full, open and honest commentary/feedback from the community.

xillibit wrote: You revert this change in the K4.0.2 package : github.com/Kunena/Kunena-Forum/commit/6d...707e544117f99f49516e

in order to be able to install k4.0.2 ...

True. I was able to install K 4.0.2 on my website by changing the install.script.php file. But it is not possible to upload attachments ... even with Blue Eagle!

There is an additional dependency involved.



If people do not have the PHP fileinfo extension enabled (and that is 9 out of 10 people on a shared webhosting environment) then they will not be able to upload attachments even if they use Blue Eagle (or another template derived from Blue Eagle—and that's 99% of all alternative Kunena templates).

So there is more than just a one-line change involved here.