By LarryEitel on

In the process of skinning, etc. I now discover that when I log out and now try to log in I get: node?destination= with a blank screen.

Any clues are most welcome! :)

⋅ Categories: Drupal 4.7.x

Comments

LarryEitel’s picture

LarryEitel commented

Well I've been doing my homework by reading all the threads regarding login issues. I have emptied sessions table. Cleared cookies. Tried different suggested hacks.

Still... When I try to log in to the DP site on my local server (testing), it comes back with blank page and a URL of: http://ap/nb/node?destination=

I noticed this after moving the site from a subdirectory to the home directory. I reset settings.php etc and the site works otherwise. For me to login I have to request a new password and follow the link provided which logs me in.

rtdean93’s picture

rtdean93 commented

Any fix on this?

Bobby Dean

genemcc’s picture

genemcc commented

Has anyone figured it our yet?

Christoph C. Cemper’s picture

Christoph C. Cemper commented

had same troubles here... no logins possible

--- http://www.cemper.com
--- http://weblog.cemper.com
--- http://www.marketingfan.com

byronm’s picture

byronm commented

I'm using PHP 5 and the default login block doesn't work - if i go to /user and login that appears to work fine.

i'm seeing quirks with relative urls across the board. site was an upgrade from 4.6 here.

whereisian’s picture

whereisian commented

I was having the same issue until I disabled the devel module. Now logins are working.

Budrick’s picture

Budrick commented

I had the same problem. My solution is:
Delete all from watchdog table and try to login, then select * from watchdog. In output I found smth like "Cant modify headers, headers already sent by [my_module]". When I checked my_module I found that there were no closing ?> at the end of the file.
After fixing this login is OK.

Petrica’s picture

Petrica commented

I had the same problem when i logged in from my frontpage. After i read this topic i checked my user.module and after i a saw, indeed, that it's missing the last ?> . After i fixed that everithing worked smooth. I made no database changing.

THX.

mwu’s picture

mwu commented

i believe this happens when the module file is missing some punctuation, or sometimes, extra punctuation.

sometimes it's missing a semicolon

steingard’s picture

steingard commented

I was getting this error among others, and I narrowed it down to this addition that I had made to my template.php file in order to omit the extra information that my site's users do not need to see.

Unfortunately, now I am stuck with this useless information in my search results until I find a proper work around.

Christoph C. Cemper’s picture

Christoph C. Cemper commented

I can't believe it...

Just setup a new DP5 version - EVERYTHING checkout out fresh from CVS, Drupal 5.1
and guess what, I'm getting that damn redirect

to /node?destination=node

once again...

I wish I had commented more on how I got rid on this in 4.7, but it was one of these

* an extra empty link in bootstrap/database or any other of those core files
(causing an "headers already sent" error that some nerdcode supressed in the core)

* or a module throwing an exception, again error supressed by some nerdcode in the core

grrr...

--- http://www.cemper.com
--- http://weblog.cemper.com
--- http://www.marketingfan.com

Christoph C. Cemper’s picture

Christoph C. Cemper commented

ok - more details

if I login via the

/user block then it works and redirects me to /user/1

if I login via the login block, then it fails sending me to an empty page

/node?destination=node

I thought it's maybe cause the node table is empty (no content yet), but adding a node doesnt help

It has nothing to do with devel being turned on or off

Christoph C. Cemper’s picture

Christoph C. Cemper commented

wonderful... after checking thru 20 modules on / off trying that login test I found the 5.x version of globalredirect causing that error

notable that there was no watchdog entry, so I'm not really sure what's happening here

This error occurs with

clean drupal 5.1 install
clean urls enabled

- path
- pathauto
- globalredirect ( revisions 1.1.2.4.2.1 which is EQUAL to 1.2.2.4 AND 1.2.2.5 [branching problems??] )
enabled

all default setup

disabling globalredirect fixed this issue

Christoph C. Cemper’s picture

Christoph C. Cemper commented

grr.. I'm bleeding edge here ... that bug was filed 19 hours ago already at
http://drupal.org/node/115649

Bevan’s picture

Bevan commented

Me too. I found this last week, but only just worked out what exactly was going on. chx's recent post got me on the trail...

Bevan/

LeeMcL’s picture

LeeMcL commented

If you are experiencing this problem without globalredirect enabled perhaps this might help:

http://drupal.org/node/123217

Lee

--
Lee McLoughlin
lmmrtech.com

chok’s picture

chok commented

I had the same problem without globalredirect enabled and I put this in the .htaccess

SetEnv PHP_VER 5

make sure your server execute PHP 5.

Sorry for my english!

--
Cours de droit

jamesmcd’s picture

jamesmcd commented

Hello,

Can you help by telling me where exactly I place "SetEnv PHP_VER 5" in the htaccess file?

I appreciate your help

Many thanks

J

chok’s picture

chok commented

it's specific to my provider web. Ovh Provider(french)

Find your own if you haven't a private server.

--
French people, you want to know french law visit http://www.lemondepolitique.fr

source4india’s picture

source4india commented

Hi my friend ,

This is [user login] form block - action problem . you fix via form block in user.module

1) have a look - form action @ home page
2) compare action with yourdomain.tld/user path login action

:)

Regards
Manisekaran

Rachel’s picture

Rachel commented

I've just installed D6, and I cannot login (as admin) without getting destination issues (node?destination=node). Also, none of the links on the site work (perhaps because none of them have the q?= in them) - they all just lead to error 404. Is this a permanent problem? Should I be looking to get a Joomla instead of a Drupal, or is there a version I can download and install that doesn't have these silly problems with navigation links?

If there's something I can do about it by changing files in the core, can you please post the 'how' and the 'where' together in the same post, since I know very little about where everything is in Drupal, and most of the geek-speak terms mean exactly zero to me.

Thankyou very much. Rachel.
:0)

acoburn4’s picture

acoburn4 commented

I am using Drupal 6 and I have global redirect installed.

I had a Drupal install on my local machine, and it was working fine. Then, when I loaded it up to the server and tried to log-in with admin, it redirected me to this page www.website.com/node?destination=node and nothing happened.

I read through these posts, but couldn't find the answer.

Here's my solution, just in case someone finds it useful.

1. Make sure the Apache module mod_rewrite is enabled on your server
2. Make sure Apache is configured to allow rewrites; by default, Apache denies rewrites
In order to configure, just add this code to your virtual host:

<Directory />
Options FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
</Directory>

After doing the 2 steps above, .htaccess will start working properly and you will be able to log into your site without a problem.

Hope this helps someone else out with a similar problem!

Skullo-1’s picture

Skullo-1 commented

Thanks a LOT, acoburn4! This worked for me like a charm. I had a similar problem too. I had made a copy of my website on my local machine. The website worked fine on the web server, but on my local machine I couldn't log in. I was getting the same dreaded /node?destination=node redirect...
I couldn't even log in using the /user/login url.

All I had to do was to enable the rewrite_module on my wampserver... and BINGO! I could now log in!
I made an account just to comment and thank you all! :)

mister_t’s picture

mister_t commented

Solved by enabling rewrite_module. Thanks.

pierredvumali’s picture

pierredvumali commented

where should I place this? I've tried it in but it didn't worked. I saw that in my httpd.conf file I have should I place the there or it should be really in ?

Thanks in advance! I've been working on this for 2days now.

john_b’s picture

john_b commented

First check it is missing.

httpd -l
or
apache2 -l
I think is the command to check loaded modules.

Once you have done that http://httpd.apache.org/docs/current/mod/mod_rewrite.html is an Apache module which can be compiled in or loaded on startup AFAIK. So assuming you are on Apache, not ngingx or some other server, you might install it in various ways, for example with yum or apt-get. If you are on cPanel you cannot manually edit httpd.conf. On some servers you have a script to enable and disable modules, a2enmod. So there are many ways of reaching the same goal.

The basic idea, assuming that mod_rewrite is not compiled in when Apache is first installed, is that you put the binary mod_rewrite.c in the folder where all the other Apache extensions live, then you tell Apache to load it by adding a line to the configuration file, which is either httpd.conf or apache.conf, or an included file with additional information to one of those (as it is on both cPanel or Virtualmin). When you restart Apache, it knows to load the mod_rewrite.c file and knows which directory to find it in. But if you use yum or apt-get to install mod_rewrite, it will put the file in the usual extensions directory automatically (and it may be there anyway). The path to that directory in httpd.conf or whatever your config file is called, so you can go and check whether mod_rewrite.c is there. All that sounds complicated, it is not really... probably just the way I put it.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

pierredvumali’s picture

pierredvumali commented

I think my mod_rewrite is already installed because I have this line un-commented on my httpd.conf file:

LoadModule rewrite_module modules/mod_rewrite.so

I'm inquiring on where to place the above suggestion of acoburn4:

Options FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all

He said that I should put it in but I have tried that and it didn't worked.

Thanks for the reply!

iamtakashiirie’s picture

iamtakashiirie commented

I had the same problem, the login form takes me to www.domain.com/node?destination=node without logging in.

In my case, the problem was that I had a custom hard coded login form in the theme I was using.

After replacing with the default user login block, the problem is gone.

Drake’s picture

Drake commented

sub

laraz’s picture

laraz commented

I had the same problem, the login form takes me to www.domain.com/node?destination=node without logging in.

I solved modify my .htaccess

jpadif’s picture

jpadif commented

Hello, I have exactly the same problem. I installed a theme, and it worked fine for a while, then suddenly it started to showing me the blank page when I try to login, can you tell me please what you did to solve this? Because I tried almost every solution posted here, but no one has worked.

alexdb’s picture

alexdb commented

Hello

I have the same problem. I cant login. I have made the steps to reset password with the hast trick but I still can't. I stiil get http://example/node?destination=node. Even with the user/1. I get access denided. Please help :)

john_b’s picture

john_b commented

see above post about .htaccess

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

anjali.n’s picture

anjali.n commented

Thanks i changed mod_rewrite in httpd.conf. It worked me

capitanmerluzo’s picture

capitanmerluzo commented

Hi all!

I had this problem when upgrading from 7.10 (www.my710site/name710) to 7.15 (www.my715site/name715).

Trying all the above did not solve the problem, but helped. I went to .htaccess in the 7.10 files and noted that it differed from the new in just one line, placed above all the rest:

RewriteBase /name710/

So, adding the line:

RewriteBase /name715/

to the .htaccess file in the 7.15 files fixed the issue.

Thanks to all who did post here their comments. Hope it helps!

rickumali’s picture

rickumali commented

Thanks for this post! I used the RewriteBase technique to solve this issue.

After installing the latest Drupal into a different "web path" (i.e. http://localhost/drupal/"), and creating the appropriate Alias and Directory configurations in my Apache, the Drupal home page appeared, but logging in caused the issue described on this page. The errors in my Apache logs were misleading:

[Thu Nov 01 09:02:06 2012] [error] [client ipaddress] File does not exist: C:/Apache2/htdocs/Users, referer: http://rickmachine/drupal/

In terms of configuration, I had:

Alias /drupal c:/Users/rumali/drupal-7.16

<Directory "C:/Users/rumali/drupal-7.16">
    AllowOverride All
    Options FollowSymLinks
    Order allow,deny
    Allow from all
</Directory>

It was only after looking carefully at my Drupal's .htaccess did I see this comment:

# Modify the RewriteBase if you are using Drupal in a subdirectory or in a
# VirtualDocumentRoot and the rewrite rules are not working properly.
# For example if your site is at http://example.com/drupal uncomment and
# modify the following line:
# RewriteBase /drupal

I uncommented this RewriteBase, and things started working! Reading the about RewriteBase at the mod_rewrite docs was helpful to get a better understanding.

jaesperanza’s picture

jaesperanza commented

This is an old post, but I have experienced this on the last D7.56 version. I tried all methods on cache, globalredirect, and .htaccess, none worked. Disabling a contrib module Betterlogin solved the problem. Re-enabling globalredirect is also ok.

joegl’s picture

joegl commented

We have a Drupal 7.58 site with a User Login block in the site header.

On the front page, the form action is: "/node?destination=node". When attempting to login, the user gets a 404. 

On any other page, the form action reflects the current page. Login attempts are successful.

As far as configuration, we are using LoginToboggan to streamline a few login features. I am not certain if this is adding to the problem.

I do know, if I set a node as the Front Page in the "System > Site Information" settings, the login works, as it uses the node assigned to the Front Page as the destination for the Form Action. It appears this is an an issue of the User Login form not appropriately handling the Form Action when there is no node set as the front page. 

joegl’s picture

joegl commented

As a follow-up, this appears to be an unresolved issue in Drupal 8 core still. I traced the issue from:

https://www.drupal.org/project/drupal/issues/897878
to
https://www.drupal.org/project/drupal/issues/949230

The issue for the user_login form appears to this code specifically, in the core user.module file:

function user_login_block($form) {
  $form['#action'] = url(current_path(), array('query' => drupal_get_destination(), 'external' => FALSE));

Where the url being generated from the current_path() and drupal_get_destination() functions results in a URL like "/node?destination=node" instead of just "/" when on the front page.

joegl’s picture

joegl commented

I pulled the idea for a workaround from this comment: https://www.drupal.org/forum/support/post-installation/2013-05-20/login-...

Essentially, I am just resetting the form action on the user_login_block form to nothing, when on the front page, as then it will submit to itself:
 

/**
 *
 * Implementation of hook_form_alter().
 */
function MYMODULE_form_alter(&$form, &$form_state, $form_id) {
  if ($form_id === 'user_login_block') {
  	// front page action is being set to /node?destination=node which 404's
  	// empty the form action if on the front page
  	if(drupal_is_front_page()) $form['#action'] = '';
  }
}

I have tested the above and it works.

harshadananjaya’s picture

harshadananjaya commented

If you are using google recapture module,
go "Home » Administration » Configuration » Spam protection » Google reCAPTCHA" and  uncheck " User Login Block " checkbox.