Hi all. A question about concerns and hope it makes sense: If I include a concern in my model/controller which has the method MyConcern::mymethod! and the model/controller has already a method called "mymethod!", which of the two remains: the concern's method or the model/controller' method?
I've write a "module MyModule.... end" and want to know if it is being known for my app. So I'm not talking about gems, I think.
tubbo: no. The complete story: I'm trying to build an engine following the devise integration pattern, being inspired by this: http://www.toptal.com/ruby-on-rails/rails-engines-in-the-wild-real-world-examples-of-rails-engines-in-action
Hi all. I'm learning about engines (and rails itself) and how to integrate them within the main app. I've found that using decorators you can override engine's controllers, views, etc??tera, as you want. But I would like to write an engine that, conversely, override main app's controllers, views, etc??tera. Does that make sense?
Thanks, let me try: the main app have a controller that do something I would like to do in a different way. Also, this doing things differently implies also differences in views and models.
I have an app that uses devise_ldap_authenticatable. This piece of code: Devise::LDAP::Adapter.get_ldap_param(username,'cn') is taking almost a minute to get answered. I have created an index for the cn field in the ldap without changes in the responde time. Suggentions? Thanks in advance.
workmad3: that actually makes a ldap query, which is taken too long, so I created an index in the ldap server for the field queried.
workmad3: yeah, the index seems to have no impact. Yes, it takes so using devise. ldapsearch answers inmediately
centrx: one posibility is: "class RegistrationsController < Devise::RegistrationsController", and the other is: "class Devise::RegistrationsController < DeviseController"... In the IRB: >> RegistrationsController.class => Class