Possible bug with ACF Pro

[Federico]

Hello,
I just wanted to report a possible bug with ACF Pro.
When saving/updating a post with ACF Pro fields, I now get an error (wp_admin/post.php):

====================
Un errore di E_ERROR è stato causato nella linea 8 del file /web/htdocs/www.mywebsite.com/home/wp-content/plugins/ajax-search-pro/includes/classes/Utils/Html.php. Messaggio di errore: Uncaught TypeError: Argument 1 passed to WPDRMS\ASP\Utils\Html::toTxt() must be of the type string, array given, called in /web/htdocs/www.mywebsite.com/home/wp-content/plugins/ajax-search-pro/includes/classes/Index/Tokenizer.php on line 46 and defined in /web/htdocs/www.mywebsite.com/home/wp-content/plugins/ajax-search-pro/includes/classes/Utils/Html.php:8
Stack trace:
#0 /web/htdocs/www.mywebsite.com/home/wp-content/plugins/ajax-search-pro/includes/classes/Index/Tokenizer.php(46): WPDRMS\ASP\Utils\Html::toTxt()
#1 /web/htdocs/www.mywebsite.com/home/wp-content/plugins/ajax-search-pro/includes/classes/Index/Manager.php(775): WPDRMS\ASP\Index\Tokenizer->tokenizeSimple()
#2 /web/htdocs/www.mywebsite.com/home/wp-content/plugins/ajax-search-pro/includes/classes/Index/Manager.php(337): WPDRMS\ASP\Index\Manager->tokenizeCustomFields()
#3 /web/htdocs/www.mywebsite.com/home/wp-content/plugins/ajax-search-pro/includes/classes/Hooks/Actions/IndexTable.php(97): WPDRMS\ASP\Index\Manager->indexDocument()

====================

Rolling back from 4.31.1 to 4.22.5 fixes the problem.
Hope it’s useful to check if there’s actually a bug.
Best,

Federico

[Ernest Marcinko]

Hi Federico,

It definitely looks like it is. Can you please try a modification to see if this resolves it:
– Open up the wp-content/plugins/ajax-search-pro/includes/classes/Index/Tokenizer.php file on your server, replace it’s contents with this
– Then wp-content/plugins/ajax-search-pro/includes/classes/Utils/Str.php file, replace with this
– Save them both, and try to replicate the bug, it should no longer appear.
Please let me know if this helps.

[Federico]

Well, I believe the fix has been pushed in the 4.23.2 update because now it works without a hitch (and without the proposed modifications)!
Thank you very much!
Best,

Federico

[Ernest Marcinko]

Great 🙂 I will mark this bug as resolved.

[Author]

Posts