New Wordpress Plugin Beta

[Forest]

I just posted a working beta of the new version of the Janrain Engage
Wordpress plugin.
This new plugin offers support for providers that do not return an
email address by asking for the email address.
I chose to rewrite the whole project to catch up with the many changes
in WP 3.
One major reason for this release was to get Twitter sign in restored
to WP. Please note http://status.twitter.com/

Read the Readme included in the package. Test this code at your own
risk.

http://wordpress.org/extend/plugins/rpx/download/
Download the "Development Version"

Warnings:
I have only tested this as a fresh install setup. I kept the option
names the same as the previous branch so it might work on a running
setup.
There is no attempt to confirm the email address entered.

Missing:
The ability to change providers for an existing user.
The deactivate cleanup hooks.
redirect_to support

[Dr P Fenderson]

Seems to be working over here.
Only thing I cannot figure out is how to get it to show up manually in
my comments section. :-/
Seems to not be inserting itself automatically any longer.

On Jul 19, 3:25 pm, Forest <for...@janrain.com> wrote:
> I just posted a working beta of the new version of the Janrain Engage
> Wordpress plugin.
> This new plugin offers support for providers that do not return an
> email address by asking for the email address.
> I chose to rewrite the whole project to catch up with the many changes
> in WP 3.
> One major reason for this release was to get Twitter sign in restored

> to WP. Please notehttp://status.twitter.com/

[Forest]

Thanks for the feedback. If this is a feature you need I can add it.
I would like to get these feature requests as fresh features and
ignore the way it used to work.
How would you like it to work?

[asshu]

I posted similar topics relating to wordpress 3.0 and waiting for
reply.

[asshu]

Is it really works well for wordpress 3.0? This message is appearing
at the top of plugin page :
"Warning: This plugin has not been marked as compatible with your
version of WordPress."

On Jul 20, 3:25 am, Forest <for...@janrain.com> wrote:
> I just posted a working beta of the new version of the Janrain Engage
> Wordpress plugin.
> This new plugin offers support for providers that do not return an
> email address by asking for the email address.
> I chose to rewrite the whole project to catch up with the many changes
> in WP 3.
> One major reason for this release was to get Twitter sign in restored

> to WP. Please notehttp://status.twitter.com/

[Dr P Fenderson]

I REALLY like the new way you have of dealing with the login screen.
The little icons at the bottom are perfect! Way better than the auto-
inserting a 400px div like before.

If possible, having it work the same way with comments would be great
- autoinserting a little "Log in to comment with (little squares)" or
"Log in with (little squares)" above the comments...perhaps below the
user info fields.

It would be even better if there was a template tag I could call for
all the different parts of the process...One for the whole "Log in
with..." or just the squares, or just the log-in modal window.

That way I could insert the Janrain login wherever I like.

[Dr P Fenderson]

Would also love to be able to customize what icons are used. Perhaps
with template tags again.
For example: janrain_login(facebook,'ALT TEXT','http://pathtoicon/
icon.png')

or something...
Customization tags are king.

On Jul 21, 9:36 am, Forest <for...@janrain.com> wrote:

[Andrew Cebulski]

Great plugin...glad I found it. One question though...

Would it be possible to make it so the identifiers I have listed here:
https://rpxnow.com/account/settings

are all to be linked to one account on my Wordpress blog?

Right now it seems it'll only link your accounts if you have the same
primary email address associated with each identifier.

On Jul 19, 6:25 pm, Forest <for...@janrain.com> wrote:
> I just posted a working beta of the new version of the Janrain EngageWordpressplugin.
> This new plugin offers support for providers that do not return an
> email address by asking for the email address.
> I chose to rewrite the whole project to catch up with the many changes
> in WP 3.
> One major reason for this release was to get Twitter sign in restored

> to WP. Please notehttp://status.twitter.com/

[Basford, Forest]

Development versions do not get the meta tags processed to enable version compatibility information.

The current Development Version on the Other Versions page was written just for Wordpress 3.

--
You received this message because you are subscribed to the Google Groups "Janrain Developers" group.
To post to this group, send email to rpx-dev...@googlegroups.com.
To unsubscribe from this group, send email to rpx-developer...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rpx-developers?hl=en.

[Basford, Forest]

Great feedback. 

I am thinking of making an action for creating a set of sign on icons and another for just a link.

Then you would just call <?php do_action('rpx_signon_icons'); ?> or <?php do_action('rpx_signon_modal'); ?> in your template.

This would allow passing variables back to control the resulting output. Like <?php do_action('rpx_signon_icons', 2, 3); ?> where this would make the icon grid two columns and three rows.

[Basford, Forest]

Thanks for the feedback.

The current plugin just creates an account if there is no account with this email address already signed up on Wordpress.

The final release of this version of the plugin will not use email as a primary or secondary key. Instead it will just attempt to collect a valid email address as a requirement of account creation. 

So if you sign on with Facebook and facebook delivers us...@email.com as the address and it is not in use it will trust this and create the account. If you come back and sign in with linkedin and it delivers us...@email.com as the address you will be prompted to enter a unique valid email address to create a second account. If you do this you will receive a validation email and if you click the link in this you will have two accounts.

Account mapping is a future version feature. The release of this version will include a release of planned features for the next version in the documentation as well a changelog.

[Dr P Fenderson]

That is absolutely perfect.

As a theme designer, having options like that make this plugin a must-have.

You description of the planned login/email process sounds keen as well. Looking forward to it.

Will you be keeping this thread updated as new development/official versions come out?

[SocialApples]

Hey Forest,

Just from my personal testing, I get kicked back to the login area
with an error saying that the login I'm using doesn't have an email
address:

This account did not provide an email address.
Please update the account with that service or use another service.

http://socialapples.com/wp-login.php?rpxmsg=noemail

It's specifically happening with Twitter. I've checked the settings
on the twitter app to make sure they're all as they should be... but I
still get this error even though I have an email account specified for
Twitter. Is there a way to get rid of the email check and I'm just
missing it? Or is there something else that I've messed up?

[Basford, Forest]

It looks like you are using the version 0.3.0 or 0.3.1 the beta is the Development Version.

The limitation that lead to the error you are seeing is described in the documentation for the current plugin.

[Lone0001]

Sorry for replying so late on this one but I just got this version
installed and the rpx now seems to work fine with my Wordpress site,
thanks. :)

On Jul 26, 11:25 am, "Basford, Forest" <for...@janrain.com> wrote:
> It looks like you are using the version 0.3.0 or 0.3.1 the beta is the
> Development Version.
> The limitation that lead to the error you are seeing is described in the
> documentation for the current plugin.
>

> On Sat, Jul 24, 2010 at 1:38 AM, SocialApples <carr...@gmail.com> wrote:
> > Hey Forest,
>
> > Just from my personal testing, I get kicked back to the login area
> > with an error saying that the login I'm using doesn't have an email
> > address:
>
> > This account did not provide an email address.
> > Please update the account with that service or use another service.
>
> >http://socialapples.com/wp-login.php?rpxmsg=noemail
>
> > It's specifically happening with Twitter.  I've checked the settings
> > on the twitter app to make sure they're all as they should be... but I
> > still get this error even though I have an email account specified for
> > Twitter.  Is there a way to get rid of the email check and I'm just
> > missing it?  Or is there something else that I've messed up?
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Janrain Developers" group.
> > To post to this group, send email to rpx-dev...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > rpx-developer...@googlegroups.com<rpx-developers%2Bunsu...@googlegroups.com>
> > .

[Moody Robot]

Thanks for your reply to my post about the rpx_comment_hint(false).
I do think you should incorporate the option to manually or
automatically inserting the hints. By doing so, you give the option to
people who don't have enough php coding experience (automatically), or
do (manually), to fully integrate your plugin into their blogs. Not
only on the wp-login.php page but also anywhere else on their site
(comment forms and sidebars - as widget, maybe), increasing the
usability and usefulness of your plugin, therefore increasing the
amount of new blog user sign-ins (therefore more exposure for Janrain
services), which is ultimately one of Janrain's goals, if I'm not
mistaken.
Besides, integrating Janrain Engage using an iframe or modal overlay
should be a selectable option, regardless of where the integration is
done. This would increase the flexibility of your plugin to blend
better with any kind of theme people use on their blogs.
BTW, getting Twitter sign in restored in this new version of the
plugin, as you state, was a wonderful idea. And hopefully replacing
what you list as missing, would be too.
Sorry. I know this is too much to ask, but you did mention you want to
hear about feature requests. Thank you very much.

On Jul 19, 5:25 pm, Forest <for...@janrain.com> wrote:
> I just posted a working beta of the new version of the Janrain Engage
> Wordpress plugin.
> This new plugin offers support for providers that do not return an
> email address by asking for the email address.
> I chose to rewrite the whole project to catch up with the many changes
> in WP 3.
> One major reason for this release was to get Twitter sign in restored

> to WP. Please notehttp://status.twitter.com/

[Forest]

Hi,

I committed a new update to the Wordpress Plugin to improve security.
As the new guy here at Janrain (I started this code my third day
here)
I did not know that it was against best practices to reuse the token
and
specifically to never pass the token in a way that revealed it.
The current commit of the beta does not do this. Instead it uses
an internally created one time use session id.
This update also enables use of the new Engage one-time use token.

- Forest

On Jul 19, 3:25 pm, Forest <for...@janrain.com> wrote:
> I just posted a workingbetaof the new version of the Janrain EngageWordpressplugin.

> This new plugin offers support for providers that do not return an
> email address by asking for the email address.
> I chose to rewrite the whole project to catch up with the many changes
> in WP 3.
> One major reason for this release was to get Twitter sign in restored

> to WP. Please notehttp://status.twitter.com/

[Forest]

Ok another new commit.
This one finalizes the end user UI elements.
Tested in the latest Firefox, Safari, Chrome, and IE8.
Keep up the feedback.
I know this might not be an update you asked for but I add only one
feature per update so I will get to your feature someday.

-- Forest

On Jul 19, 3:25 pm, Forest <for...@janrain.com> wrote:

> I just posted a working beta of the new version of the Janrain EngageWordpressplugin.
> This new plugin offers support for providers that do not return an
> email address by asking for the email address.
> I chose to rewrite the whole project to catch up with the many changes
> in WP 3.
> One major reason for this release was to get Twitter sign in restored

> to WP. Please notehttp://status.twitter.com/

[Anwar Wilkerson]

I installed the developer model on to my wordpress journal because
another user insisted that it would fix my problem. Well now I'm
having a new problem. The login to use the Jarain is not even showing
up on the login page. I checked my setting and they are correct, I
checked the admin panel and the setting just show where to put in a
api key and nothing more. Nothing comes up after I save the changes.
I have anyone can register as checked off. the plugin still worked
with that setting as it was in the older vers. My site is www.darkprincearmon.com

On Jul 19, 6:25 pm, Forest <for...@janrain.com> wrote:
> I just posted a working beta of the new version of the Janrain Engage
> Wordpress plugin.
> This new plugin offers support for providers that do not return an
> email address by asking for the email address.
> I chose to rewrite the whole project to catch up with the many changes
> in WP 3.
> One major reason for this release was to get Twitter sign in restored

> to WP. Please notehttp://status.twitter.com/

[Baptiste M (FrAndroid)]

Hello,

I checked the developpement version, interesting, but ...
In can never login with provider that doens't provide a e-mail
(twitter, linked-in).

It seems that that user is always locked in the database and so he can
never login even after click on the verification mail's link.

Thanks for making evolve this plugin !!

Baptiste
(small request: can you pass the widget as a class in order to put in
in severall place ?)

[Scott]

With the latest development version there is no automatic integration
with the Wordpress login and commenting mechanism. Is there something
we can do to enable this, or do we just have to wait until the
official release?

Thanks.

[Basford, Forest]

If you have it setup it should integrate with login/posts (comment social share is pending). Did you look at Settings->Janrain Engage?

--
You received this message because you are subscribed to the Google Groups "Janrain Developers" group.
To post to this group, send email to rpx-dev...@googlegroups.com.

To unsubscribe from this group, send email to rpx-developer...@googlegroups.com.

[Dr P Fenderson]

I have it setup, but I only see it on the login screen. It does not appear in my comments. Is there some way to enable it? A template shortcode or something?

[Basford, Forest]

Are you looking for social sharing or login?
You can make it show a login link for comments if you mark login as
required for comments. Also look in widgets for the Janrain Engage
widget. Currently social sharing of comments is scheduled for release
but not as a required feature.

On Tuesday, August 31, 2010, Dr P Fenderson

--

<http://www.janrain.com/>

*Forest Basford* | *Technical Support Engineer*
| E: for...@janrain.com
| W: 503-488-6754 x54 | F: 888-267-9025
www.janrain.com <http://bit.ly/cKKudR> | Follow: [image:
Facebook]<http://bit.ly/9CGHdf>
[image: Twitter] <http://bit.ly/9umxlK> [image: LinkedIn]<http://bit.ly/a7WZMC>
[image: Janrain Blog] <http://blog.janrain.com/>

[Bo Crawford]

Probably a dumb question, but how do we get an API key? I do not see
a link to "get an API key"...

On Aug 31, 7:19 pm, "Basford, Forest" <for...@janrain.com> wrote:
> Are you looking for social sharing or login?
> You can make it show a login link for comments if you mark login as
> required for comments. Also look in widgets for the Janrain Engage
> widget. Currently social sharing of comments is scheduled for release
> but not as a required feature.
>
> On Tuesday, August 31, 2010, Dr P Fenderson
>
>
>
> <drpfender...@pinkonbrown.org> wrote:
> > I have it setup, but I only see it on the login screen. It does not appear in my comments. Is there some way to enable it? A template shortcode or something?
>
> > On Tue, Aug 31, 2010 at 5:03 PM, Basford, Forest <for...@janrain.com> wrote:
> > If you have it setup it should integrate with login/posts (comment social share is pending). Did you look at Settings->Janrain Engage?
>

> > On Tue, Aug 31, 2010 at 3:32 PM, Scott <scatterli...@gmail.com> wrote:
> > With the latest development version there is no automatic integration
> > with the Wordpress login and commenting mechanism. Is there something
> > we can do to enable this, or do we just have to wait until the
> > official release?
>
> > Thanks.
>
> > --
> > You received this message because you are subscribed to the Google Groups "Janrain Developers" group.
> > To post to this group, send email to rpx-dev...@googlegroups.com.
> > To unsubscribe from this group, send email to rpx-developer...@googlegroups.com.

> > For more options, visit this group athttp://groups.google.com/group/rpx-developers?hl=en.

>
> > --
> > You received this message because you are subscribed to the Google Groups "Janrain Developers" group.
> > To post to this group, send email to rpx-dev...@googlegroups.com.
> > To unsubscribe from this group, send email to rpx-developer...@googlegroups.com.

> > For more options, visit this group athttp://groups.google.com/group/rpx-developers?hl=en.

>
> > --
> > You received this message because you are subscribed to the Google Groups "Janrain Developers" group.
> > To post to this group, send email to rpx-dev...@googlegroups.com.
> > To unsubscribe from this group, send email to rpx-developer...@googlegroups.com.

> > For more options, visit this group athttp://groups.google.com/group/rpx-developers?hl=en.

>
> --
>
> <http://www.janrain.com/>
>
> *Forest Basford* | *Technical Support Engineer*
> | E: for...@janrain.com

> | W:503-488-6754begin_of_the_skype_highlighting              503-488-6754      end_of_the_skype_highlightingx54 | F: 888-267-9025www.janrain.com<http://bit.ly/cKKudR> | Follow: [image:

[Basford, Forest]

Adding the link is on my todo before finalizing this release. Just go to http://rpxnow.com/ and sign up.

[Scott]

Okay. I think I understand now. Thank you so much for your development
and support on this forum!

Here is my feedback:

1) I was missing the step of "requiring login for comments". This
should be added to the Readme.
2) I see the social link ("share"), even when I have the setting
turned off.
3) I don't like that login is required for comments. I am using this
for a blog where maybe 50% of the people will not want to login just
to post a comment. I would hate to lose half of the people in order to
offer Janrain to the rest.

Smaller points:
4) At first blush it makes me uncomfortable that I have to allow
anyone to register. Time will tell if this is actually a problem.
5) I have never liked the way that the "Or log in with" section with
the line of icons shows providers that I do not have enabled. I wish
it would only show the icons of the services I have selected. It would
be fine even if I had to select the icons separately in the plugin
settings.
6) I wish that for the line of icons, clicking on one of them would
directly start the login with that provider, rather than launching the
modal overlay as it currently does.

Thanks again.
--
Scott

[Basford, Forest]

Scott,

Thanks for the detailed feedback. 

I plan to improve both the ReadMe and the integrated prompts before release.

Is it acceptable to use the widget to offer log in without needing to force log in on comments?

If not I will look into adding it on the comments form even if log in is not required.

Share should not show up if it's disabled, this is a defect that I will correct.

Currently I have no API call that returns a list of enabled providers to build a custom icon bar.

The ability to launch a provider based on the icon clicked will come in a future version of Engage.

Currently this can only be achieved via Pro and the Custom UI API.

--

[Scott]

Forest,

I don't have a strong preference yet about how to offer login when
login is not required. The old way of adding in a link that would pop
up a widget was fine.

Thanks again.
--
Scott

[Dr P Fenderson]

Forest,

I would LOVE to be able to add it to the comment form, regardless of the status of "log in required".

A template tag would be best.

Thanks again.
--
Scott

[Bo Crawford]

Another dumb question: Is there a help file giving more specific
instructions for the token url step?

Sorry---total rookie here.