where does drupal navigate to after posting a comment ?

ruled out the possibilty this is merely a psychotic episode im having by testing this issue on a different machine and with DRUPAL 4.7 as well. both 4.6 and 4.7 seem to have this BUG [after posting a comment drupal returns to a node list and not to viewing the node the comment was added to, but still shows the address q=node/(nodeNumber)#comment-(newCommentNumber)].

furthermore i have just installed internet explorer 7 and tested it. it seems IE7 doesnt have this BUG.

but that doesnt help much since IE7 isnt officialy out yet. i cant believe such an obvious problem can exist on the IE6 [which right now is the most important platform on the market].

havnt been getting lots of replies on this issue. i guess replies are about to start pouring in :). i must say i really regret choosing drupal. getting no support whatsoever / buggy / and messy docs. come on ! do you devs realize you have some reponsibilty towards ppl ? ive just spent more than 2 weeks studying your system. what i ask is simple enough -

can someone please confirm this simple behaviour :


with drupal 4.6 or 4.7 on internet explorer 6 > create new PAGE content type > add new comment > enter comment info > press post comment > does drupal show you now a nodes list or do a single node view + its list of comments ?


please someone who used drupal before, check it on your system. if this is really a bug i might find a way to bypass it and not lose all this time ive invested in drupal already

thx

yo simon thx so much, needed that confirmation to make sure im not wasting my time digging deeper into drupal. for me that comment behaviour is critical though

so anyway and to anyone out there interested i have some further info on the issue-

it seems IE6 does have some trouble handling drupals URL redirection. look in includes/common.inc for

function drupal_goto($path = '', $query = NULL, $fragment = NULL) {
  if (isset($_REQUEST['destination'])) {
    extract(parse_url($_REQUEST['destination']));
  }
  else if (isset($_REQUEST['edit']['destination'])) {
    extract(parse_url($_REQUEST['edit']['destination']));
  }

  $url = url($path, $query, $fragment, TRUE);

  // Before the redirect, allow modules to react to the end of the page request.
  module_invoke_all('exit', $url);

  header('Location: '. $url);

  // The "Location" header sends a REDIRECT status code to the http
  // daemon. In some cases this can go wrong, so we make sure none
  // of the code below the drupal_goto() call gets executed when we redirect.
  exit();
}

as is commented that header('Location: '. $url) seems to go wrong. having changed it with the following-

function drupal_goto($path = '', $query = NULL, $fragment = NULL) {
  if (isset($_REQUEST['destination'])) {
    extract(parse_url($_REQUEST['destination']));
  }
  else if (isset($_REQUEST['edit']['destination'])) {
    extract(parse_url($_REQUEST['edit']['destination']));
  }

  $url = url($path, $query, $fragment, TRUE);

  // Before the redirect, allow modules to react to the end of the page request.
  module_invoke_all('exit', $url);

  //header('Location: '. $url);

?>

<script language="javascript">
document.location.href = "<?= $url ?>";
</script>

<?
  // The "Location" header sends a REDIRECT status code to the http
  // daemon. In some cases this can go wrong, so we make sure none
  // of the code below the drupal_goto() call gets executed when we redirect.
  exit();
}

seems to fix my problem. im dont think this is the perfect solution and i would be happy to get more info about this issue but being on a tight deadline and having wasted enough time on this issue, i have to move along.

hope this helps someone

oh the coin just dropped on what youve suggested and it might work for me as well since focusing on the recently added comment isnt that important to me as well. i havnt tested it yet but i will later on tonight and post my conclusions. so - another thx.

an unbased suspicion i had is that the usage of the char # in the url header LOCATION might have caused the problem by being misinterperted in IE6. your solution, completely removing the anchor call #comment-$cid, might support that suspicion. but thats just a shot in the dark, im not that great in php