1. 09 May, 2002 1 commit
  2. 08 May, 2002 1 commit
  3. 22 Apr, 2002 1 commit
  4. 01 Mar, 2002 1 commit
  5. 26 Feb, 2002 1 commit
  6. 25 Feb, 2002 1 commit
    • Leigh B. Stoller's avatar
      Change caching directives. Used to be that all of the pages we spit · c6f8434f
      Leigh B. Stoller authored
      out included directives to prevent caching along the way. Now we look
      at the protocol (http vs https) and include directives that allow
      (encourage) http pages to be cached for a short time. My reasoning is
      that anything we spit out via http is documentation, and can grow a
      bit stale. Sure, the menu on the left is dynamic, but not so dynanic
      that it can't go a little stale too for people who are not logged in.
  7. 14 Feb, 2002 1 commit
    • Leigh B. Stoller's avatar
      A morass of form changes. The main goals are to avoid the loss of info · 9ac3d870
      Leigh B. Stoller authored
      when backing up (cause of an error that needs to be fixed) since not
      all browsers handle this the same. Instead, redraw the form with all
      of the original info and a list of error messages at the top.
      Conceptually simple change, but it turns out to be a pain to implement
      since you need to combine the form and processing code in one page
      (well, its just a lot easier to do that), and then change all of the
      forms to deal with a "default" value. That is, each different kind of
      input tag (text, radio, select, checkbox, etc.) requires slightly
      different changes to do that. Lots of forms, lots of entries on the
      forms, and its a long slow tedious process. Much nicer though, although
      the code is a bit harder to grok. At the same time, I added a lot more
      sanity checks of the information being passed in.
      The other change is to deal with how browsers handle the back button
      on a form thats been properly submitted. Not all browsers use
      the cache directives the same, and I was often typing back, only to
      have some form get reposted. Thats a major pain in the butt. The way
      to deal with that is to have the processor send out a Location header,
      which modifies the browser history so that the post is no longer in
      the history. You back up straight to the unposted form (if its in the
      cache). I've done this to only some forms, since its a bit of a pain
      to rework things so that you can jump ahead to a page that spits out
      the requisite warm fuzzies for the specific operation just completed.
      I've done newproject, joinproject, update user info, newimageid, and
      newimaged_dz forms.
  8. 08 Feb, 2002 2 commits
  9. 18 Jan, 2002 1 commit
  10. 10 Jan, 2002 1 commit
  11. 17 Dec, 2001 1 commit
  12. 11 Dec, 2001 1 commit
  13. 10 Dec, 2001 1 commit
  14. 08 Dec, 2001 1 commit
  15. 06 Dec, 2001 1 commit
  16. 05 Dec, 2001 1 commit
    • Leigh B. Stoller's avatar
      More inventive ways to avoid real work; add password expiration · 3e2bb386
      Leigh B. Stoller authored
      capability. New DB field in the users table (pswd_expires) which is a
      date field that initially gets set to one year after the user account
      is created. When the password is changed via the web form, it gets
      bumped 1 more year into the future *unless* the current uid is
      different from the target_uid (ie: you are changing a password for
      someone else). In that case, the expiration is set to the current
      date, which forces the target user to change his password next time he
      logs in. I've changed the menu/auth code to look for password
      expiration, and when expired the menu options contain just a single
      option to change the password. All other https pages will fail with a
      password expired message. Normal text pages will work of course.
  17. 30 Nov, 2001 1 commit
  18. 12 Nov, 2001 1 commit
    • Leigh B. Stoller's avatar
      Check in search page stuff. I've incorporated the web form from the · 423e25a5
      Leigh B. Stoller authored
      webglimpse dir right into search.php3. Its a simple form and I wanted
      it to look a little different. It also allows me to get rid of the
      FollowSymlinks change I made a couple of days ago. I've added a
      install section that creates a symlink to the webglimpse dir, but
      thats strictly for convenience. The install target cds into that
      directory and reruns the glimpse index (its very quick cause we do not
      have much documentation, perhaps a second. Overall, I do not like the
      webglimpse stuff, but it will do for now.
  19. 07 Nov, 2001 1 commit
  20. 05 Nov, 2001 1 commit
  21. 30 Oct, 2001 1 commit
    • Leigh B. Stoller's avatar
      Minor changes for docwrapper. Add a docwrapper file to each subdir so · 8c4945a1
      Leigh B. Stoller authored
      that relative links work. This old way:
      	<a href="docwrapper.php3?docname=tutorial/nscommands.html">
      throws off relative links cause the actual file (docwrapper.php3) is
      in a different dir than the file loaded. Instead, do this:
      	<a href="tutorial/docwrapper.php3?docname=nscommands.html">
      So loading tutorial/docwrapper.php3 sets the current directory
      properly, and then loads the specified file.
  22. 16 Oct, 2001 1 commit
  23. 05 Sep, 2001 1 commit
  24. 10 Aug, 2001 1 commit
  25. 26 Jun, 2001 2 commits
  26. 25 Jun, 2001 1 commit
  27. 04 Jun, 2001 1 commit
  28. 21 May, 2001 1 commit
  29. 15 May, 2001 1 commit
  30. 10 May, 2001 1 commit
    • Leigh B. Stoller's avatar
      Lots of little changes for sending email to the right places, with · 3285bc3e
      Leigh B. Stoller authored
      proper headers. Split out some of the mail into testbed-logs,
      testbed-ops, and testbed-approval. Added a library for including from
      our perl scripts. Contains a couple of mail helper functions, but will
      hopefully contain more as time goes by.
      Fixed a bug in the web interface that was causing breakage for people
      with multiple accounts. Mac and Jay have noticed this, when logging
      out and trying to join or create a project under a new or different
  31. 04 May, 2001 1 commit
  32. 03 May, 2001 2 commits
  33. 02 May, 2001 1 commit
  34. 19 Apr, 2001 2 commits
  35. 18 Apr, 2001 1 commit