Resolved "search engine indexing" is set to off and I can't turn it on

[mr-wolf]

A site that was recently migrated to one of our servers now has "search engine indexing" set to off.
The client also told me that indexing wasn't possible anymore (I don't know how they know this, yet).

I can press "enable" and then I will get an error message that blog_public can't be updated.
I checked that value in the "wp_options" table (it in fact does not have that wp_ prefix anymore)
That value is already set to 1

Is this the only flag it is trying to change?
Why does it give an error message if it's already 1?
Why can't robots have access to that site?


To be certain the extension has all the access it needs I did a refresh of the WP-setttings.
This setting is not giving a problem on any other site.
Not on that server or on other ones I manage with Plesk.

I am able to set and unset debugging options using that same extension.

 

[mr-wolf]

I decided to set "blog_public" to 0 and then "enable" search engine indexing.
I will now try and find out if that's enough to fix the underlying issue that it's not being searched....

BTW... If this is the way to fix it, then it's a bit silly. The script should be doing that thing extra anyhow if "blog_public" is already 1

 

[Aleksander Prikhozhdenko]

Hello Mr-Wolf,

I was not able to reproduce the issue on my environment. Could you please provide me with credentials?

 

[mr-wolf]

Hello Mr-Wolf,

I was not able to reproduce the issue on my environment. Could you please provide me with credentials?

After I fixed mine it now isn't possible to reproduce it anymore.

Somehow it was in a state that it saw search indexing as disabled although "blog_public" is set to 1
What's in the code that will invoke this error message?

 

[mr-wolf]

I'm setting this thread as resolved as the issue itself is fixed and I haven't seen this anymore on any other site.

If someone else experiences the same and sees this thread he can do the same (set blog_public to 0 using phpmyadmin).
Do add a post to this thread, if so.

 

[igorneumann]

I'm setting this thread as resolved as the issue itself is fixed and I haven't seen this anymore on any other site.

If someone else experiences the same and sees this thread he can do the same (set blog_public to 0 using phpmyadmin).
Do add a post to this thread, if so.

I run intto the same problem and managed to fix it... so I kinda know how to reproduce it.

- Just replicate a wordpress website with this feature disable into a different existing one that have this enable... BAM, it gets disabled and you cant enable it.

To fix it: Enable search engine index before replicating it again.

 

[TomBoB]

Just had the exact same issue. Wordpress site. Indexing enabled. Cloned it into a staging site (didn't use default suggestion subdomain) as clients wanted to test a few updates and changes.
Created the staging site just fine.
However for reasons unknown, after the cloning, the original site its indexing showed as turned off in Plesk, and couldn't be turned on. Causing above error.
Checking the database of original site, the value was correctly set to 1. As per suggestion above, changed it to 0. Afterwards turned the slider back to indexing on.
Appears under certain circumstances Plesk can't read the actual value, and then attempts to change it when it is correct already. Or possibly doesn't check that value at all and just goes ahead wanting to change it and can't.
Bug still exists.

 

[Kaspar@Plesk]

I tried to replicate the issue, but wasn't able to. For me when cloning a site the original site keeps it indexing settings (whether that enabled or disabled originally). Are there any related errors logged in the panel.log?

 

[TomBoB]

stderr:
Error: Could not update option 'blog_public'.

[2024-07-04 16:31:21.635] 2707567:6686b2394a240 ERR [extension/wp-toolkit] An error occurred while executing WP-CLI command for instance: WordPress installation #2 ('https://clientdomain.com'). Error: Could not update option 'blog_public'.

[2024-07-04 16:31:21.674] 2707567:6686b2394a240 ERR [extension/wp-toolkit] Failed to toggle search indexing: Error: Could not update option 'blog_public'.

[2024-07-04 16:32:02.289] 2707567:6686b262177b4 ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/filemng' 'ftpaccessuser' 'exec' '/var/www/vhosts/clientdomain.com/httpdocs' 'timeout' '300' '/opt/plesk/php/8.1/bin/php' '-d' 'safe_mode=off' '-d' 'display_errors=on' '-d' 'opcache.enable_cli=off' '-d' 'open_basedir=' '-d' 'error_reporting=341' '-d' 'max_execution_time=300' '-c' '/var/www/vhosts/system/clientdomain.com/etc/php.ini' '/usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php' '--path=/var/www/vhosts/clientdomain.com/httpdocs' '--no-color' 'option' 'update' 'blog_public'] with exit code [1]
[2024-07-04 16:32:02.289] 2707567:6686b262177b4 ERR [panel] '/usr/local/psa/admin/bin/filemng' 'ftpaccessuser' 'exec' '/var/www/vhosts/clientdomain.com/httpdocs' 'timeout' '300' '/opt/plesk/php/8.1/bin/php' '-d' 'safe_mode=off' '-d' 'display_errors=on' '-d' 'opcache.enable_cli=off' '-d' 'open_basedir=' '-d' 'error_reporting=341' '-d' 'max_execution_time=300' '-c' '/var/www/vhosts/system/clientdomain.com/etc/php.ini' '/usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php' '--path=/var/www/vhosts/clientdomain.com/httpdocs' '--no-color' 'option' 'update' 'blog_public' failed with code 1.

stdout:


stderr:
Error: Could not update option 'blog_public'.

[2024-07-04 16:32:02.371] 2707567:6686b262177b4 ERR [extension/wp-toolkit] An error occurred while executing WP-CLI command for instance: WordPress installation #2 ('https://clientdomain.com'). Error: Could not update option 'blog_public'.

[2024-07-04 16:32:02.390] 2707567:6686b262177b4 ERR [extension/wp-toolkit] Failed to toggle search indexing: Error: Could not update option 'blog_public'.

[2024-07-04 16:45:13.631] 2731994:6686b5799a25b ERR [panel] Call to a member function getParam() on null
[2024-07-04 16:45:24.582] 2752999:6686b5845cadc ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/filemng' 'ftpaccessuser' 'exec' '/var/www/vhosts/clientdomain.com/httpdocs' 'timeout' '300' '/opt/plesk/php/8.1/bin/php' '-d' 'safe_mode=off' '-d' 'display_errors=on' '-d' 'opcache.enable_cli=off' '-d' 'open_basedir=' '-d' 'error_reporting=341' '-d' 'max_execution_time=300' '-c' '/var/www/vhosts/system/clientdomain.com/etc/php.ini' '/usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php' '--path=/var/www/vhosts/clientdomain.com/httpdocs' '--no-color' 'option' 'update' 'blog_public'] with exit code [1]
[2024-07-04 16:45:24.583] 2752999:6686b5845cadc ERR [panel] '/usr/local/psa/admin/bin/filemng' 'ftpaccessuser' 'exec' '/var/www/vhosts/clientdomain.com/httpdocs' 'timeout' '300' '/opt/plesk/php/8.1/bin/php' '-d' 'safe_mode=off' '-d' 'display_errors=on' '-d' 'opcache.enable_cli=off' '-d' 'open_basedir=' '-d' 'error_reporting=341' '-d' 'max_execution_time=300' '-c' '/var/www/vhosts/system/clientdomain.com/etc/php.ini' '/usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php' '--path=/var/www/vhosts/clientdomain.com/httpdocs' '--no-color' 'option' 'update' 'blog_public' failed with code 1.

stdout:

 

[Kaspar@Plesk]

Thank you. That's helpful. Does the website use Redis by any chance?