esferic-better-thingsS

Problem:
The client, Sven, reported an issue with excessive resource usage in the database and a problem with the translation of author meta descriptions in a Divi theme WordPress site. The author's meta description was not translating correctly, although the author's title was.
Solution:
We performed several troubleshooting steps. For the performance issue, we suggested:
1. Visit the WPML String Translation page at WPML String Translation
2. Select and delete a significant number of strings to see if this resolves the performance issue.
3. Deactivate the caching plugin as strings can only be deleted after the cache is cleared.
For the issue with the author's meta description not translating, we provided a workaround involving editing a PHP file in the Divi theme:
- Create a backup of the entire site
- Navigate to ...wp-content/themes/Divi/includes/builder/feature/dynamic-content.php
- Locate line 1026 and replace:

if ( $post ) {
	$author = get_userdata( $post->post_author );
} elseif ( is_author() ) {

with:

if ( $post ) {
	$author = get_userdata( $post->post_author );
	if ( class_exists('Sitepress') ) { 
		$author->description = get_the_author_meta('description', $author->ID);
	}
} elseif ( is_author() ) {

- Save the changes and check the results.

If these solutions do not resolve your issues or seem outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Spanish Support Forum.

Problem:
El cliente enfrenta un error 500 'Internal Server Error' al intentar abrir 'Traducción de cadenas' en WPML, además de picos altos en el uso de recursos de la base de datos y CPU. La tabla 'wp_icl_string_translations' es muy grande, lo que contribuye al problema.
Solution:
1. Realizar un downgrade de PHP a la versión 8.1 o 8.2 y seguir los pasos de troubleshooting de WPML disponibles en esta guía.
2. Crear un sitio staging para realizar pruebas sin afectar el sitio en producción, utilizando el plugin WP Staging.
3. Solicitar al hosting que ajuste los siguientes parámetros en el servidor de base de datos y reinicie MySQL:
- wait_timeout = 300
- max_allowed_packet = 512M
- innodb_log_file_size = 256M
4. Verificar si el problema persiste en el sitio staging y en producción.

Si la solución proporcionada no resuelve el problema o parece irrelevante debido a que está desactualizada o no se ajusta a tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Para asistencia adicional, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.