Subodh Rajpopat

This error is suggesting that wp_kses() function doesn’t exist, which is a core WordPress function that is used to filter text content and strips out disallowed HTML.

One reason could be a custom db.php drop-in file in the wp-content directory that could be trying to directly access the wp_kses() function before WordPress is loaded. It’s possible that this file was introduced by a plugin and wasn’t removed on deactivation. Can you try temporarily removing/renaming this file and testing your admin access? This will disable the database without deleting it.

Another reason could be that the core files are corrupted. Updating WordPress can replace the missing files and resolve the issue. You can also try re-uploading the core WordPress files (except for /wp-content/ and wp-config.php).

You could try the following steps to resolve this issue:

• Please check your permalink settings. In your dashboard, go to Settings > Permalinks and click on Save Changes without making any changes. This will refresh the rewrite rules and often resolves these 404 errors.
• Please confirm that your page is in Published state and not in the trash.
• I can see from your site link that you are using HTML blocks, make sure it is not set as reusable, since this causes the same content to appear on multiple pages.
• Also have you tried clearing your browser cache?

The code that was added in the config file, define(‘WP_ALLOW_REPAIR’, true); gives you access to the database repair tool at your website’s link: https://anisacolombia.org/wp-admin/maint/repair.php.

After the repair was run, WordPress report stated that there was a problem with the h5nvo_options table, and the number of rows changed from 293 to 290.

This means that 3 of those rows were lost during repair. There are a few steps you can follow:

1. Manually inspect your h5nvo_options table. Verify the table structure and look for any issues.
2. Please create a backup of the table if not already done.
3. Use Your Hosting Control Panel’s Database Repair Tool and look for the “Repair Database” option. It might be WHM (WebHost Manager) or cPanel.
4. The Database Repair Tool will try to repair any of your corrupted tables, like h5nvo_options.
5. Check for any error messages and if the site is loading without giving any errors, and check for the missing data again. If you know your missing options, insert them back into the DB.
6. Finally please make sure to remove the line define('WP_ALLOW_REPAIR', true); when it is not needed.
7. To avoid any problems like this in the future, you can try to have regular backups of data and use plugins like WP-Optimize to regularly clean and optimize your database.

Yes, WordPress version update to 6.6.2 is generally recommended, it can fix unexpected issues like this one. The earlier WordPress 6.x versions might not be fully compatible with PHP 8.0. The new version also includes updates and bug fixes in the Gutenberg block editor.

If the issue still persists, you can try to use the “Attempt Block Recovery” option to fix the blocks that show an error.

You’re welcome! I’m glad the tagline is now displaying in your new theme!
Feel free to explore more themes, you can find different levels of customization other than control over displaying the tagline.

To set the site tagline, you are at the correct place: Appearance -> Customize -> Site Identity.

However, there should also be an option below the input, to choose whether to display the Site Title and Tagline. If this is not the case in your theme, then it is possible that your theme currently doesn’t support displaying it.

Simple solution to this problem without jumping into the code: Can you try switching to another theme that supports it, and see if the tagline appears there? This will confirm if it’s a theme-related issue.

Reference Image:

If the theme change isn’t persisting, it could be because of plugin conflicts that override the theme settings. You can try deactivating the plugins to see which plugin might have conflicts with your theme.

If this doesn’t work, you can try these fixes:

1. Verify that your user role has the correct capabilities. The Administrator role has the switch_themes capability which should be present here.
2. Inspect your wp_options table and search for these option_name values: template and stylesheet. The option_value for these should match the folder name of your new theme when activated. You can try to update these values and see if the new theme activates.
3. Check if your host uses server-side caching. In their control panel, you can try to temporarily disable caching, and also clear your Browser cache.