Anubis2702 Posted November 8, 2016 Share Posted November 8, 2016 Hello, I installed Prestashop 1,7 and I can't use the backend because the "WELCOME TO YOUR SHOP!" popup wont close, I hit start/close/later buttons and nothing happens. Could this be caused by some files permissions? Link to comment Share on other sites More sharing options...
vekia Posted November 8, 2016 Share Posted November 8, 2016 To find issue it will be necessary to: go to shop back office turn on browser console (in chrome ctrl+shift+j) clear it refresh page watch the console output copy it and paste here (if errors) Link to comment Share on other sites More sharing options...
Anubis2702 Posted November 8, 2016 Author Share Posted November 8, 2016 No errors Link to comment Share on other sites More sharing options...
vekia Posted November 8, 2016 Share Posted November 8, 2016 and if you try to close it? does it spawn some errors then? Link to comment Share on other sites More sharing options...
yourrfriend Posted November 8, 2016 Share Posted November 8, 2016 (edited) I got same error. After doing ctrl+shift+j error message was siteurl/modules/welcome/welcome-api.php 500 (Internal Server Error)send @ jquery-1.11.0.min.js:4ajax @ jquery-1.11.0.min.js:4save @ module.js:434setShutDown @ module.js:525(anonymous function) @ index.php?controller=AdminDashboard&token=cccae34…:906dispatch @ jquery-1.11.0.min.js:3r.handle @ jquery-1.11.0.min.js:3 And from error logs Edited November 8, 2016 by yourrfriend (see edit history) Link to comment Share on other sites More sharing options...
vekia Posted November 8, 2016 Share Posted November 8, 2016 hello, two things to check: verify privileges to file: /modules/welcome/welcome-api.php - it must be accesible from browser error reporting file that is available on your host Link to comment Share on other sites More sharing options...
yourrfriend Posted November 8, 2016 Share Posted November 8, 2016 /modules/welcome/welcome-api.php has 777 permission i got the messages from error reporting 2016/11/08 14:40:09 [error] 7832#7832: *3862 FastCGI sent in stderr: "PHP message: PHP Warning: require_once(SITE-ROOT/modules/welcome/../../init.php): failed to open stream: No such file or directory in SITE-ROOT/modules/welcome/welcome-api.php on line 28 2016/11/08 14:40:18 [error] 7833#7833: *3869 FastCGI sent in stderr: "PHP message: PHP Warning: require_once(SITE-ROOT/modules/welcome/../../init.php): failed to open stream: No such file or directory in SITE-ROOT/modules/welcome/welcome-api.php on line 28 Link to comment Share on other sites More sharing options...
Anubis2702 Posted November 8, 2016 Author Share Posted November 8, 2016 Thanks, changing the file: /modules/welcome/welcome-api.php permissions to 0644 worked for me. Dont know why all my files are 0666 and the hosting is blocking them. I think I'll have more problems because of this, how do I change the permissions of all files on a shared server without ssh? 1 Link to comment Share on other sites More sharing options...
vekia Posted November 8, 2016 Share Posted November 8, 2016 /modules/welcome/welcome-api.php has 777 permission 777 are not always okay, some hostings (like aruba.it for example, and many others) blocks possibility to run php scripts if they are with chmods 777 644 is the proper one Link to comment Share on other sites More sharing options...
vekia Posted November 8, 2016 Share Posted November 8, 2016 Thanks, changing the file: /modules/welcome/welcome-api.php permissions to 0644 worked for me. Dont know why all my files are 0666 and the hosting is blocking them. I think I'll have more problems because of this, how do I change the permissions of all files on a shared server without ssh? it's for security purposes. There is no universal chmods for files - its because each hoster can use different security stuff, so in effect files with 777 / 666 permissions cant be executed. I know many hosts like that, for example aruba - they accepts only 644 for files and 755 for directories Link to comment Share on other sites More sharing options...
w3bsolutions Posted November 8, 2016 Share Posted November 8, 2016 I also experienced the problem with many files having 666 permissions after extracting the PS 1.7 zip file on the server and this was causing many errors. I had to change the perms via ssh to 644 and everything started working correctly. 1 Link to comment Share on other sites More sharing options...
marcelosteles Posted January 12, 2017 Share Posted January 12, 2017 I also experienced the problem with many files having 666 permissions after extracting the PS 1.7 zip file on the server and this was causing many errors. I had to change the perms via ssh to 644 and everything started working correctly. Hola, actualmente he instalado prestashop 1.7 en mi hosting y he tenido múltiples problemas, tal como el que publicaron aquí. Entre ellos, no poder hacer login en el backend, no poder entrar a los módulos instalados. Estimo que todos son derivados de permisos, ya que instalándolo localmente no me da ninguno problema. La solución sería cambiar masivamente los permisos de directorios y archivos a 644? Link to comment Share on other sites More sharing options...
w3bsolutions Posted January 16, 2017 Share Posted January 16, 2017 Hola, actualmente he instalado prestashop 1.7 en mi hosting y he tenido múltiples problemas, tal como el que publicaron aquí. Entre ellos, no poder hacer login en el backend, no poder entrar a los módulos instalados. Estimo que todos son derivados de permisos, ya que instalándolo localmente no me da ninguno problema. La solución sería cambiar masivamente los permisos de directorios y archivos a 644? Lo primero sería ver si la consola de Firebug en Firefox (por ejemplo) lanza algún error, un error 500 de algún fichero podría estar relacionado con permisos incorrectos. Si da error y dicho fichero no tiene permisos 644 podría haber más ficheros con permisos incorrectos, con lo cual lo primero que habría que hacer sería cambiar los permisos masivamente para descartar que este sea el origen del problema. Link to comment Share on other sites More sharing options...
prestafreak1 Posted May 13, 2017 Share Posted May 13, 2017 (edited) To find issue it will be necessary to: go to shop back office turn on browser console (in chrome ctrl+shift+j) clear it refresh page watch the console output copy it and paste here (if errors) I'm having the same issue and I'm getting this error in the console: VM605:1 POST http://tiarstudio.ro/modules/welcome/welcome-api.php 403 (Forbidden) All my files in the /modules directory have 0777 permission and I did tried to change the welcome-api.php permission to 0644 but this didn't change anything. Should I try to change all the file permission to 0644? If yes what files should be affected by this permission change? Edited May 13, 2017 by prestafreak1 (see edit history) Link to comment Share on other sites More sharing options...
adminsellout Posted June 25, 2017 Share Posted June 25, 2017 Hi! POST http://sellout.com.ar/modules/welcome/welcome-api.php 500 (Internal Server Error) send @ jquery-1.11.0.min.js:4 ajax @ jquery-1.11.0.min.js:4 save @ module.js:438 setShutDown @ module.js:529 (anonymous) @ index.php?controller=AdminDashboard&token=2eaa4ae…:930 dispatch @ jquery-1.11.0.min.js:3 r.handle @ jquery-1.11.0.min.js:3jquery-1.11.0.min.js:4 POST http://sellout.com.ar/modules/welcome/welcome-api.php 500 (Internal Server Error) send @ jquery-1.11.0.min.js:4 ajax @ jquery-1.11.0.min.js:4 save @ module.js:438 setShutDown @ module.js:529 (anonymous) @ index.php?controller=AdminDashboard&token=2eaa4ae…:930 dispatch @ jquery-1.11.0.min.js:3 r.handle @ jquery-1.11.0.min.js:3 Link to comment Share on other sites More sharing options...
Marco M. Posted July 21, 2017 Share Posted July 21, 2017 (edited) Hello, I've the same problem: the welcome popup does't close. The browser console shows: "POST ... /modules/welcome/welcome-api.php 500 Internal Server Error". I tried to set "welcome-api.php" file permissions to 777, but the result not change.I'm on the PrestaShop 1.7.1.2, local webserver (XAMPP for Linux 5.6.19).Thank's. -- Update: now it works. Edited July 21, 2017 by Marco M. (see edit history) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now