WPIntell

Source evidence

Warning in media library

Media Library Helper — Bulk edit image ALT, caption & description · support · 2024-10-29T13:26:00+00:00

complaintsentiment
mediumseverity
0.86relevance
3replies
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
classweb unresolved
Hi, If I open the admin’s media library, I get the following warning by every image or media: “ Deprecated : WP_List_Table::__get(): The property is_trash is not declared. Getting a dynamic property is deprecated since version 6.4.0! Instead, declare the property on the class. in /home/www/clients/client7884/web16995/web/wp-includes/functions.php on line 6085 “ WP version is 6.6.2 Plugin version is 1.3.0 If I open the following source: \media-library-helper\lib\Admin\Extended_Media_List_Table.php On line 314 there is a condition: if ( current_user_can( ‘edit_post’, $post->ID ) && ! $this->is_trash ) and this causes the warning. Could you please fix it in a future version of the plugin? Regards, Csaba I also am seeing this same warning for each media item in the media list. Otherwise this is a great plugin. Thank you for notifying us of the issue. We are actively investigating the errors and will release an update soon. I can confirm this issue is officially resolved. Thank you. 🙂

Comments

3 shown
Josh Journey 2024-11-12T23:00:00+00:00

I also am seeing this same warning for each media item in the media list. Otherwise this is a great plugin.

cxnmedia 2024-11-13T07:15:00+00:00

Thank you for notifying us of the issue. We are actively investigating the errors and will release an update soon.

Josh Journey 2024-11-13T20:05:00+00:00

I can confirm this issue is officially resolved. Thank you. 🙂