Jump to content
ceffylau

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

 

 

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
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)

Share this post


Link to post
Share on other sites

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, 

Share this post


Link to post
Share on other sites

This did not work for my, not sure why. 

 

But yes this a Softacuolus error, just not sure how to fix it. 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Hi,

I have also the same problem since the update to Prestashop 1.7.1.1

  • Like 1

Share this post


Link to post
Share on other sites

same here, i can only log in to the backoffice if i go into Debug mode.

i tried to change from HTTP tp HTTPS, then this happend.

Edited by Rekal007 (see edit history)
  • Like 1

Share this post


Link to post
Share on other sites

+1

 

Me after change HTTP to HTTPS in backend, only in the backend ERROR 500, but if i active Debug mode the backend works finde

Share this post


Link to post
Share on other sites

Same here, if debug mode is off, I get an error 500 when I load the backend.

 

My PS version is already 1.7.1, it's on HTTPS and has custom backend url (www.mydomain.com/custom-name)

 

Any idea?

Share this post


Link to post
Share on other sites

Same problem. Only can enter to backoffice width debug mode.

 

Its happened me after updating custome theme. But i try to back to classic theme and the error still happened

Share this post


Link to post
Share on other sites

Hello everyone,

Could you please make a new ticket on the forge to report the issue to the Product Team? Here is the dedicated link (note that you'll need to make an account on the forge to get access to this link).

Thank you! :)

Share this post


Link to post
Share on other sites

I have the same problem. i am not sure i understood LieBM 

 

 

 

UPDATE:

i updated prestashop to last version and now it works ok

Edited by francescR (see edit history)

Share this post


Link to post
Share on other sites

For me the car/cache/prod folder (with contents) was missing, after copying it from another site it worked like a charm

Share this post


Link to post
Share on other sites

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? :/

Share this post


Link to post
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

Share this post


Link to post
Share on other sites

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)?

Edited by Sharak (see edit history)
  • Like 1

Share this post


Link to post
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.

Share this post


Link to post
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

Share this post


Link to post
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.

Share this post


Link to post
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

Share this post


Link to post
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)

Share this post


Link to post
Share on other sites

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)
  • Thanks 2

Share this post


Link to post
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.

Share this post


Link to post
Share on other sites
On 3/26/2019 at 12:48 AM, Sharak said:

Thanks, now work, only need delete /var/cache/ content (/dev and /prod)

 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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 !

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More