Let me ask, is there anyone who has actually gotten this mod working correctly on their own forum? Before attempting re-implementation, I'd like to know if it's worth the time ...
Let me ask, is there anyone who has actually gotten this mod working correctly on their own forum? Before attempting re-implementation, I'd like to know if it's worth the time ...
Yes, finally...But it took some work and a bit of trial and error. It appears that the following steps need to be taken in this specific order:
------------------------------------------------------- 1) Copy the new files to your forum directory
2) Run the "Admin Level MOD" in MOD SETUP (to add the additional "M_ALEVEL" field to the FORUM_MEMBERS table.
3) You'll have to edit the database directly...Find the field "M_ALEVEL" in the FORUM_MEMBERS Table and set the value to "1" for your super admin account "admin", and anyone else you want to have access to Admin Options.
4) Make all of the code changes as noted in the readme.txt file. -----------------------------------------------------------------
Once that's done, the administrators with a "1" in the M_ALEVEL can access the Admin Options (The link will appear right below the LOGOUT button). They also have access to a dropdown list to grant or revoke access to Admin Options for the other members while editing that members profile.
Admins WITHOUT the "1" won't have the "Admin Options" link, and will only see the "Admin Options Allowed: No" statement in their profile without a dropdown.
I wonder how David is getting on with the improved version?
I'm also wondering how it will handle MOD's that use admin level. I'm thinking Active Users and Private Messages (PM all Users) just off the top of my head.
I wonder how David is getting on with the improved version?
I'm also wondering how it will handle MOD's that use admin level. I'm thinking Active Users and Private Messages (PM all Users) just off the top of my head.
I'm not 100% sure, but It seems like it would still work. the code changes just check for "M_ALEVEL = 1" in addition to the normal check for "M_LEVEL = 3". The only time you'd care about the "M_ALEVEL" field would be when an administrator is attempting to access any of the options from the admin menu.
Okay... I have everything working or at least it seems, EXCEPT... When I try to view edit or any thing on someones (even me) profile, the page cannot be displayed. I have the full admin stuff, i am the super admin blah blah blah... but i think there is an error in Pop_profile.asp and i dont know what... any help?
as soon as i add the lines into the pop_profile.asp i am no longer able to view there profiles. I have installed the fields into the database and checked to make sure they are there.
Success! Thank you, Frank! Following your instructions, step by step, resulted in the MOD working as advertised. A bit awkward, I'd say, and the ReadMe is not all that clear on the order of things - at least to me, and apparently to a few others, as well - but, in the end, I'm satisfied. Thanks, David K. for creating it!
To JLocke & Sentinel ... I checked this right off. Works fine on my forum. Do as Frank says! Also, check your copied & pasted code for errors or misplacement. It does work.
The first big problem was that if you made the code changes before installing the MOD, then you crashed all over the place because the code was looking for the M_ALEVEL field which wouldn't exist in the table yet. CATCH-22! The second problem was that even if you ran the MOD install first, then made the code changes, then tried to access the admin page, you couldn't because the M_ALEVEL field was set to "0" for everyone so nobody would be allowed access to the admin page. CATCH-22 again!
I suspect that David thought/thinks his MOD install automaticalyy assigns a "1" to the "M_ALEVEL" for all of the administrators, which it doesn't.
UPDATE: I just looked at the "dbs_AdminLevel.asp" file and it looks like that may be part of the problem.... The file looks like this:
------------------------------------------------------ Admin Level MOD (Default) [ALTER] MEMBERS ADD#M_ALEVEL#int#NULL#0 [END] [UPDATE] MEMBERS M_ALEVEL#1#M_LEVEL=3 and M_ALEVEL <>0 [END] [UPDATE] MEMBERS M_ALEVEL#0#M_ALEVEL <> 1 [END] ----------------------------------------------
The two [UPDATE] lines don't seem to make sense for this MOD.
The first [UPDATE] is assigning a "1" to "M_ALEVEL" for all records where "M_LEVEL=3 and M_ALEVEL<>0". All administrators will have a "3" in M_LEVEL, but all of the values for "M_ALEVEL" will be "0" (meaning no records match the search criteria) and nothing would get updated. It should read like this:
[UPDATE] MEMBERS M_ALEVEL#1#M_LEVEL=3 [END]
The second [UPDATE] (which wouldn't be needed now anyway) is attempting to set M_ALEVEL to "0" for any records where M_ALEVEL isn't already set to "1". I would think that the only values in this field would be either "0" or "1". Again, if you remove the "and M_ALEVEL <>0" portion from the first [UPDATE], all of your administrators will have access to the Admin Page, then you could log as "admin" (the super admin), and edit the profile of each admin to grant/deny them access to the Admin Page.
I know... It sounds complicated, but it really isn't once you really think about it
then simply load the page from their local drive, change "Allow Admin Options" to "Yes" then submit the form and they can root ya. There needs to be some sort of check function in place to see if their current ALEVEL is set to 0 then don't allow them to set an ALEVEL to 1.
Topic Locked
Posted - 06 January 2003 : 07:02:27
