Jairo Ochoa

@nilovelez sí, ese ya no aparece. 🙂

En el caso de los WP MU genero un debug.log por cada sitio porque así puede investigar cada caso de forma independiente.
Tengo esto en el wp-config.php:

define( 'WP_DEBUG', false );
define( 'WP_DEBUG_LOG', false );
define( 'WP_DEBUG_DISPLAY', false );
define( 'SAVEQUERIES', false );

ini_set( 'log_errors', 1 );
ini_set( 'error_log', dirname(__FILE__) . '/wp-content/debug-' .$_SERVER['SERVER_NAME']. '.log' );

Revisando todos los logs es curioso que solo afecta a:

• debug-dominio.com.log
• debug-.log

Es decir, afecta al sitio principal ¿y al no-sitio ? es raro

Hay que tener en cuenta un detalle, Machete no está activado para toda la red, solo lo he activado en algunos sitios.
Voy a activarlo para toda la red para ver si afecta positivamente.

También tenía instalado Machete PowerTools que voy a eliminar para reducir cualquier efecto colateral.

Borré los logs y voy a ver si algo cambia.

Te informo de las novedades.

Saludos!

Hi, yes please close the topic.
I did not have more request from the web admin.
I did suggest them to upgrade to Elite version.
Thanks

Hi,

I think that its free version because there is a CTA in green which says “Go Elite”.

This site was supported by another guy and I guess that probably he did not renewed the license last year, because these fields are filled in other products.
Furthermore the product that I was told to check has some variations with Brand, EAN GTIN with values and other variations in blank. And if I try to write their values, they are not saved.
It’s a bit weird that some variations of the same product have values and another are blank.

Does it makes sense ?

Thanks

Hi,

Current plugin:
Redux Versión 4.3.9

New plugin:
Template Library and Redux Framework Versión 4.3.12.1

Are both the same ?
Administrator have not gave me access to staging yet, so I don’t want to active before been sure that both are the same.

Thanks

Hi,

It occurs in WP-admin.
Site runs WooCommerce and if I enter Products > New Product the site crash.
It’s not a frontend bug.

@roskib we got the 403 when opening the label on the frontend.

If you get the error inside Admin pages, try to uninstall plugin and then reinstall it.
Also you can do a CHMOD of files in your WP installation.

find -type d -exec chmod 755 {} \;
find -type f -exec chmod 644 {} \;

If you do not know how to do it you can ask your hosting provider to restore files permissions.

Regards

Yes, sure!
I will rate it.

Hi @pdosev

Great to know that you’re working on an update of the plugin.
It’s OK to do it as a temporary fix for this issue. I’d understand that it should be the “normal” procedure.
Thanks