which version are you using?
with 0.18.0 and 0.18.3 its working correctly.

I'm not allowing anonymous login too.

I think I fixed this some versions back. Try upgrading to 0.18.3.

I have both 0.18.2 and 0.18.3 running and it is not working on either installations.
The installations are running on the same server, so the setup should not have any thing to say.

hmmm...
that's strange.

on which side are you after clicking the link and logging in?

When clicking the link I am promted for login and the returned to main_page.php

hmmmm....

sorry, i have no idea.

vboctor?

is your 0.18.0 / 0.18.3 a "new installed" version or an updated version?

i have both versions "new installed" without this problem.

bearbeitet am: 06-18-04 05:37

Both 0.18.2 and 0.18.3 are clean installs - the only mods are the mailsetup, header and footer on pages and db setup in config

maybe you've changed something essential in the header.

can you post it?

in between i'll try to find out where this redirect is happening.
its the login_cookie_test.php i think...

bye the way: the user who tries to login, has access to the bug in the link?

bearbeitet am: 06-18-04 06:28

The user is me, and I am administrator with access to everything I think.

I have uploaded the 2 files I use for header and footer - there are some images that I haven't uploaded

ok, your header / footer shouldn't be the problem, unless its not in the page ahead of the redirect.

i guess you need some help of vboctor...

the redirect to the bug-page is in the page login_cookie_test.php
over $f_return = gpc_get_string( 'return', 'main_page.php' ); (line 17)
this will give back the url.
try
print_r($f_return);
exit;

you should get something like /mantis/bug_view_page.php?bug_id=0000123
with the bug-id in the link.

did you try to switch on all debug-messages under "Debugging" in config_defaults_inc.php (especially $g_stop_on_errors=ON;)?

maybe you'll get a warning then.

bearbeitet am: 06-18-04 07:00

When I try the
print_r($f_return);
exit;

I get main_page.php

$g_stop_on_errors = ON;
SYSTEM NOTICE: Undefined index: REQUEST_URI

Sorry - pushed the button to soon

$g_show_detailed_errors = ON
$g_show_notices = ON
$g_show_warnings = ON
$g_stop_on_errors = ON;
SYSTEM NOTICE: Undefined index: REQUEST_URI

hmm... i'm nearly out of ideas...

vboctor???

one last thing to check:

when you type in an url like http://your-domain/bug_view_page.php?bug_id=0003948
in the browser-address, hit enter then you're redirected to the login_page and the url should be like this
http://your-domain/login_page.php?return=%2Fmantis%2Fbug_view_page.php%3Fbug_id%3D0003948

is this the url you get?

The URL that I get is http://your-domain/login_page.php?return=

so thats the problem!

which browser are you using?

bearbeitet am: 06-23-04 05:48

Mozilla FireFox 0.8.0+
Internet Explorer 6.0.2800.1106

do you have the problem in both browsers?

if yes...

open core/access_api.php
got to line 34:
$p_return_page = string_url( $_SERVER['REQUEST_URI'] );

place afterwards
echo "p_return_page: $p_return_page - ";
echo "REQUEST_URI: ".$_SERVER['REQUEST_URI'];
exit;

and tell me if you get an output and paste it here (when opening url like http://your-domain/bug_view_page.php?bug_id=0000123).

should be something like
p_return_page: %2Fmantis%2Fbug_view_page.php%3Fbug_id%3D0000123 - REQUEST_URI: /mantis/bug_view_page.php?bug_id=0000123

bearbeitet am: 06-23-04 06:13

The only output I get is

p_return_page:

And the problem is in both browsers

i've edited my note..
please put all 3 lines in your code and paste the output.

p_return_page: - REQUEST_URI:

so.. i guess its not a mantis.. but a server problem...

$_SERVER['REQUEST_URI'] is a server variable...

please ask vboctor for more details.. my knowledge isn't enough... i think.

Erinnerung gesendet an vboctor

Hi!

The server-variable $_SERVER['REQUEST_URI'] is empty...
So I guess he may have a server problem.
Can you help him?
My knowledge ends here.

Bye,
Jumar

What version of PHP are you using?

PHP 4.3.4
MySQL 3.23.38
IIS on Windows 2000 server

The issue is still alive after I installed version 0.19.0a2 so it might be a server problem, but what?

Any one with any ideas

grangeway> I can see you added a relationship, but I can't get access to it.

Question:

Does changing the 2-3 references in access_api, authentication_api of:
$_SERVER['REQUEST_URI']
To read:
$_SERVER['PHP_SELF']

Have any effect for you ?

Yes it results in:

APPLICATION ERROR #200
A required parameter to this page was not found.

in which case, try adding one of following before the REQUEST_URI lines. I'd be interested in whether both/neither work.

if (!isset($_SERVER['REQUEST_URI'])) {
$_SERVER['REQUEST_URI'] = $_SERVER['SCRIPT_NAME'].'?'.$_SERVER['QUERY_STRING'];
}

if (!isset($_SERVER['REQUEST_URI'])) {
$_SERVER['REQUEST_URI'] = $_SERVER['PHP_SELF'].'?'.$_SERVER['QUERY_STRING'];
}

if (!isset($_SERVER['REQUEST_URI'])) {
$_SERVER['REQUEST_URI'] = $_SERVER['SCRIPT_NAME'].'?'.$_SERVER['QUERY_STRING'];
}
gives an URL like
http://hqsm2/bug_test/login_page.php?return=%2Fbug_test%2Fbug_view_advanced_page.php%3Fbug_id%3D0000097

when inserted in access_api, authentication_api and when pressing the link in my mail I am redirected to the login picture and when logged in I am returned to the correct bug / issue

I haven't tried the second yet - should I do so ?

The code in authentication_api
} else { # not logged in
if (!isset($_SERVER['REQUEST_URI'])) {
$_SERVER['REQUEST_URI'] = $_SERVER['SCRIPT_NAME'].'?'.$_SERVER['QUERY_STRING'];
}
if ( is_blank( $p_return_page ) && isset( $_SERVER['REQUEST_URI'] ) ) {
$p_return_page = $_SERVER['REQUEST_URI'];
}
$p_return_page = string_url( $p_return_page );
print_header_redirect( 'login_page.php?return=' . $p_return_page );
}

ok, so that code solves the issuefor you?

Both $_SERVER['PHP_SELF'] and SCRIPT_NAME as far as i know should return the same value - i'd be interested in you confirming that this is the case as i think i'd rather check for $_SERVER['PHP_SELF'] then SCRIPT_NAME

If that does fix the issue, i'll check something into CVS for 0.19

Paul

The fix for this issue should be in 0.19.0rc1 when it's released.

Has to add note for Paul

Just tested the second code snippet and the result is the same - it works. If that is the one you like the most, then I will leave this in my setup.

Had to reopen the bug to be able to add this comment! I think some people would like that the participant in an issue (and only those) could add notes even after the bug was resolved/closed - I know that I would.

thanks