Next Steps - System Settings

FlightPath has various global "system" settings which can be modified by an administrator by visiting the Admin Console -> System settings.

Most of the fields contain a description below to better explain what that field is.  This page will go into more detail.  Please note that depending on your configuration, there may be extra or different fields than those listed below:

 

System settings

  • Set maintenance mode?
    • Displays a maintenance message on every page if checked.  This is useful if you are performing actions which might interfere with the normal functioning of FlightPath.
  • Disable all new logins (except admin user)?
    • If set to Yes, then all other users except "admin" are not allowed to log in.
  • Disable all new student logins?
    • If set to Yes, then faculty and staff will be able to log in, but not students.
  • Only allow certain users to log in (allow list)
    • This box will override the previous two "disable" options, and let you specify exactly whom should be allowed to log in.
    • This is very useful, for example, if you don't want anyone to log in except a handful of test users.
  • Enable multi-factor authentication
    • At present, "local" users (eg, not ones using an SSO or LDAP) will be sent a validation code before being allowed to log in.
  • System Name
    • You can rename FlightPath to anything you wish.  Ex:  MyDegree, BulldogPath, etc.  This will change the displayed name "FlightPath" for all users, though it may still refer to itself as "FlightPath" in certain admin-only areas.
  • System timezone
    • Make sure to set the timezone to wherever your primary campus is located.  Users are still able to set their own timezones, but this will be what FlightPath uses by default.
  • Default tab to view when loading a new student
    • When searching for a student, and clicking on them, the default behavior is to go to the Student Profile. However, you can set the default to go directly to a different screen, like the student's Degree tab.
    • Individual users are able to override this global setting to their own preferences.
  • Clean URLs
    • FlightPath's URLs can look like either of these two options:
      • example.com/admin/tools
      • example.com/index.php?q=admin/tools
    • The "clean" version is preferred, which is the first option displayed.  This value will reflect if your server supports clean URLs, and if you wish to enable it.  It is recommended you do.
  • Theme
    • FlightPath comes with a built-in theme, but you can easily add others, allowing you to make more dramatic changes as desired.  It is recommended any new themes be added to /custom/themes.
      • Any additional themes will show as options here.
  • External/Additional CSS file(s)
    • You may specify additional or external CSS files to load, separated by comma.  This is very useful if you have web developers working on an outside server to, for example, customize the CSS.  You can simply enter the full URL to the outside CSS file here.
  • Logo image URL
    • You can change the default FlightPath "banner" logo image.  See this page for more information.
  • Allowed file extensions for public file uploads
    • Under Admin Tools -> Content, users with appropriate permissions may upload files which do not get encrypted and are visible to non-logged-in users.  This setting lets you specify the file extensions permitted.
  • Contact email address
    • On most pages in FlightPath, at the very bottom (in the footer region) is a link that says "Contact FlightPath Production Team".  This is the email address which will receive such messages.
  • Notify apply draft changes email address
    • If you wish, you may enter one or more email addresses which will be notified when someone "applies draft changes" for the degree data.
  • Notify MySQL error email address
    • If a user or routine triggers a MySQL error, this email address will be sent the details of the error.  It is recommended to enter your (or your head developer's) email address here.
  • Notify PHP error email address
    • This is the same concept as the setting above, but for PHP warnings and errors.
  • Admin Apply Draft password
    • This is the password a user must enter when they Apply Draft Changes.  See this page for more information.
  • Max watchdog (log) entry age
    • The "watchdog" is what FlightPath calls its logging system.  Most actions are logged in the watchdog. It is recommended to set this to a high value if you have the database server space available.
  • Max watchdog (log) DEBUG entry age
    • Some actions which are logged are considered "debug" messages, and are there to help developers figure out issues which might arise.  It is unlikely that these are the types of messages you'd want to keep for years, so you have the option to delete them once they reach a certain age.
  • Max watchdog (log) ERROR entry age
    • This is a similar concept as the DEBUG entry age above.
  • Default 'Allow Dynamic' value for new degrees
    • When a degree has its "allow dynamic" value set to "1" (the number one), it means the degree is allowed to be combined with other degrees.  For example, with a double major, a minor, a concentration, etc.  It is recommended to leave this set to 1.
  • Degree Classifications - Level 1
  • Degree Classifications - Level 2
    • See previous setting
  • Degree Classifications - Level 3
    • See previous setting
  • Enable legacy concentrations?
    • In older versions of FlightPath, concentrations were handled differently.  Checking this box tells FlightPath to use this legacy method.  
    • If this is a new installation of FlightPath, leave this box unchecked.
  • Allowed student ranks (CSV)
    • List every student rank code who is allowed to log into FlightPath.  For example: FR, SO, JR, SR, GR, etc.
  • Rank descriptions
    • This box allows you to describe how each rank code should appear.
    • Ex:  FR ~ Freshman
  • Not allowed student message
    • This message will be displayed when a student tries to log in, but does not have a rank code which allows them in.  Ex:  "Sorry, but FlightPath is only designed for undergraduate students."
  • Enter the 'Need Help Logging In?' Content ID number
    • On the default /login page, FlightPath displays a "Need help logging in?" link.  This lets you enter the content ID number of a page (see Admin Tools -> Content) where you might provide students with more information.
    • If you are making using of a Single Sign-On module, this is likely not needed, as no link will show.
    • If you leave this set to zero, a default message will be shown to users who click the link.
  • Log out message
    • You may use this to display a custom message when a user logs out of FlightPath.
    • If you are using a Single-Log Out service (with an SSO) then this will not be visible.
  • How often should we recalculate the alert "bell" count?
    • In the top right corner of every screen there is a bell icon which displays important notices to the user (though it is only checked on page load).
    • If you frequently have alerts or other types of notifications for users, set this to 30 seconds or less.  Otherwise you can set it to a higher value.
    • At the moment, this is only updated when the page refreshes, though in the future it may update automatically via Ajax.
  • Permanently delete the following from the database once it has been flagged for deletion
    • The items you can check off are all normally not actually deleted when a user "deletes" them.  For example: advising comments.  Instead, they're simply marked as deleted but otherwise remain in the database.  This may take up extra space in the database, but it is the only way you can "recover" something which someone has accidentally deleted.
    • Checking any of these boxes means that FlightPath will permanently delete that type of deleted item.  This may be desirable during testing or if you have very limited database storage.
    • In most production situations, you would want to leave these all unchecked.