Decouple from refinerycms-authentication-devise

[bricesanchez]

At this time we have to use Blog at least with refinerycms authentication devise gem : https://github.com/refinery/refinerycms-blog/blob/master/lib/refinery/blog/configuration.rb#L28-L35

We can't use it without an authentication system (like for development or testing).

Perhaps we should be able to disable by default the author feature?

[parndt]

@bricesanchez can't we access authorisation_manager.current_user or whatever that API was?

[parndt]

@bricesanchez I think we should remove the author feature and implement it as purely a string field

[bricesanchez]

I'm ok, we should rethink the author feature. I don't think it should be only a string, i use this feature with refinerycms-teams (Refinery::Team model) instead of Refinery::User. It's very useful.

[parndt]

So do we disable it unless something is specified? Opt-in to feature?

[bricesanchez]

@parndt i think yes.

[parndt]

I had to make a fix so that it would boot in current applications.
The problem is: it makes the build fail because we don't depend on refinerycms-authentication-devise and nor should we

[bricesanchez]

Could we depend on refinerycms-authentication-devise only to run tests ?
And find another solution in the next stable version ?

[parndt]

@bricesanchez I don't think so.. but I have a branch where I attempt to solve this entirely: https://github.com/refinery/refinerycms-blog/compare/refinery-user-coupling

[parndt]

See #449

[marcelotto]

What's the status on this issue? On trying to integrate Refinery with Refinery-Blog in a Spree-app using Spree's authentication system via spree-refinery-authentication instead of refinerycms-authentication-devise I was running in issue #452. Are there any preliminary workarounds I could try to get this setup running?

[bricesanchez]

@marcelotto At this time i manually create the blog initializer before running the extension generator : bricesanchez/spree-refinerycms-test@1e13ebd

[marcelotto]

@bricesanchez Thanks, that helped. 👍

[bricesanchez]

@parndt Should we change this line :
https://github.com/refinery/refinerycms-blog/blob/master/lib/refinery/blog/configuration.rb#L29

 - class_name = @@user_class_name || "Refinery::Authentication::Devise::User"
 + class_name = @@user_class_name || "Refinery::Core::NilUser"

[bricesanchez]

@marcelotto nice to know that there are spree-refinery-authentication users :)

[marcelotto]

A bit too early happy. When trying to create a post, it failed on the collection_select in /app/views/refinery/blog/admin/posts/_form.html.erb, since Spree::User has no username. Could workaround this by extending Spree::User with an appropriate alias:

Spree::User.class_eval do
  alias_attribute :username, :login
end

In a refinerycms-authentication-devise-decoupled solution it would be instrumental to have a config option to set the username attribute.

@bricesanchez spree-refinery-authentication works like a charm, thanks.

[bricesanchez]

Extending Spree::User is the good way.

refinerycms-blog could be have a config to set the username attribute.

Feel free to open a pull request :)

[parndt]

@parndt Should we change this line :
https://github.com/refinery/refinerycms-blog/blob/master/lib/refinery/blog/configuration.rb#L29

• class_name = @@user_class_name || "Refinery::Authentication::Devise::User"
• class_name = @@user_class_name || "Refinery::Core::NilUser"

@bricesanchez Probably? Does it work?

[bricesanchez]

Closed in favor of #459