Closed Atastor closed 6 years ago
Ok, I got a solution, wrapping it up and will post it then with a pull request; won't be before Sunday evening, though.
I added configurable options describing the tables used for Roles
and RolesUsers
to refinerycms-authentication-devise
Hi, I am still struggling with migrating my pre-refinery-authentication-devise application. I described initial trouble in https://github.com/refinery/refinerycms-authentication-devise/issues/6
My current problem ist the handling of the existing refinery tables, which of course have the old names, i.e. former
refinery_roles
now is expected to berefinery_authentication_devise_roles
, formerrefinery_roles_users
now is expected to berefinery_authentication_devise_roles_users
and so on.My current attempt is, to tell each and every refinery model in question that it should use a table with the old name. Looking for an in-rails solution I am trying the following:
self.table_name="old_table_name"
to the class_eval of the decorator.This gets rid of the initial rails/refinerycms complaints for the first model popping up, aka
Refinery::Authentication::Devise::Role
; the decoratorrefinery_authentication_devise_role_decorator.rb
contains the following code:And, as stated, this lets me carry on with the second refinerycms model, namely
Refinery::Authentication::Devise::RolesUsers
; the decoratorrefinery_authentication_devise_roles_users_decorator.rb
contains the following code:Then, accessing the login-page fails with
I will gladly receive any suggestions about
Thanks a lot in advance Michael