forked from delynn/userstamp
-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathCHANGELOG
More file actions
39 lines (30 loc) · 1.8 KB
/
CHANGELOG
File metadata and controls
39 lines (30 loc) · 1.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
2.0.3 (2-1-2013)
* [robotex82] - Fixed issue where capitalized user classnames would fail to work
* Includes many fixed found in https://github.com/insphire/userstamp
* Updated to work in rails 3.2.11
* Autodetection of the fields used in stamping (ex. updated_by vs updater_id) added. This also
removes the dependency on using the acts_as_paranoid gem to managed a deleter. Either a
deleted_by or an deleter_id will now be updated without further configuration.
* Rebuild entire test platform to use rspec. Includes full testing of controller integrations.
2.0 (2-17-2008)
* [Ben Wyrosdick] - Added a migration helper that gives migration scripts a <tt>userstamps</tt>
method.
* [Marshall Roch] - Stamping can be temporarily turned off using the 'without_stamps' class
method.
Example:
Post.without_stamps do
post = Post.find(params[:id])
post.update_attributes(params[:post])
post.save
end
* Models that should receive updates made by 'stampers' now use the acts_as_stampable class
method. This sets up the belongs_to relationships and also injects private methods for use by
the individual callback filter methods.
* Models that are responsible for updating now use the acts_as_stamper class method. This
injects the stamper= and stamper methods that are thread safe and should be updated per
request by a controller.
* The Userstamp module is now meant to be included with one of your project's controllers (the
Application Controller is recommended). It creates a before filter called 'set_stampers' that
is responsible for setting all the current Stampers.
1.0 (01-18-2006)
* Initial Release