At an authenticated user logging in, drupal recognises them fine, but still displays the home page for non-authenticated users.
They have to click on 'home' before they see the homepage for authenticated users. ie after logging in the 'home' link works correctly for them.
I'd like the logging-in process to trigger the displaying of the authenticated users' homepage.
I have searched for this and http://drupal.org/node/82251 has the same problem but I cannot understant where to apply the suggested solution.
I haven't "inadvertantly selected SAME for logged in users" as you suggested in http://drupal.org/node/78036
I am having no other problems with front-page which is, overall, brilliant.
Thanks
Nigel
Comments
Comment #1
dublin drupaller commentedHI Nig,
Sorry, but, I'm unable to recreate the problem in 4.7 and 5.0 (even with aggresive cache on) and it works as it should. I don't get the same problem you are having.
There's not much difference between the Drupal 4.7 and Drupal 4.6 versions and while I haven't got a test Drupal 4.6 installation to try and recreate your issue with, can you check to see if it might be a login issue, such as this one: http://drupal.org/node/70521 ?
I don't mind installing a test bed Drupal 4.6 to try and recreate the problem your having..but, before I do, can you confirm it isn't any of the login/cache issues already raised?
Thanks
Dub
Comment #2
nig commentedhello Dublin
Thanks for thinking about this.
I looked at the issue you mentioned. I have not had trouble with any of those issues myself, but one of my users has reported such an issue to me (after logging out they still see authenticated content).
Unfortunately I am unable to perform patches [Windows system etc]. Beleive me I have tried and tried as this barrs me from a lot of good Drupal developments. I just can't get it to go.
To save you installing a test site, would you like to create an account on my site and see it there? www.healheadingley.org.uk
Thanks again
Nigel
Comment #3
dublin drupaller commentedNigel
drop me an email with a bog standard login and I'll have a look at your site.
that's quicker than me installing Drupal 4.6.
cheers
Dub
Comment #4
Anonymous (not verified) commentedI have the same problem in version 4.7 ( http://drupal.org/node/90008). I tried the solution on http://drupal/org/node/82251. It worked!
For understanding: There is no admin menu after installing the module, you should open de login _destination module file and change line 24 in $path = 'front_page';
What I think is that the problem is not a caching problem, I thougt that first but could not find the solution therefore. Imo there is a trigger missing for opening the node front_page.
Comment #5
dublin drupaller commentedhttp://drupal.org/node/82251
Comment #6
nig commentedHi Dublin
Looks like you are recommending the fix at http://drupal.org/node/82251
I'd be happy to try it, but I have no modules/login_destination/login_destination.module in my site.
Where do I make this change of code?
I am now running 4.7.5
Thanks for a great module
Nigel
Comment #7
Phillip Mc commentedYou can work around this by creating a custom LOGIN block that forces the login destination to the front page. Note the Form action in the snippet below. You can configure the block to only appear for Anonymous Users.
The only problem with that is it creates confusion for users who try to access a page, but, are not logged in and when they login, instead of being brought to the page they were trying to access, they are forced to the front page.
In other words, it's probebly a bad idea to force the login destination.
Philk
Comment #8
nig commentedThank you for this fantastic idea. I don't mind about the drawback you mention as it would only apply to a few of my logger-ins, whereas at the moment all my logger-ins don't get directed where they should on login ie. to the members home page (=/node).
However .....
It all worked fine, following your instructions, as long as I still had the old member login block enabled as well as your new one.
As soon as I had done all testing, was happy, and disabled the original login block then .... a login would send a user to /node/front_page?destination=front_page, which displayed the /node page I am wanting punters to see, but they were still not logged in. ie they were still being treated as an anonymous user.
So near and not quite there.....
Any suggestions?
Comment #9
dublin drupaller commentedSorry nig, I'm unable to recreate the login problem your having with Drupal 4.7.5 and the latest front_page module for 4.7.x.
Recommend you check out these threads relating to login problems. The front page module doesn't manage logins, it just displays a different front page after someone has logged in, so it sounds like the problem you're having is happening earlier.
Incidentally, for a site's ergonomics, it's probably not a good idea to redirect users to the front page every time they login. It's far better to bring them to the page they were trying to view.
Marking this as closed.
Dub
Comment #10
huayen commentedI am using latest front page module on Drupal V5.1, also having the problem of "Logging in gives the same page as for non logged in" as Nig described. Dublin, I don't know why you can not encounter this problem, but I found it on both V5.0 and V5.1. So, I guess this is not a 'only' problem of Nig.
Or, you can try log into my site to see the problem:
http://www.featips.com
user:demo
Password: demo
Front Page is really a great module, hoping this problem can be solved soon.
-Derek
Comment #11
huayen commentedAdd more detail:
In front page setting, I redirect anonymous user to go to http://featips.com/anonymous, and redirect login users to http://featips.com/authenticated.
After user logged in, the first page showing after login is still http://featips.com/anonymous, not my expected http://featips.com/authenticated. Only after clicking 'Home' will load http://featips.com/authenticated.
This is exactly what Nig described. Should be a bug of front-page module.
Comment #12
Phillip Mc commentedIt's not really a problem with the front_page.module it's a simple problem when using REDIRECTS.
As an example: If the front_page settings for anonymous user is set to REDIRECT to 'node/4'...when an anonymous visitor comes to the site, they land on 'node/4' for the front page - and thus the login destination in the LOGIN FORM is 'node/4' - so when that visitor logins in, they will be brought to 'node/4'.
The correct usage is to use the text area for Anonymous User on the front_page settings page instead of redirecting. By using the text area to set the front page for anon users, it means the LOGIN DESTINATION is 'front_page' for the LOGIN FORM when a visitor lands on the site, so when the visitor logs in, they see the front_page for authenticated users.
Perhaps the readme.txt file might have a note about that. it's a simple mistake to make.
phil
Comment #13
nig commentedThat did it for me.
Thank you for spelling it out Phil. I wouldn't have got there without, so I think your idea of putting it in the help text would be good.
Thanks for a great module, Dub.
Nig