Create "login" widget

[orchardbot]

rpaquay created: https://orchard.codeplex.com/workitem/16684

Change the login front-end UI to be a widget that can be positioned anywhere

[orchardbot]

rpaquay commented:

Re-triage.

[orchardbot]

@bleroy commented:

Similar to menu widget work.

[orchardbot]

@BenedekFarkas commented:

I've created a fork, the LogOn widget is fully working. Please comment about it, if it's okay, I'll make the pull request: http://orchard.codeplex.com/SourceControl/network/forks/nightwolf226/16684LogOnWidget

[orchardbot]

@BenedekFarkas commented:

I've sent a pull request for the fork.

[orchardbot]

@agriffard commented:

Try this module : http://gallery.orchardproject.net/List/Modules/Orchard.Module.Contrib.Mod.AccountWidgets http://modaccountwidgets.codeplex.com/

[orchardbot]

@jetski5822 commented:

Looking for the pull request? Has it disappeared?

[Jetski5822]

@BenedekFarkas @agriffard @NogginBox Do we need this any more? Can we not just use a Shape Widget and render the shape Logon?

[Piedone]

@Jetski5822 Good point, but for ease of use I'd still add a login widget. @BenedekFarkas ?

[sfmskywalker]

You can do this today with 1.9 by creating a Dynamic Forms form and setting up a simple workflow. There is a SignInUser activity available (see the "Login" section here: http://www.ideliverable.com/blog/customizing-user-registration-and-login-with-dynamic-forms-and-workflows). Since we also have a LayoutWidget, you could do it as a widget just as easily.

[Piedone]

Now explain this to a user who "just wants to display a login form to the right" :-). We're repeatedly getting into the situation where users want a very specific feature with a very limited scope (this issue was among the top voted ones!) and what we can offer is a developer-level solution like in this case. Or we re-implement something just for the sake of ease of use (like in the comment notification e-mail case, which can also be done with Workflows but now we have a checkbox for it and thus duplicated functionality).

I still think that the ideal solution would be to build simplified abstractions for the most-wanted setups using existing complex services. E.g. there would be a login widget that you can simply add but in the background it could do e.g. what you described @sfmskywalker . Or have a checkbox to get comment notifications for your content items that in the background would create an appropriate workflow.

This way we have simple to use features that cover the most used cases but we have no duplicated functionality and for power users there is still unlimited customizability.

What do you think?

[sfmskywalker]

I still think that the ideal solution would be to build simplified abstractions for the most-wanted setups using existing complex services

That's exactly what I think - make it simple for the average user as a layer on top of lower level things, so that more advanced users can tweak and further configure the setup.

[sfmskywalker]

This particular feature could be implemented as a recipe that performs the following steps:

1. Define a new widget content type called LoginWidget which has a LayoutPart attached and a default JSON string representing a Form element (named "Login"), Username element, Password element and a Signin button element.
2. Adds a workflow that handles the submit event for the form "Login".

The result: a very simple to use Login widget that is highly customizable if needed.

[Piedone]

This would be great!

[dcinzona]

+1