config/effective_logging.rb in effective_logging-3.0.13 vs config/effective_logging.rb in effective_logging-3.1.0

- old
+ new

@@ -1,39 +1,13 @@ EffectiveLogging.setup do |config| # Configure Database Tables config.logs_table_name = :logs - # Authorization Method - # - # This method is called by all controller actions with the appropriate action and resource - # If the method returns false, an Effective::AccessDenied Error will be raised (see README.md for complete info) - # - # Use via Proc (and with CanCan): - # config.authorization_method = Proc.new { |controller, action, resource| can?(action, resource) } - # - # Use via custom method: - # config.authorization_method = :my_authorization_method - # - # And then in your application_controller.rb: - # - # def my_authorization_method(action, resource) - # current_user.is?(:admin) - # end - # - # Or disable the check completely: - # config.authorization_method = false - config.authorization_method = Proc.new { |controller, action, resource| authorize!(action, resource) } # CanCanCan - # Admin Screens Layout Settings - config.layout = 'application' # All EffectiveLogging controllers will use this layout + # config.layout = { application: 'application', admin: 'admin' } - # config.layout = { - # logs: 'application', - # admin_logs: 'admin', - # } - # EffectiveLogger.info('my message') macros - # The following statuses are already present: info, success, error, view, change, email, sign_in, sign_out + # The following exist: info, success, error, view, change, download, email, sign_in, sign_out # Add more here config.additional_statuses = [] ######################################### #### Automatic Logging Functionality ####