On 12/10/25 10:11 AM, David C Rankin wrote:
On 12/10/25 9:56 AM, Andy Pieters wrote:
To me this looks more like a bug in the nextcloud rather than PHP
I did see a ticket being opened on nextcloud talking about this same
thing, presume this was yourself?
Yes, that's the ticket I opened with Nextcloud:
https://help.nextcloud.com/t/nextcloud-32-call-to-undefined-function-oc-
security-idn-to-utf8/237090
No response yet, but not two-days old yet. I'll keep you posted here if
I get a solution there.
I'm going to bump this thread again. I've had no response in 8-days on
the nextcloud support list. Usually they get back quicker if it's an
issue that is more widespread or they have a fix for.
Is there any way the minor version update in php-legacy from 8.2 to 8.3
could be the culprit? Is this worth opening an issue with either
nextcloud or php-legacy at gitlab, if for nothing else to track upstream
progress?
Nextcloud 33 is out, so the lack of response on the support forum could
be a "wait until 33 is installed and see if the same thing occurs".
Which I can do. It's just the admin functions that are broken by the
idn_to_utf8() issue. I can get to the data and normal user apps. And
since I use the Arch nextcloud package, I can upgrade without relying on
the nextcloud admin functions.
If any of the devs have a preference in course of action, let me know,
otherwise, I'll just wait for the 33 package and see if the issue
remains. (no hurry, holiday season is busy for everyone)
--
David C. Rankin, J.D.,P.E.
