Since yesterday and for no apparent reason I can't longer login to the backend of my prestashop 1.7.6.8.
The login page appears normal but if I insert credentials the button load for some seconds and after the page remains the login page. (If I insert wrong credentials the page remains the same except for the login fields that disappear).
There was no updates (the version of prestashop is the same since I
installed it and no modules have been added or updated these days).
No changes have been made to the php 7.2 version of the server (and
no change to other requirements)
By activating the debug mode the backend login page does not show any
errors I searched in the logs and there are no errors
What could be happened?
Thank you
Related
I have a website for family content. I wanted to block external users so I set the pages to be visible just for registered users. So I put a login module to the footer so that users (me and my family members can log in even if the error page came up that you are not allowed to view this page (before logging in). It worked well.
enter image description here
However, after I upgraded to Joomla 3.10 the error page appears differently and my footer with the login module is not visible.
enter image description here
Unfortunately, I haven't made a backup for a long time so using an earlier version of the site is not an option. Could you help me find a good solution to this problem? Creating another method to log in or customize the error page or whatever good idea.
Thanks in advance
I am building an app using .Net Core with VueJs along with JavascriptServices&NodeServices for ServerSideRendering, and Identity as auth mechanism.
Scenario :
I navigate to /details page - having some hidden info because the user is not logged in (so, User.Identity.Name) is null.
I click login, a pop-up shows up, I enter my credentials, and after the AJAX call is made to auth the user, I do a full refresh of the page using location.reload(true).
This works on chrome desktop but on mobile devices it doesn't; on mobile browsers it works if I "fake navigate away" meaning that I go back one page and then come back (so I don't trigger a SSR).
Does anybody have an idea why this doesn't work?
I installed Dspace multiple time on different windows servers.
I worked perfectly but i faced a fundamental problem in user authentication.
When I register a new account, it was made correctly.
the main problem is on the login/logout process.
When i logged in, then would like to logout,after a short refresh, the header of the Dspace was not changed the user status and continue to display my username instead of login button. I notice that when the page refreshed manually , the problem was solved.
another problem is that when i try to login from other browsers, before authentication, I see my username or other username(unknown) on top of the page.
Please inform me about the potential problems and solutions.
It's the navigator cache. It is harmless
Our web app allows users to log in via Facebook. Technically, we are using Facebook OAuth2. We have implemented this login process two years ago. It worked fine until 13th November 2015 but since that day it does not. When our server sends the request
https://graph.facebook.com/oauth/access_token
with appropriate parameters (client_id, redirect_uri, client_secret, code), the response from Facebook has HTTP status 400. The response body is a HTML page saying "Sorry, something went wrong".
On 13th November, there was some problem on Facebook probably.
I have found the following message:
http://www.independent.co.uk/life-style/gadgets-and-tech/news/facebook-down-site-breaks-for-many-people-though-not-for-everyone-a6732906.html
However, our server still gets this error response after a week. We have an instance of the system deployed in the production environment and one more instance in the test environment (with different Facebook account, i.e. with different client_id and client_secret). Currently, Facebook login works fine in the test environment. I am not sure if it worked on 13th November.
Do you have any experience with recovery from such problem? Why does Facebook login work in test environment and does not work in the production environment in the same app? Why did the production instance break on a particular day and is still broken a week later?
Thanks for any help.
I had the same issue. I believe that the issue stems from passing in invalid scope in your authentication requests. Try removing the scopes in your authentication request to see if that works.
One more corner case I found in 2022:
In the App Dashboard, if you choose Facebook login for Business, same error happens. It will go away as soon as you select Facebook Login one.
Finally, the issue was resolved by restarting the servlet container (Tomcat 7). However, I have no idea why.
All of this is using exclusively the login button. Not the API serverside and not FB.login(). It would work for me sometimes and sometimes not and I couldn't figure out why. I would open a new window and it may work, or may not - but it seemed like once broken it was broken.
There appears to be an issue when using the Chrome 'Device simulator'.
Looking at the SDK Javascript (that's to say the SDK that the Facebook Login button uses) it checks to see if the device is a 'touch' device and if so it will use the m.facebook.com domain when requesting the oauth token.
This domain fails m.facebook.com:
However if the mobile device mode isn't activated when the page loads then it uses www.facebook.com and succeeds:
So for me the current workaround is:
Assuming you are developing with the console active.
When you need to reload your page press Ctrl + Shift + M to deactivate the mobile device mode.
Refresh the page
Once the button has initialized press Ctrl + Shift + M to reactivate it again.
If you see m.facebook.com then you didn't do it fast enough, or maybe you're using something like Angular with hot reload and you need to manually refresh.
I have had the facebook connect set up for over a few months and have done a lot of testing on it and everything seems to be working correctly. Suddenly when I try to login using the php facebook sdk I get redirected to the following page https://www.facebook.com/help/258359927634494
It seems to let me login on occasion, but it usually redirects to this page. I assume my app was reported however we only have a few test users at this time as we are in beta and I stopped my app from asking for repeatedly for post permissions a while back as soon as I was aware it was doing that. What can I do to clear up the report?
This message appears when an app loads the login dialog many times in a short duration. Make sure you are only loading the dialog once per user. Until this redirect behavior is tweaked to be me more lenient, try waiting ~30 seconds between tests.