Jump to content

Prestashop 1.7 - Only log in to back office if debug mode is on


Recommended Posts

Every time I try to log into the back office it accepts my password and says it is redirecting to the dashboard, but it just shows the log in page again. Only way I can get in is by turning debug mode on.

 

I have done everything I can think of (clearing all cache and cookies etc)

 

Any Ideas

 

 

Link to comment
Share on other sites

  • 3 weeks later...

Try one thing:

 

1. put in your browser URL to your front office and push INTRO. Wait until load fully

2. Put in your browser URL to your BO puch INTRO and introduce your credentials. Try to enter.

 

 

I hope you solve your issue with this steps.

 

Best regards!

Link to comment
Share on other sites

I have the exact same issue, fresh install ( through Softaculous).

I can only access BO when I enable debug. Otherwise the login page just refreshes.

 

LieBM's solution does work for us.

 

Update: This problem only seems to happen on installations done through Softaculous as it renames the admin folder. Will report this to the Softacuolus team...

Edited by Smart-Web (see edit history)
Link to comment
Share on other sites

  • 3 weeks later...

Sorry for the delayed response, but I ended up doing that site on a manual install. 

 

However, I'm doing another one and seeing the same issue.

 

I'm not sure if I fully understood your instructions, but I went to the front office and waited for it to fully load, then I typed in the backoffice and it still didn't work, 

Link to comment
Share on other sites

  • 2 months later...

Hi,

 

I've the same problem. My version is prestashop 1.7.1 updated from 1.7.0.

At the beginning I did'nt have this problem, it came suddenly... without any modifications in the core, the scripts or this sort of things...

 

A big problem, can someone of the Prestashop team help us ?

 

Thanks

Regards

Edited by fabbea (see edit history)
  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...
  • 1 month later...
  • 1 month later...
  • 1 year later...

I've installed 1.7.5.0 and the same thing still happens. In normal mode it doesn't even try to open admin site. Just goes straight to blank page and console shows error 500. And yet it shows absolutely no error when debug mode is enabled. WTF prestashop? :/

Link to comment
Share on other sites

17 minutes ago, Sharak said:

I've installed 1.7.5.0 and the same thing still happens. In normal mode it doesn't even try to open admin site. Just goes straight to blank page and console shows error 500. And yet it shows absolutely no error when debug mode is enabled. WTF prestashop? :/

Disable debug mode. Try to go into BO and when error 500 is launched, contact with your server provider telling them the time (hour and minute) when this error was launched. Ask for a log errors. They will show you the error message with details about this error 500. Then write this message here and I can help you.

 

Best regards

Link to comment
Share on other sites

5 hours ago, Sharak said:

I've installed 1.7.5.0 and the same thing still happens. In normal mode it doesn't even try to open admin site. Just goes straight to blank page and console shows error 500. And yet it shows absolutely no error when debug mode is enabled. WTF prestashop? :/

Be sure that the user and user groups used to upload and to execute the website  are the same (you can use ftpzilla and a little PHP script to generate a test file to check user/group). Check the logs to be sure that the paths are correct. I experienced a similar behaviour and the problem was due to rights errors on user/group and to the fact that it seems prestashop try to use cache (if files exist) even if caches  have been disabled.

Link to comment
Share on other sites

I installed my shop localy on my computer and then uploaded to the server. Locally everything was fine. On the server I can't access admin panel unless I'm in debug mode. FO seems to work fine everytime.

 

Logs don't show anything. Just that it runs normally with http code 200, then I can turn off debug mode through admin advanced settings which results in blank page and http code 500 in the log or by updating values in defines.inc.php with the same result when trying to open admin page again.

Link to comment
Share on other sites

2 hours ago, Sharak said:

I installed my shop localy on my computer and then uploaded to the server. Locally everything was fine. On the server I can't access admin panel unless I'm in debug mode. FO seems to work fine everytime.

 

Logs don't show anything. Just that it runs normally with http code 200, then I can turn off debug mode through admin advanced settings which results in blank page and http code 500 in the log or by updating values in defines.inc.php with the same result when trying to open admin page again.

There is some files with logs. You should check the file named error_logs

Link to comment
Share on other sites

On 1/22/2019 at 2:33 AM, Sharak said:

I installed my shop localy on my computer and then uploaded to the server. Locally everything was fine. On the server I can't access admin panel unless I'm in debug mode. FO seems to work fine everytime

Be aware if you tried locally with Wamp and then you are using Linux for production. The path separator (\ on windows, / on Linux) changes and the cache accesses will be all wrong.

Edited by Dixin (see edit history)
Link to comment
Share on other sites

  • 1 month later...

The problem is with permissions. 1.7.5.0 repeats old bugs (typical for presta 😣 ). It works on localhost because you have full access there, but on the server it all dependes on folders' and files' permissions and it's simply wrong. Set 755 on all folders and 644 on all files. Then delete /var/cache/ content (/dev and /prod)

Edited by Sharak (see edit history)
  • Like 1
  • Thanks 4
Link to comment
Share on other sites

On 3/25/2019 at 11:48 PM, Sharak said:

The problem is with permissions. 1.7.5.0 repeats old bugs (typical for presta 😣 ). It works on localhost because you have full access there, but on the server it all dependes on folders' and files' permissions and it's simply wrong. Set 755 on all folders and 644 on all files. Thene delete /var/cache/ content (/dev and /prod)

Thanks for the reply.
I had already solved deleting / var / cache / content (/ dev and / prod).
I had read this in another discussion and it was enough to solve.

As for file and folder permissions, I had also read about these but when I tried to change those in the files something stopped working, so I put them back as they were by default. It is not clear to me what they refer to.

Link to comment
Share on other sites

  • 2 months later...
  • 3 months later...
  • 4 months later...
On 1/21/2019 at 6:19 PM, Sharak said:

Is this normal that /var/cache/prod directory has rights 0755 (the same inside) and /var/cache/dev has 0771 and most folders inside have 0777 (except /doctrine which has 0775) and most files have 0666 (except FrontContainer.php which has 0644)?

This one works perfectly well for me. Thanks !

Link to comment
Share on other sites

  • 1 year later...
  • 1 year later...
On 3/25/2019 at 7:48 PM, Sharak said:

The problem is with permissions. 1.7.5.0 repeats old bugs (typical for presta 😣 ). It works on localhost because you have full access there, but on the server it all dependes on folders' and files' permissions and it's simply wrong. Set 755 on all folders and 644 on all files. Then delete /var/cache/ content (/dev and /prod)

I confirm the recipe cited here..., facing the fkg problem of "only accessing in debug mode" by deleting the "\dev" and "\prod" folders from the \var\cache path this issue is solved. Many thanks to the contributor of the solution!

Link to comment
Share on other sites

  • 1 month later...

 

On 1/24/2020 at 3:51 PM, PrestaUserr said:

Hello, I deleted contents of  var/cache/prod folder and it worked. It generates them again, but this time correctly.

It works for me also. Somehow when you hit clear cache it doesn't clean all the cache, you have to delete it manually in file manager

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...