Additionally, 2.1.9 is also causing another critical/fatal error
PHP Fatal error: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, null given in /www/xxx/wp-content/plugins/search-exclude/lib/controllers/class-backend.php:180
Stack trace:
#0 /www/xxx/wp-content/plugins/search-exclude/lib/controllers/class-backend.php(180): array_diff(NULL, Array)
#1 /www/xxx/wp-content/plugins/search-exclude/lib/controllers/class-backend.php(166): QuadLayers\QLSE\Controllers\Backend->save_post_ids_to_search_exclude(Array, false)
#2 /www/xxx/wp-content/plugins/search-exclude/lib/controllers/class-backend.php(308): QuadLayers\QLSE\Controllers\Backend->save_post_id_to_search_exclude(51389, false)
#3 /www/xxx/wp-includes/class-wp-hook.php(326): QuadLayers\QLSE\Controllers\Backend->post_save(51389)
Having the same problem. Also the settings page is just blank.
@krypsin @wundawoman
We want to inform you that we’ve released a new version 2.2.0 of Search Exclude to address the issues that have been reported. We need you to update and give us your feedback so we can adjust any issues that may persist.
Best regards, Quadlayers Support Team.
Hi there
I’ve updated but unfortunately still can’t see the settings page, hidden pages are still visible in the search archives and random words trigger a ‘content is restricted error’.
@wundawoman
Hi mate,
Most users have confirmed that the issue was resolved with version 2.2.0. However, since you’re still experiencing the problem on your specific WordPress installation, we recommend submitting a support ticket through the following link: https://urbiport1.atlassian.net/servicedesk/customer/portal/2.
This will allow us to investigate further. It’s possible that the issue is related to a particular configuration in your theme, plugins, or WordPress setup.
Best regards, Quadlayers Support Team.
The problem still exists on 2.2.0.
I think this may be due to the priority number on the pre_get_posts action.
Since it is using the default number of 10, this is also used by other plugins.
If the priority was changed to a higher number, it would fix the issue by preventing other plugins overwriting at a lower priority.
I have reported a bug to a separate plugin here: https://ww.wp.xz.cn/support/topic/post__not_in-hook-is-overriding-other-plugins/#new-topic-0
They override post__not_in which causes the issue.
However, this issue can still be fixed by Search Exclude simply by using a higher number for the priority on the hook so it will run after other plugins.
@krypsin Most users have confirmed that the issue was resolved with version 2.2.0. However, since you’re still experiencing the problem on your specific WordPress installation, we recommend submitting a support ticket through the following link: https://urbiport1.atlassian.net/servicedesk/customer/portal/2.
