Jump to content

Minkus

Members
  • Posts

    57
  • Joined

  • Last visited

Everything posted by Minkus

  1. Hi all, I've been setting up MRBS as well, and used Chris' code to implement the 'book ahead' restriction. We wanted to make it so that the restriction didn't apply to administrators - turned out to be quite easy. We changed Chris' code in edit_entry_handler - add the underlined code: If (check_allowed($_GET["month"], $_GET["day"], $_GET["year"], $max_days_ahead)[u] or getAuthorised(2)[/u]){ } else{ $err = "You cannot book more than ".$max_days_ahead." days ahead"; $hide_title = 1; } I also made it so that the same 'book ahead' restriction applied to the delete code (for why we needed to do this, read on) - in del_entry.php, add the underlined code: if(getAuthorised(1) && ($info = mrbsGetEntryInfo($id)) && ($series != 1 || getAuthorised(2))) { $day = strftime("%d", $info["start_time"]); $month = strftime("%m", $info["start_time"]); $year = strftime("%Y", $info["start_time"]); $area = mrbsGetRoomArea($info["room_id"]); [u]if (check_allowed($month, $day, $year, $max_days_ahead) or getAuthorised(2)){ } else{ showAccessDenied($day, $month, $year, $area); exit(); }[/u] if (MAIL_ADMIN_ON_DELETE) { include_once "functions_mail.inc"; // Gather all fields values for use in emails. $mail_previous = getPreviousEntryData($id, $series); } Finally, we also made it so that any logged in user was able to edit existing bookings, not just the owner and administrators. (This was why it was important for us to make the Book Ahead restriction apply to deleting entries as well as adding). Edit mrbs_auth.inc and change the GetWritable function: function getWritable($creator, $user) { global $auth; // Always allowed to modify your own stuff if(strcasecmp($creator, $user) == 0) return 1; [u]// if(authGetUserLevel($user, $auth["admin"]) >= 2) if(authGetUserLevel($user, $auth["admin"]) >= 1)[/u] return 1; // Unathorised access return 0; } Hope these code changes help anyone else trying to do the same thing!
  2. On the parent folder, under Security / Advanced, try going to the 'Owner' tab, picking 'Administrators' and using the 'Replace owner on subcontainers and objects' option. This will reset the ownership on all files and folders regardless of permissions. Once you've done this, resetting permissions should work as well.
  3. Could well be a problem with the Marlett font. See the following KB article - even though it's 95 specific, I think it still applies to later versions: http://support.microsoft.com/kb/134861
  4. Recently installed the .NET Framework 3.0? Try this: http://support.microsoft.com/kb/944203
  5. I think the best thing to do if you've got nothing is to start NOW. If you're installing a new server, document how and why you did it. Then next time you start fiddling with something slightly older, make part of the job documenting what's there already. Try to fill in the gaps in spare time at the end of the day & odd moments (like if you're waiting for a large file to download, or for someone to ring you back). I find documentation is best done 'on the job' - if you try to do it all in one go, it just becomes a mammoth task that never gets completed.
  6. If you don't want to install the HP JetAdmin software, you can do it with a few scripts. See the following HP link: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpl03612 I've attached a zip file which contains the scripts that we use here. All you have to do is map the (presumably networked) printer to the LPT2: port as so: net use LPT2: \\server\printershare then run one of the scripts. There are various levels of lock, and I've provided scripts for 'Off', 'Moderate' (which gets rid of quite a lot of settings) and 'On' (which gets rid of pretty much everything). We tend to use 'On' for most printers, as under 'Moderate' you can still change the Copies setting on most printers, which is one of the more annoying ones. Unfortunately 'On' also disables the Cancel Job button if you have one - but that's just the price you have to pay. You can set a password as well if you want to so that the lock can't be easily disabled, but we haven't found this to be necessary in our environment. hp_laserjet_control_panel_lock.zip
×
×
  • Create New...