Orphaned Activities Bug
Reported by Scott Miller | May 6th, 2009 @ 01:09 PM | in 0.9.7 "Steinitz"
It appears that if user1 views a contact, and then user2 deletes that contact, it creates an orphaned activity record, which throws an error and prevents user1 from accessing the system. The error is a nil object in _recent.html.haml for user1.
Comments and changes to this ticket
-
-
Mike Dvorkin May 6th, 2009 @ 03:41 PM
- State changed from “new” to “open”
(from [f945fa7174f324537464d86054bd3d00270f1eb0]) If somebody deletes an object it gets removed from everyone's recently viewed items list [#32 state:open] http://github.com/michaeldv/fat_...
-
Mike Dvorkin May 6th, 2009 @ 03:52 PM
Previous commit fixes the bug.
We should also handle an issue when user2 deletes the object, and user1 clicks on object's name from recently viewed items. Now it generates:
NoMethodError in Leads#show
Showing app/views/leads/show.html.haml where line #5 raised:
You have a nil object when you didn't expect it! The error occurred while evaluating nil.status
We should basically safeguard object#show to make sure we gracefully handle requests to show deleted objects.
-
Mike Dvorkin May 6th, 2009 @ 07:12 PM
- State changed from “open” to “resolved”
I'm opeining a new ticket since it's a global issue that affects all core objects (see #34).
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Ruby on Rails CRM platform for Web 2.0 and beyond
People watching this ticket
Mike Dvorkin
Scott Miller
Tags
Referenced by
-
32
Orphaned Activities Bug
(from [f945fa7174f324537464d86054bd3d00270f1eb0]) If some...
-
34
Gracefully handle missing objects and objects with restricted access
Also see #32 that uncovered this issue.