Right, first off, well done on a module that 75% works great.....but

This isn't the first time I've had issues with modules nor is it the first time I've tried to untangle this birds nest of a site to find one single answer that helps newcomers with the problems they encounter.

Ive been with drupal for around 4 months now and still a relative "newbie" if you like but to be honest things like this make me start to wonder if I made a mistake choosing drupal at all!

Sorry for the long intro but seriously letting off steam....so to the point.....Boost

Member or admin signs in, has to sign in on near enough every page.

Member or admin signs out gets a 403 access denied, then has to sign out on every other page too.

Not only do I have to sign out on every page once I then have to do it a second time... On EVERY page.

This is what I have done, follow the instructions, adjusted the .htaccess, installed poormanscron, set logout page to not cached and flushed every damn cache I can find clearing cookies and cached data off 2 different browsers and still get the same problems.

Question, do I give up on this module too and continue to throw money after money at server upgrades because 1. these modules (some) just seem too hard to understand to a newcomer and 2. because without this module I will have to leave Drupal because I cant afford the rising server costs.

And if I can make it a 2 part question why oh why is there sooooo many settings for this module? seriously?

Sorry for the moan but I aint a developer or a rocket scientist and this is all very frustrating!

CommentFileSizeAuthor
#5 boost-645900.patch1.46 KBmikeytown2
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented

Short summary of the issues your having.
* Logged in user does not stay logged in.
* Logging out generates a 403.
* Too many settings.

The latest version of boost has some fixes for the way the boost cookie is handled (how boost tells if your logged in or not); give the new version a try. The fact that logging out generates a 403 means that Drupal thinks your already logged out; it's what Drupal does when you try to double logout: Core issue #17664: user/register should show custom message instead of 403 for logged-in users for the confusing message; this is a symptom not a solution for your situation. When you log in is it on the login block or the user/login page? Try both and let me know if the block is whats causing the issue.
Are you using something other then the core login? Do you have a module installed that handles user credentials; if yes what is it?

As for all the settings, its something I'm aware of and will try to get these down into a more manageable configuration page; the possibilities are almost endless with Boost, thats why there are all of these settings.

lagerassassin’s picture

lagerassassin CreditAttribution: lagerassassin commented

Thanks for the quick reply and sorry if my original message sounded a bit abrupt but as I said, it is frustrating to newbies and most of the talk about module development goes way over my head..

Your summary is correct, I've tried what you suggested by going straight through to the login page as apposed to the login block and just found the same results, basically, if I login on the homepage, then go to another page - logout then return to the homepage its then showing me as logged in....

as far as I'm aware I'm only using the core login, I don't think theres anything else installed that would mess with logins, only the common userpoints, views, things like that installed.

And I followed the link you gave but to me thats 20 posts of things I don't understand :(
I take it I need to somehow add this somewhere.... http://drupal.org/files/issues/useraccesserror.1.2.patch
??
And when I say somehow somewhere I mean I know nothing about patches and how or where to add them.

Thanks for your help btw

lagerassassin’s picture

lagerassassin CreditAttribution: lagerassassin commented

Ok, installed the newest version (sorry original post was wrong version stated (1.16 now 1.17) and happier with the results, the 403 page seems to have gone thank god when people sign out, still getting issues with signing in then switching pages and then signed out etc etc, can kind of live with it but if you could let me know if that patch in my previous post is what I need that would be great, then I will just have to work out how to add it.

Thanks again

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Version: 6.x-1.14 » 6.x-1.x-dev

Sounds like for some reason hook_user is not working correctly. The core patch will not solve your problems, it only makes the issue that much worse. How comfortable are you with applying patches? I should write a debug patch that saves some useful info to the dblog on user login logout.

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Status: Active » Needs review
FileSize
boost-645900.patch1.46 KB

Try this patch; based off of what went in for 1.17 and how it handles logouts I think I can use the same kind of logic for logins.

lagerassassin’s picture

lagerassassin CreditAttribution: lagerassassin commented

If I'm honest I haven't got a clue but its a good time to learn I guess lol, I will do some reading and see how I get on, sorry for my late reply, my internet sucks lol

Will post back when I have applied it, many thanks Mikey

By the way I have no longer got issues with logging out in the sense that it doesnt take users to a 403 anymore, its now simply a case of (or so I understand it) the cache is holding the users info on each page i.e logged in or logged out, so if say I visited a page signed out, then went back to another page and signed in, if I returned to the original page it would then show I'm signed out and vice versa if you see what I mean.

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented

Does what your describing happen when only the boost module is installed? Please verify before blaming Boost; this project has a tendency to bring out the flaws in code that surrounds it. The login logout thing has always been one of the more nagging issues that I can't replicate on any of my sites, as such it makes solving these bugs that much harder to do.

Now that I think about it; try this one patch for core, hopefully it does the trick for you.
http://drupal.org/node/550488#comment-1931780

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Status: Needs review » Fixed

committed this code... sadly this resulted in another setting because it directly interferes with some custom logic over here
#646228: Object of class stdClass could not be converted to string

You can grab the dev in 9 hours from now and it should fix your issue. Reopen this if it doesn't.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.