Solución página en ...
 
Avisos
Vaciar todo

Solución página en blanco tras actualizar a PrestaShop 1.6

7 Respuestas
3 Usuarios
0 Reactions
954 Visitas
Respuestas: 485
Reputable Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

He actualizado el prestashop 1.6.1.4 y se queda en blanco y si inicio desde el panel administrador si me sale la pagina bien. Me podéis ayudar?

un saludo

URL del sitio: Contenido solo visible a usuarios registrados


 
Respondido : 30/01/2016 11:00 am
Lorena
Respuestas: 1698
Noble Member Moderator
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Hola Pepe,

Si la web carga en blanco en el frontal, esto implica un error 500. Realiza una revisión con nuestro asistente Stephan y mira si te devuelve algún error 500.

Para hacer el análisis con Stephan, accede a tu Área de Cliente https://www.webempresa.com/areacliente.php y pulsa en "Crear Ticket", clica en "Consultar sobre esta cuenta" (escoge la cuenta de hosting que deseas revisar si tienes varios planes) y en la parte inferior en "Revisar cuenta y crear ticket", hará un análisis de la instalación

En ese caso,, si en el informe que te presenta tras la revisión te muestra errores , péganos aquí los errores que te muestre con fecha de hoy.

Un saludo.


 
Respondido : 30/01/2016 11:34 am
Respuestas: 485
Reputable Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

[30-Jan-2016 05:33:02 US/Eastern] PHP Fatal error: Uncaught --> Smarty: Missing template name Smarty: Missing template name <--
[29-Jan-2016 21:30:07 Europe/Berlin] PHP Fatal error: require_once(): Failed opening required '/home/guiatebi/public_html/includes/defines.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/guiatebi/public_html/index.php on line 28
[30-Jan-2016 00:46:10 Europe/Berlin] PHP Fatal error: require_once(): Failed opening required '/home/guiatebi/public_html/includes/defines.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/guiatebi/public_html/index.php on line 28
[30-Jan-2016 04:52:39 Europe/Berlin] PHP Fatal error: require_once(): Failed opening required '/home/guiatebi/public_html/includes/defines.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/guiatebi/public_html/index.php on line 28
[30-Jan-2016 04:52:47 Europe/Berlin] PHP Fatal error: require_once(): Failed opening required '/home/guiatebi/public_html/includes/defines.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/guiatebi/public_html/index.php on line 28


 
Respondido : 30/01/2016 11:40 am
Respuestas: 485
Reputable Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Revisión Permisos incorrectos en ficheros:

Los permisos correctos de ficheros para que su web funcione correctamente son 644. Hemos encontrado los siguientes ficheros que no tenían permisos 644 y los hemos corregido.

/home2/guiatebi/public_html/sherrysur/cache/class_index.php

Revisión Permisos en directorios incorrectos:

Los permisos correctos de directorios para que su web funcione correctamente son 755. Hemos encontrado los siguientes directorios que no tenían permisos 755 y los hemos corregido:

/home2/guiatebi/public_html/sherrysur/cache/cachefs/2
/home2/guiatebi/public_html/sherrysur/cache/cachefs/9
/home2/guiatebi/public_html/sherrysur/cache/cachefs/0
/home2/guiatebi/public_html/sherrysur/cache/cachefs/b
/home2/guiatebi/public_html/sherrysur/cache/cachefs/a
/home2/guiatebi/public_html/sherrysur/cache/cachefs/f
/home2/guiatebi/public_html/sherrysur/cache/cachefs/6
/home2/guiatebi/public_html/sherrysur/cache/cachefs/7
/home2/guiatebi/public_html/sherrysur/cache/cachefs/4
/home2/guiatebi/public_html/sherrysur/cache/cachefs/8
/home2/guiatebi/public_html/sherrysur/cache/cachefs/5
/home2/guiatebi/public_html/sherrysur/cache/cachefs/1
/home2/guiatebi/public_html/sherrysur/cache/cachefs/3
/home2/guiatebi/public_html/sherrysur/cache/cachefs/e
/home2/guiatebi/public_html/sherrysur/cache/cachefs/c
/home2/guiatebi/public_html/sherrysur/cache/cachefs/d


 
Respondido : 30/01/2016 11:42 am
Lorena
Respuestas: 1698
Noble Member Moderator
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Hola Pepe,

Parece que el problema puede venir por la caché, comprueba en el fichero de configuración de la web Contenido solo visible a usuarios registrados tienes el siguiente código:

define('_PS_CACHE_ENABLED_', '1');

y cámbialo por

define('_PS_CACHE_ENABLED_', '0');

Luego, limpia la caché desde la administración de la web y comprueba nuevamente.

Un saludo.


 
Respondido : 30/01/2016 11:50 am
Respuestas: 485
Reputable Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

sigue igual despues de cambiralo


 
Respondido : 30/01/2016 11:57 am
Johnny Heredia Montiel
Respuestas: 20127
Illustrious Member Moderator
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Hola,

Verifico los siguientes advertencias:

30-Jan-2016 16:40:33 Europe/Berlin] PHP Warning: Module 'suhosin' already loaded in Unknown on line 0
[30-Jan-2016 16:40:33 Europe/Berlin] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20121212/imagick.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20121212/imagick.so: cannot open shared object file: No such file or directory in Unknown on line 0
[30-Jan-2016 10:40:33 US/Eastern] PHP Fatal error: Uncaught --> Smarty: Missing template name <--
thrown in /home/guiatebi/public_html/sherrysur/tools/smarty/sysplugins/smarty_internal_template.php on line 678
[30-Jan-2016 16:40:33 Europe/Berlin] PHP Warning: Module 'suhosin' already loaded in Unknown on line 0
[30-Jan-2016 16:40:33 Europe/Berlin] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20121212/imagick.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20121212/imagick.so: cannot open shared object file: No such file or directory in Unknown on line 0

Envía un ticket y consulta si hay que aplicar cambios sobre la cuenta.


 
Respondido : 30/01/2016 4:45 pm