Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums
  • Feature tour
    Feature tour

Content

You are here:
  1. Forums
  2. General discussion

NoMethodError "clear_attribute_changes"

Added by Michael Heseltine about 9 years ago

Im running OP 4.2.7. Now I’m trying to add a new or existing version entry to an already existing work package. I get this result:

NoMethodError (undefined method `clear_attribute_changes' for #<WorkPackage:0x007f102dd3b258>):
  lib/plugins/acts_as_customizable/lib/acts_as_customizable.rb:140:in `method_missing'
  app/models/work_package.rb:443:in `update_by!'
  app/services/update_work_package_service.rb:42:in `update'
  app/controllers/work_packages_controller.rb:186:in `update'
  app/middleware/params_parser_with_exclusion.rb:40:in `call'

What is the problem, and how can I get this to work?


Replies (1)

RE: NoMethodError "clear_attribute_changes" - Added by Oliver Günther about 9 years ago

Hi Michael,

the issue resulted from a breaking change in a Rails upgrade of one of our plugins during the development of the next stable version (5.0).
It should be fixed when you re-run bundle install on the release/4.2 branch.

There are two relevant work packages that contain more information:
https://community.openproject.org/work_packages/21701
https://community.openproject.org/work_packages/21647

Best,
Oliver Günther

  • (1 - 1/1)
Loading...