WPIntell

Source evidence

Error message / Deprecated: mb_substr():

Tag Groups is the Advanced Way to Display Your Taxonomy Terms · support · 2023-11-23T13:52:00+00:00

mixedsentiment
highseverity
0.95relevance
5replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 23 rows with source links

17.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Thomas resolved
Hi Team, For your information, when I use the following shortcode: [tag_groups_tag_list column_count=1 hide_empty_content=1 include=2,3,4,5,8] I get this error line (four times): Deprecated : mb_substr(): Passing null to parameter #1 ($string) of type string is deprecated in /home/xxxx/xxxx.fr/modules/tag-groups/include/helpers/class.shortcode_common.php on line 77 WordPress : 6.4.1 PHP 8.1 Is something wrong with my shortcode settings? This topic was modified 2 years, 6 months ago by Thomas . This topic was modified 2 years, 6 months ago by Thomas . This topic was modified 2 years, 6 months ago by Thomas . Hi @thomhsb Thanks for using Tag Groups. You can safely ignore and hide deprecated errors. They are only advice for developers. We’ll remove this in the next version of the plugin. Hi Steve, Of course, I hide them and ignore them, but my server records these errors in the logs and it’s just a lot of lines all the time 😉 Thanks in advance for the correction. “ We’ll remove this in the next version of the plugin. “ Hello, How are you? Is there really a next version in the pipeline? Yes, there is. You can safely ignore “Deprecated” messages. From a security point of view, yes. But I’m not ignoring the 3,000 lines that clutter up the log file every month, it’s annoying. So, I took care of it myself with a simple ” if(!empty($value)){} “ And I should have done it from the start after all. Thanks anyway. This reply was modified 2 years, 2 months ago by Thomas .

Comments

5 shown
Steve Burge 2023-11-27T13:07:00+00:00

Hi @thomhsb Thanks for using Tag Groups. You can safely ignore and hide deprecated errors. They are only advice for developers. We’ll remove this in the next version of the plugin.

Thomas 2023-11-27T17:44:00+00:00

Hi Steve, Of course, I hide them and ignore them, but my server records these errors in the logs and it’s just a lot of lines all the time 😉 Thanks in advance for the correction.

Thomas 2024-03-26T22:29:00+00:00

“ We’ll remove this in the next version of the plugin. “ Hello, How are you? Is there really a next version in the pipeline?

Steve Burge 2024-03-27T14:19:00+00:00

Yes, there is. You can safely ignore “Deprecated” messages.

Thomas 2024-03-27T16:43:00+00:00

From a security point of view, yes. But I’m not ignoring the 3,000 lines that clutter up the log file every month, it’s annoying. So, I took care of it myself with a simple ” if(!empty($value)){} “ And I should have done it from the start after all. Thanks anyway. This reply was modified 2 years, 2 months ago by Thomas .