I'm new in J2EE and I try some samples, when I try to enter in the admin console it is in blank, curent location for the redirect login page is
localhost:4848/j_security_chec
Why? some help please.
Clear your browser's cache and cookies and then go directly to
http://localhost:4848
and you should be good to go.
Related
I was trying to set path for login page as /user/login but login form was not showing up, now by mistake I have logged out and cannot login. Please help me in logging in.enter image description here
You probably override the template for this page.
Use the twig debug and look out the template.
Without more informations it's the only thing that I can say.
How did you override the login path?
If you're using Drush you can use uli command https://drushcommands.com/drush-9x/user/user:login/
I'm manually setting the cookie during the test run as the userRole is not working for me in my local environment as the client sets the cookie and due to some reasons TestCafe clears it out.
When my first test is ran it kicks out and I set the cookie before the second test. I can see the cookie exists but as I'm already in the login page I need to use t.navigateTo(URL) to login to the homepage. When I use it t.navigateTo(URL) clears out the cookie and I keep in the login page instead of the homepage.
If I manually enter the URL of my homepage while the test is stopped at a breakpoint I'm successfully able to go to my home page and my test pass if the debug is resumed from this point onwards.
I was hopeful that the t.navigateTo(URL) would be just doing the redirect to URL but it seems with the redirect it is clearing out cookies as well. Any fix for this?
I actually figured out. By running the tests with flag --disable-page-caching it worked.
Our dnn version is 07.04.00 (353). We have an external system that redirects the user to some page. In order, the user will see the page he must have specific role i.e. this page only visible for users that have this role. If the user doesn't have this role he should be redirected to the home page.
Using chrome developer tools we see that the page get "You+do+not+have+access+to+view+this+page+within+the+website", dnn then redirect to Default.aspx where there it gets "=An%20unexpected%20error%20has%20occurred". It then try redirect to the page again and it enter into infinite loop of redirection.
Can you please advise?
Please check the Log4Net files in \Portals_default\Logs for more a detailed error message.
I want to show this following url but when I try to show it, it goes to authentication page while if you copy and paste this url in your browser it will show the requested page without authentication.
I am using phpdesigner and easyphp in which I confront this problem. I try using file_get_content, curl_init, ... but still can't show the following url.
Thanks in advance.
http://sepehrreservation.iranhrc.ir/Systems/FA/Reservation/Flight_NewReservation_Search.aspx?itinerary=THR|MHD|2017-02-28|
I am new to liferay 5.1 technology.
I by mistake removed the login portlet and now I am not able to login into the application.
I mean login portlet is no more visible any help would be of great help.
Can you please try hitting the following url?
localhost:8080/c/portal/login
Replace host and port with your host and port number.
If it doesnt work out try doing the following.(Make sure the package is correct as i am not aware of package path in 5.1)
http://www.liferay.com/community/forums/-/message_boards/message/5005621
Actually, with enough persistence, it would be also possible to lock yourself out of access to /c/portal/login (as of Liferay 6.0.6). This can be done by setting community home page to a hidden "redirect" page (as opposed to default "portlet" page), causing /c/portal/login to redirect wherever the home page redirects.
Liferay tries to prevent from doing so by issuing alerts whenever you try to make home page hidden. But you can make some page hidden and then drag&drop it to the first position in site map root level.
The reason behind doing so is to achieve a certain appearance of portal navigation (which would otherwise require some mangling in theme), i.e. make home page redirect to one of it's children.
Going back to the topic, when /c/portal/login fails, there is one another, more reliable (yet more ugly) method of getting to what one would call a login page - append this: ?p_p_id=58&p_p_state=maximized to any non-redirecting Liferay page (and probably drop any other GET parameters if existent). This is also basically what /c/portal/login does - but it appends it to home page, so if home page is a redirect page it fails display login portlet in it's maximized state.