• Hi guys

    I am still on version 2.1.7 as the last few updates have caused critical errors. In fact the 2.1.7 version doesn’t allow me to view search excludes settings page anymore.

    Also it seems that pages I excluded in the past are now visible in search results and the search exclude meta box that used to appear in the page editor is no longer available, including in the screen options section.

    I’m now unsure when the last working version of the plugin was as i haven’t been monitoring.

    Hoping you can help 🤞

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

    (@jmatiasmastro)

    @noelawill Hi mate,

    Please update to the latest version of the plugin (2.3.0), as it addresses issues present in some previous versions. This update should resolve the problems you’re experiencing.

    If you encounter any critical errors after updating, please share your PHP error log details so we can assist you further. If you’re unsure where to find the error logs, your hosting provider can guide you.

    Best regards, Quadlayers Support Team.

    Thread Starter noelawill

    (@noelawill)

    Sorry if i didn’t explain myself properly, it is V2.3.0 that is causing the critical error which is why i had to rollback to 2.1.7

    As it is now with 2.1.7 I cannot access the settings page

    • This reply was modified 1 year, 4 months ago by noelawill.
    Plugin Support jmatiasmastro

    (@jmatiasmastro)

    @noelawill Please share your PHP error log details PHP stores error logs in /var/log/apache2 if PHP is an apache2 module. Shared hosts are often storing log files in your root directory subfolder. If you’re using cPanel, the master log file you’re probably looking for is stored (by default) at: /usr/local/apache/logs/error_log If you’re not sure where to find PHP error logs please contact your hosting provider.

    Best regards.

    Thread Starter noelawill

    (@noelawill)

    this is all i have

    [28-Dec-2024 05:08:42 UTC] PHP Fatal error: Uncaught Error: Undefined constant “ABSPATH” in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-settings.php:33
    Stack trace: 0 {main}

    thrown in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-settings.php on line 33
    [28-Dec-2024 19:27:46 UTC] PHP Fatal error: Uncaught Error: Undefined constant “ABSPATH” in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-settings.php:33
    Stack trace: 0 {main}

    thrown in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-settings.php on line 33
    [29-Dec-2024 21:24:35 UTC] PHP Fatal error: Uncaught Error: Undefined constant “ABSPATH” in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-settings.php:33
    Stack trace: 0 {main}

    thrown in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-settings.php on line 33
    [09-Jan-2025 16:39:26 UTC] PHP Fatal error: Uncaught Error: Call to undefined function __() in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-admin/includes/file.php:16
    Stack trace: 0 {main}

    thrown in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-admin/includes/file.php on line 16
    [10-Jan-2025 09:50:09 UTC] PHP Fatal error: Uncaught Error: Call to undefined function __() in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-admin/includes/file.php:16
    Stack trace: 0 {main}

    thrown in /var/www/54480ed9-849e-467c-b9f8-ee2da6771288/public_html/wp-admin/includes/file.php on line 16

    Plugin Support jmatiasmastro

    (@jmatiasmastro)

    @noelawill

    Hello mate,

    Thank you for sharing the error log with us. To assist you better, could you please also provide the following information?

    • The PHP version you are using.
    • The WordPress version installed on your site.
    • If you are using Jetpack, the version of Jetpack currently active.

      Best regards, Quadlayers Support Team.
    Thread Starter noelawill

    (@noelawill)

    8. 3

    6.7.1

    I don’t use jetpack

    • This reply was modified 1 year, 4 months ago by noelawill.
    Thread Starter noelawill

    (@noelawill)

    is this thread still open?

    Thread Starter noelawill

    (@noelawill)

    Hello?

    Plugin Support jmatiasmastro

    (@jmatiasmastro)

    @noelawill Hi mate, what version of our plugin do you currently have installed? Sorry for the delay.

    Best regards.

    Thread Starter noelawill

    (@noelawill)

    As stated four weeks ago

    8.3

    6.7.1

    I don’t use jetpack

    Plugin Support jmatiasmastro

    (@jmatiasmastro)

    @noelawill We are referring to the version of our plugin, search exclude.

    Thread Starter noelawill

    (@noelawill)

    As stated in the very first comment, I haven’t been able to get past 2.1.7

    Thread Starter noelawill

    (@noelawill)

    Are you ignoring me specifically or do you eventually ignore every support ticket that comes through?

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Critical error after recent update’ is closed to new replies.