Uncaught ValueError: mb_convert_encoding(): Argument #3 ($from_encoding)

Hi @7thcircle,

Can you give us a little more information to help use replicate the issue. Are you seeing this on a Post or Page? Does the post/page have any content in the editor. Are you using the block editor or the classic editor?

Thanks!

I get this in an email after editing a page. The page is using GenerateBlocks, Block Visibility, and Gravity Forms. When I save on a WooCommerce site it takes a long time. The save is successful, but I get the error. I do not seem to get the error on non WooCommerce sites.

For reference, PHP 8.1 on Woo and 8.2 on other sites. All sites have GenerateBlocks, etc. All sites are running NGINX Redis, on GridPane.

@7thcircle I have been looking into this issue and can only reproduce it so far in one unlikely situation. Are you able to provide me with the list of encodings on your system returned from running mb_list_encodings(); so I can check if my investigations are on the right path.

Thanks in advance!

• This reply was modified 8 months ago by williampatton. Reason: Typos and grammar

array(78) { [0]=> string(6) “BASE64” [1]=> string(8) “UUENCODE” [2]=> string(13) “HTML-ENTITIES” [3]=> string(16) “Quoted-Printable” [4]=> string(4) “7bit” [5]=> string(4) “8bit” [6]=> string(5) “UCS-4” [7]=> string(7) “UCS-4BE” [8]=> string(7) “UCS-4LE” [9]=> string(5) “UCS-2” [10]=> string(7) “UCS-2BE” [11]=> string(7) “UCS-2LE” [12]=> string(6) “UTF-32” [13]=> string(8) “UTF-32BE” [14]=> string(8) “UTF-32LE” [15]=> string(6) “UTF-16” [16]=> string(8) “UTF-16BE” [17]=> string(8) “UTF-16LE” [18]=> string(5) “UTF-8” [19]=> string(5) “UTF-7” [20]=> string(9) “UTF7-IMAP” [21]=> string(5) “ASCII” [22]=> string(6) “EUC-JP” [23]=> string(4) “SJIS” [24]=> string(9) “eucJP-win” [25]=> string(11) “EUC-JP-2004” [26]=> string(18) “SJIS-Mobile#DOCOMO” [27]=> string(16) “SJIS-Mobile#KDDI” [28]=> string(20) “SJIS-Mobile#SOFTBANK” [29]=> string(8) “SJIS-mac” [30]=> string(9) “SJIS-2004” [31]=> string(19) “UTF-8-Mobile#DOCOMO” [32]=> string(19) “UTF-8-Mobile#KDDI-A” [33]=> string(19) “UTF-8-Mobile#KDDI-B” [34]=> string(21) “UTF-8-Mobile#SOFTBANK” [35]=> string(5) “CP932” [36]=> string(8) “SJIS-win” [37]=> string(7) “CP51932” [38]=> string(3) “JIS” [39]=> string(11) “ISO-2022-JP” [40]=> string(14) “ISO-2022-JP-MS” [41]=> string(7) “GB18030” [42]=> string(12) “Windows-1252” [43]=> string(12) “Windows-1254” [44]=> string(10) “ISO-8859-1” [45]=> string(10) “ISO-8859-2” [46]=> string(10) “ISO-8859-3” [47]=> string(10) “ISO-8859-4” [48]=> string(10) “ISO-8859-5” [49]=> string(10) “ISO-8859-6” [50]=> string(10) “ISO-8859-7” [51]=> string(10) “ISO-8859-8” [52]=> string(10) “ISO-8859-9” [53]=> string(11) “ISO-8859-10” [54]=> string(11) “ISO-8859-13” [55]=> string(11) “ISO-8859-14” [56]=> string(11) “ISO-8859-15” [57]=> string(11) “ISO-8859-16” [58]=> string(6) “EUC-CN” [59]=> string(5) “CP936” [60]=> string(2) “HZ” [61]=> string(6) “EUC-TW” [62]=> string(5) “BIG-5” [63]=> string(5) “CP950” [64]=> string(6) “EUC-KR” [65]=> string(3) “UHC” [66]=> string(11) “ISO-2022-KR” [67]=> string(12) “Windows-1251” [68]=> string(5) “CP866” [69]=> string(6) “KOI8-R” [70]=> string(6) “KOI8-U” [71]=> string(9) “ArmSCII-8” [72]=> string(5) “CP850” [73]=> string(16) “ISO-2022-JP-2004” [74]=> string(23) “ISO-2022-JP-MOBILE#KDDI” [75]=> string(7) “CP50220” [76]=> string(7) “CP50221” [77]=> string(7) “CP50222” }

Copied

Hey @7thcircle,

Thanks for sharing that. It is the same list that I have on my system so my suspicions about what caused this for you were incorrect. I will need to create a GitHub issue for this and continue my investigations over there as part of our typical workflow. I discovered some php 8 quirks in one of the packages used for the scan which needs deeper consideration about how to tackle them.

It might be helpful for me if you were able to share the post content of the page that triggered this error so I can reproduce the error with the same data you are experiencing it with. If that post content is something you are not able to share here in the forums let me know.

You can follow along with the progress on github and please feel free to add any additional details to the issue or this thread if something relevant comes to mind. https://github.com/equalizedigital/accessibility-checker/issues/570