Open Hub
Black Duck Open Hub

 Settings |  Report Duplicate

0
I Use This!
Inactive

Commits : Listings

Analyzed about 12 hours ago. based on code collected about 17 hours ago.
Apr 27, 2023 — Apr 27, 2024
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
forgot to set User.current since it isn't totally removed.
[email protected]
More... over 16 years ago
- domain checks back in
[email protected]
More... over 16 years ago
adding some tests for user and the notification systems
[email protected]
More... over 16 years ago
Merge of branch user_current rev 396-418 into trunk
[email protected]
More... over 16 years ago
possible correction for color issue
[email protected]
More... over 16 years ago
Well even though one line doesn't seem like a big change, I believe that this will be the fix that makes the reply messages not full of escaped html markup. Ticket: 396, 398
[email protected]
More... over 16 years ago
- fix the mail validation logic to save sidebar data for drafts
[email protected]
More... over 16 years ago
unpacking ezcrypto and tzinfo
[email protected]
More... over 16 years ago
Changed report_issue recipients to use the exception_recipients JoyentConfig value
[email protected]
More... over 16 years ago
addresses an exception that came in regarding exporting a person that had a google talk im address.
[email protected]
More... over 16 years ago
graphical suppport for Unflag
[email protected]
More... over 16 years ago
icon support for Flagging
[email protected]
More... over 16 years ago
if the time is nil, then the mailbox wasn't loading and all kinds of other issues were popping up. I added a Message with a nil Date and fixed the failing tests. Hopefully this will get past some of the initial issues we were seeing.
[email protected]
More... over 16 years ago
adding tests from rev 389, 391 back in.
[email protected]
More... over 16 years ago
I am making the executive decision to roll back to rev 378 because I am realizing two things while working on this User.current refactor. 1 - We should not have removed the User.current setting until we are completely done with everything. 2 - This refactor is pretty big that we should work in a branch and then move it into trunk, since the tests do not all pass
[email protected]
More... over 16 years ago
some small refactors
[email protected]
More... over 16 years ago
removing another model reliance on User.current
[email protected]
More... over 16 years ago
Test coverage to ensure proper errors are raised from rev 389
[email protected]
More... over 16 years ago
the only place i see this being used is in the tests -- gone!
[email protected]
More... over 16 years ago
Raise proper errors on nil arguments
[email protected]
More... over 16 years ago
removing User.current from calendar model
[email protected]
More... over 16 years ago
more current_user type changes. These are rooted in the fact that current_user = ... needed to be changed to self.current_user = ...
[email protected]
More... over 16 years ago
moving the find logic to the model.
[email protected]
More... over 16 years ago
unit tests pass again.
[email protected]
More... over 16 years ago
looks like this got removed
[email protected]
More... over 16 years ago
change for comments because the destroy method seemed like a bad hack.
[email protected]
More... over 16 years ago
- Deprecated Organization.current, Domain.current, User.current in views - Changed views to use new methods
[email protected]
More... over 16 years ago
- Deprecated Organization.current, Domain.current, User.current in controllers - Added current_[org,domain,user] methods - Changed controllers to use new methods
[email protected]
More... over 16 years ago
changing User.current to current_user for all of the views.
[email protected]
More... over 16 years ago
changing User.current to current_user in the controllers and helpers
[email protected]
More... over 16 years ago