My preference is to use it with PHP-FPM to make it easier to support newer PHP for everything else. While PHP-FPM is not officially supported by ownCloud, I have successfully run it that way for more years than I can remember.
i think it is important to note that Bullseye will be the next âLTSâ version with additional support until August 31st, 2026 if iâm understanding LTS - Debian Wiki correctly.
But iâm not sure if this also includes additional (security) support for PHP 7.4
I am also very interested in a PHP 8 Support.
Is there any news? Is this aforementioned PR still worked upon? Or is there maybe any info if or when this can be expected in the near future?
Ok, sounds legit.
But is there any effort in this direction?
Any timeline?
I donât understand why this is handled so poorly and seem to have no priority. In my eyes this will creep out users over time getting more rapid by the minute.
For my case the migration to next cloud also seems to get inevitable over time, if this keeps on going.
iâm not sure but i donât think that the ownCloud people will share any internals on this matter or will give any details in public here (otherwise i think they probably would have done this already since this thread was created two years ago).
But i think it could be possible that their priorities have shifted with the introduction of oCIS or with the acquisition of ownCloud by Kiteworks. Maybe the days of the PHP based ownCloud are already counted? But i think we can only do assumption from user side
I for myself are also weightening my options but luckily i have time until August 31st, 2026 when PHP 7.4 support will probably end in Debian Bullseye.
Hey,
I agree. But at least they could be up front about it, if it is not coming then at least they could make it clear once and for all.
There are loads of php own cloud instances running and I donât think changing the complete code basis away from PHP is a viable option for most people.
I think it is a mistake to let the users down like that, but what do I know. For me it gets more clear every day, that a migration to next cloud will have to be the way.
I am sorry, but they leave us no choice.
cleaning up - I think this is no longer of anybodyâs interest
Further comments includes:
The end of owncloud 10 was marked by the time all forces have been moved to infinite scale. It was quite obvious in all these years. Not really shocking - right?
There is also a similar note here:
I think how this was handled from ownCloud side (no real announcement, no more details then given in the first post) and the general lack of communication from them is quite frustrating
I think if it was so obvious like indicated in the first quote from the GitHub pull request then i think they could have easily made an official announcement rather then keeping a GitHub pull request for PHP 8.x compatibility that long open. I think this has been contributed a lot to some misinterpretations or speculations
I think it is time to start planning to migrate away from ownCloud 10 to a different product now.
This is disappointing news. Infinite Scale doesnât do most of the things for which I use ownCloud. I guess I need to start testing another CalDAV server and hunt for a replacement CardDAV solution. I have enjoyed using ownCloud for those functions for over a decade.
I see that you brought this concern in another topic already.
i will also try to evaluate alternatives to ownCloud because for me quite a lot trust has been lost due to the way this topic was handled as also expressed by another user in the previously linked GitHub pull request:
That itself was not shocking.
The fact that this branch existed and now abandoned signals some change that you folks have all the rights to reserve to yourself. I get that, I guess many people get that. But thatâs the trust eroded that you wonât get back anytime soon.
For me as a home user OCIS seems to be also way too complex with all the different services involved (i see a lot of OCIS problems posted here without much support).