Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloning PFT with Ruby 2.0 gives NoMethodError #141

Closed
robkooper opened this issue Sep 8, 2014 · 4 comments
Closed

Cloning PFT with Ruby 2.0 gives NoMethodError #141

robkooper opened this issue Sep 8, 2014 · 4 comments
Labels

Comments

@robkooper
Copy link
Member

When using Ruby 2.0,

When cloning a pft record you will get the following error : NoMethodError: undefined method 'insert_record' for #<Array:0x000000052541f8> from,

This is due to the fact that ruby 2.0 does not have that function anymore, or something else. See also rails/rails#11026.

Upgrading from rails 3.0.18 to 3.2.19 (latest in 3 series) will solve this problem, but create new ones: 1) rjs will not work and opening of species etc will not work.

@gsrohde
Copy link
Contributor

gsrohde commented Sep 10, 2014

We officially only support BetyDB running under Ruby 1.9.1. That said, I have for some time been wanting to upgrade our Rails version to at least 3.2.* and would probably upgrade the official Ruby version at the same time. This, however, has been a pretty low-priority to-do. But if you see a compelling reason to upgrade sooner rather than later--something that I hope would be more compelling than "I don't want to bother installing Ruby 1.9.1"--be all means make an issue for it and give your reasons.

@robkooper
Copy link
Member Author

Issue is created so people are away of this, documentation says ruby > 1.9.1 but should probably include < 2.0.

@dlebauer dlebauer changed the title ruby 2.0 and gems Cloning PFT with Ruby 2.0 gives NoMethodError Sep 16, 2014
@dlebauer
Copy link
Member

updated documentation to reflect that we only support 1.9.1 <= Ruby < 2.0.

@gsrohde
Copy link
Contributor

gsrohde commented May 12, 2015

Not an issue (I think!)--we now officially support Ruby version 2.1.5, but anything >= 1.9.3 probably works.

@gsrohde gsrohde closed this as completed May 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants