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

updating from 1.6.0 -> 1.6.1 means that you will need require 'active_directory' even if loaded from Gemfile #1

Open
freibuis opened this issue Jun 4, 2015 · 2 comments

Comments

@freibuis
Copy link

freibuis commented Jun 4, 2015

Hi,

since updating to revision 1.6.1 you will need to use

require 'active_directory'

regardless if you run this from bundle exec

otherwise when you run

ActiveDirectory::Base.setup(settings)

you will get

uninitialized constant ActiveDirectory::Base

this breaks behavior from 1.6.0

@Mazwak
Copy link
Owner

Mazwak commented Jun 4, 2015

Sorry for the inconvenience.
As the gem as no bin, could you tell me what you are trying to exec ?

@freibuis
Copy link
Author

freibuis commented Jun 4, 2015

ok add the gem to you Gemfile require 'active_directory'

add a config or initializer that has the setting for the ActiveDirectory::Base.setup(settings)

bundle exec rails c

ActiveDirectory::User.find(:first, :userprincipalname => "[email protected]")

you will get

uninitialized constant ActiveDirectory::Base

The way around this would be to use require 'active_directory' in side the config or initializer

Thats the problem. 1.6.0 didnt need this. If the gem was in the gem file then it automatically required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants