What's the secret to creating a migration for my extension that changes the data yet doesn't trigger the UserActionObserver?
I already figured out that I need to set MyClass.record_timestamps = false so that I don't artificially change the updated_at field, but changing a value and saving that record still causes the updated_by field to loose the user_id since migrations don't have any user assigned. What am I missing? -Chris _______________________________________________ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
