• Resolved arcstone

    (@arcstone)


    Not sure what was causing the issue, but it seems to be related to the Search Exclude plugin, because when I disabled it (both on a dev and prod site) the issue went away. But like the title mentions, if I went to a custom post type index page (like: /wp-admin/edit.php?post_type=resource), only one post was showing up, and some of the interactive links on the page weren’t working either (“screen options” button at the top). I’d noticed that you had made a plugin update 2hrs before, so thought maybe it was something in that latest update.

    Just wanted to let you know, thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support jmatiasmastro

    (@jmatiasmastro)

    @arcstone Hi mate,

    Thank you for bringing this to our attention!

    In order to better understand the issue you’re experiencing, could you please provide us with a screencast showing the steps to replicate the problem? Additionally, it would be helpful if you could share details about the environment where our plugin is running (e.g., WordPress version, theme, other active plugins).

    This information will allow us to investigate and provide a more effective solution.

    You can use the tool https://www.loom.com to easily record and share the screencast with us.

    Best regards, Quadlayers Support Team.

    I do have the same exact problem, when accessing the podcast episodes (serioulsly simple podcast plugin).

    WordPress versión 6.7.1 Theme: GeneratePress (versión 3.5.1) Search Exclude (versión 2.1.8) PHP versión 8.3.14

    If I deactivate your plugin, the error and warning dissappear.

    Here is the warning and error messages:

    Warning: Undefined array key “podcast” in wp-content/plugins/search-exclude/lib/controllers/class-backend.php on line 186

    Warning: Trying to access array offset on null in wp-content/plugins/search-exclude/lib/controllers/class-backend.php on line 186

    Fatal error: Uncaught TypeError: array_search(): Argument #2 ($haystack) must be of type array, null given in wp-content/plugins/search-exclude/lib/controllers/class-backend.php:188 Stack trace: #0 wp-content/plugins/search-exclude/lib/controllers/class-backend.php(188): array_search(11579, NULL) #1 wp-content/plugins/search-exclude/lib/controllers/class-backend.php(284): QuadLayers\QLSE\Controllers\Backend->is_excluded(11579) #2 wp-includes/class-wp-hook.php(324): QuadLayers\QLSE\Controllers\Backend->add_column_value(‘search_exclude’, 11579) #3 wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) #4 wp-includes/plugin.php(517): WP_Hook->do_action(Array) #5 wp-admin/includes/class-wp-posts-list-table.php(1385): do_action(‘manage_posts_cu…’, ‘search_exclude’, 11579) #6 wp-admin/includes/class-wp-list-table.php(1802): WP_Posts_List_Table->column_default(Object(WP_Post), ‘search_exclude’) #7 wp-admin/includes/class-wp-posts-list-table.php(1437): WP_List_Table->single_row_columns(Object(WP_Post)) #8 wp-admin/includes/class-wp-posts-list-table.php(839): WP_Posts_List_Table->single_row(Object(WP_Post), 0) #9 wp-admin/includes/class-wp-posts-list-table.php(815): WP_Posts_List_Table->_display_rows(Array, 0) #10 wp-admin/includes/class-wp-list-table.php(1712): WP_Posts_List_Table->display_rows() #11 wp-admin/includes/class-wp-list-table.php(1639): WP_List_Table->display_rows_or_placeholder() #12 /wp-admin/edit.php(503): WP_List_Table->display() #13 {main} thrown in wp-content/plugins/search-exclude/lib/controllers/class-backend.php on line 188

    • This reply was modified 3 months, 1 week ago by inakipsiko.

    I get the same problem, only the first field in the first row of CPT index pages are shown, I’m using Secure Custom Posts

    Plugin Support jmatiasmastro

    (@jmatiasmastro)

    @arcstone @nobbiexxx @inakipsiko

    Hi guys,

    We want to inform you that a new version of Search Exclude (v2.1.9) has been released to address several issues reported after the update to WordPress 6.7.X. Please update to the latest version directly from your WordPress admin dashboard and check if it resolves the issue on your site.

    If the issue persists in your specific case, feel free to contact us directly via our Facebook page at https://www.facebook.com/quadlayers. This will allow us to provide tailored assistance for your situation.

    Best regards, Quadlayers Support Team.

    As far as I am concerned: problem solved. Thanks!

    Plugin Support jmatiasmastro

    (@jmatiasmastro)

    @inakipsiko Thanks for updating your ticket!

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.