XF 2.1 Constants already defined in php72compat_const.php after upgrade

[PetersWeb]

I've recently upgraded from 2.1x to 2.1.5a and now received many errors referring to various (20+) constants already defined in my Xenforo Directory /src/vendor/paragonie/sodium_compat/lib/php72compat_const.php on line 86

Has anyone else received similar errors?

 

[PetersWeb]

I have been able to find a solution. Apparently, it's a result of an incompatibility between two versions of the sodium_compat library deployed by WordPress and XenForo. The library authors have deployed a patch, but it yet needs to be shipped with either software.

I just uploaded the new files to my WP site which then fixed the problem.

 

[Chris D]

I might be wrong, but thus far I have assumed that if you are running PHP 7.2 or 7.3 then the library wouldn't be loaded at all therefore that is usually going to be the most logical solution and in some hosting environments, a couple of clicks to enable.

 

[Victoria Bampton]

PetersWeb, could you please share which files you uploaded? I'm just testing updates on my staging site (which is on 7.2,24) and I'm hitting the same issue). Thank you!

 

[covertedin2017]

I might be wrong, but thus far I have assumed that if you are running PHP 7.2 or 7.3 then the library wouldn't be loaded at all therefore that is usually going to be the most logical solution and in some hosting environments, a couple of clicks to enable.

Chris, I'm running PHP 7.3 and encounter this issue as well.

 

[StoveBolts]

I am running php 7.2.25 and am receiving a similar error.
Unfortunately, it created a 5 gig error log which put a pretty heavy dent on my storage space.

XF 2.1 - 5 gig php error log created

I logged in to my site today to find my disc space almost full due to a very large log file. Here is what Tech support had to say. Hello, Thank you for contacting *** Technical Support Team! We would like to inform you that the logs directory contains Apache access and error logs for the...

xenforo.com

Had I not logged into my server, I would have never noticed the increase in disc usage. A few more errors and my site would have shut down due to exceeding disc space.

Looks like I'll be logging into my VPS each day to delete log files until this can get resolved. I'll be following this thread for a fix

 

[teletubbi]

Looks like I'll be logging into my VPS each day to delete log files until this can get resolved.

There is a program called logrotate.