No, lo que explico es que he intentado en otras ocasiones cambiar la plantilla, pero cuando lo hago me desestructura las categorías que tengo organizadas, además de eliminar algunas, es decir, no puedo arriesgarme a cambiar la plantilla porque me produce este error que no puedo reparar manualmente. La pregunta ¿Como cambiar la plantilla sin desordenar y eliminar las categorías exixtentes? gracias

Hola, he seguido las instrucciones que me indicó, borre el complemento tagDiv Composer y lo he vuelto a instalar, pero el problema con alloneseo sigue igual

Por otra parte me sigue apareciendo un código en las pantallas del celular, me puede indicar como puedo eliminar esto en globatium.net gracias

Hello, I have this problem when I use the mobile version and AMD, this message appears on the mobile, can someone help me, thanks

Warning: is_readable(): open_basedir restriction in effect. File(/Newspaper/theme.json) is not within the allowed path(s): (/usr/home/globatium.net/:/home/globatium.net/:/usr/home/services/:/usr/share/php74/) in /usr/home/globatium.net/web/wp-includes/class-wp-theme-json-resolver.php on line 433 Warning: is_readable(): open_basedir restriction in effect. File(/Newspaper/theme.json) is not within the allowed path(s): (/usr/home/globatium.net/:/home/globatium.net/:/usr/home/services/:/usr/share/php74/) in /usr/home/globatium.net/web/wp-includes/class-wp-theme-json-resolver.php on line 433

Hi Hugo,

Thanks for reporting this and I’m really sorry that you’re facing this issue.

Our dev team investigated this further and we found that this error is coming from a plugin called “tagDiv Composer” which is pre-installed with the Newspaper theme from tagDiv.

Their plugin is using Vue in development mode and this is causing issues not only with AIOSEO but with any plugin that uses Vue Router. This seems to be a problem with their latest version and downgrading your theme to an older version should fix the issue.

Please reach out to your theme author (tagDiv) here and let them know that their plugin is breaking your site. They should be able to fix this from their end.

In the meanwhile, we are trying to figure out a workaround for this so that it can be avoided in our future releases.

I’d like to assure you that this is not something caused by AIOSEO or something that can be fixed from our end, but it’s definitely affecting our plugin and breaking your site.