Hello illiminal!
Nice find! Indeed it should be __(). I’ll add the fix in the upcoming patch (tonight probably).
It’s weird that it cause problem on your setup, because there’s a compatibility function in WP core for this case in wp-includes/compat.php:10.
It’s also a native translation PHP function _().
Just out of curiosity, can you tell me your WP + ACF + PHP version?
Do you have any error/warning in your logs about it?
Thanks for the report 🙂
Regards.
Hello,
Just to let you know that the new patch fix this issue 🙂
Have a nice day!
Regards.
Thanks so much for the quick fix! 🙂
Sorry, I didn’t get to reply earlier, but my config is:
WP: 5.2.2
ACF: 5.7.13
PHP: 7.2.8
This is my local dev install, using MAMP 5.1.
The only thing I could find is that it looks like I was getting a segmentation error in PHP at this time in my Apache error logs, along the lines of:
child pid XXXXX exit signal Segmentation fault (11)
Looks like this is related to the issue, since I just went back in and reintroduced the old code to test and got this same error again. Not sure if there is maybe a module or extension in my PHP which is conflicting, or something in the WP theme/setup that’s interfering with the WP compatibility function – definitely seems to be something specific to my config either way.
Hello!
I just checked the error child pid XXXXX exit signal Segmentation fault (11) and it looks like it’s related to apache/PHP configuration.
You should check your PHP ini file, and specifically the memory_limit property. Try to rise it to 512M (Make sure there is a M unit. If it’s missing, it can cause this kind of errors).
Here is a tutorial for MAMP: http://blog-en.mamp.info/2009/09/increase-php-memory-limit-with-mamp-pro.html
Hope it will work!
Regards.