[Xoops-trackers] [ xoops-Bugs-1014203 ] xoops2.0.7.1 "Administration Menu" link of "user menu"

[SourceForge.net <no...@so...>]

Bugs item #1014203, was opened at 2004-08-23 18:15
Message generated for change (Comment added) made by onokazu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1014203&group_id=41586

Category: Core -  Core
Group: XOOPS 2.0.x
Status: Open
>Resolution: Fixed
Priority: 5
Submitted By: toshimitsu (domifara)
>Assigned to: K.Ono (onokazu)
Summary: xoops2.0.7.1 "Administration Menu" link of "user menu"

Initial Comment:
xoops2.0.7.1 "Administration Menu" link of "user menu" 

not what happens is that this menu became "context-
sensitive".

It is if it is why.
As for $xoops_isadmin, the value is set by 
$xoopsUserIsAdmin.

Related sauce 
include/common.php line 220
$xoopsUserIsAdmin = $xoopsUser->isAdmin();

and 
assign 

header.php about line 91 etc

$xoopsTpl->assign(array('xoops_isuser' => 
true, 'xoops_userid' => $xoopsUser->getVar
('uid'), 'xoops_uname' => $xoopsUser->getVar
('uname'), 'xoops_isadmin' => $xoopsUserIsAdmin));

---------
It is if you want to make it "context-sensitive."
I think that a change of include/common.php  should 
also be made.

maybe 
 In include/common.php  the last place

Changing is also set to "context-sensitive" like add lines
-----------
	if (is_object($xoopsUser)) {
		$xoopsUserIsAdmin = $xoopsUser-
>isAdmin();
	}
-----------

----------------------------------------------------------------------

>Comment By: K.Ono (onokazu)
Date: 2004-10-02 09:08

Message:
Logged In: YES 
user_id=290718

This has been fixed in 2_0_9-branch, common.php 1.59.2.2
Also I have removed the isAdmin call in b_system_user_show
() of system_blocks.php since the user menu block template 
uses $xoops_isadmin.

----------------------------------------------------------------------

Comment By: K.Ono (onokazu)
Date: 2004-10-02 05:04

Message:
Logged In: YES 
user_id=290718

I will personally work on this and would probably be removing 
the fix added to 2.0.7.1 and use another way to fix the bug 
originally posted.

----------------------------------------------------------------------

Comment By: toshimitsu (domifara)
Date: 2004-08-24 08:14

Message:
Logged In: YES 
user_id=926983

Thank you jegelstaff
I investigated and looked at . 
Although the condition which is writing is different
However, it was surmised that a cause was the same. 
Surely, the condition like [1109439] is also caused.
Is it better to set this report status to "close"?  

----------------------------------------------------------------------

Comment By: toshimitsu (domifara)
Date: 2004-08-24 08:14

Message:
Logged In: YES 
user_id=926983

OK, I'll take care of this one personally. 

----------------------------------------------------------------------

Comment By: toshimitsu (domifara)
Date: 2004-08-24 08:08

Message:
Logged In: YES 
user_id=926983

Thank you jegelstaff
I investigated and looked at . 
Although the condition which is writing is different
However, it was surmised that a cause was the same. 
Surely, the condition like [1109439] is also caused.
Is it better to set this report status to "close"?  

----------------------------------------------------------------------

Comment By: toshimitsu (domifara)
Date: 2004-08-24 08:08

Message:
Logged In: YES 
user_id=926983

OK, I'll take care of this one personally. 

----------------------------------------------------------------------

Comment By: Julian Egelstaff (jegelstaff)
Date: 2004-08-24 00:15

Message:
Logged In: YES 
user_id=1109439

I think this is talking about the same thing I talk about
in: 1014403

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=430840&aid=1014203&group_id=41586