Sunday, January 27, 2013

My answer to "linking linkedin accounts"

This is my answer to a Question on Support site for LampCMS project


I know. I just found yesterday about changes to LinkedIN API. I wrote an answer about that, here:
http://support.lampcms.com/viewquestion/quest2274/LinkedIn-posts-do-not-work

Basically LinkedIN did not provide email address when user connects with LInkedIN API, but after the recent changes to their API they started providing email address.

I am making changes to the logic so that we can detect (using email address) when existing user is adding a LinkedIn account.

Saturday, January 26, 2013

My answer to "Search AutoComplete Behavior Broken?, Inconsistant with Code Comments"

This is my answer to a Question on Support site for LampCMS project


OK, I just looked at the javascript in qa.js again and it looks like it's not a bug
The behavior that you described (in the comments) applies only to autocomplete in the "title" of the questions form.
When you asking a new questions there is another auto-complete form that searches for similar questions as you typing the title of your question. That autocomplete will take you to the question when you click on one of the suggested results.

The search form's autocomplete just enters the suggested results into the search form. It was always working like that, it's not a bug.

There is a third autocomplete - for the tags form on the "ask question" form. That one inserts suggested tags into the tags field.

My answer to "LinkedIn posts do not work"

This is my answer to a Question on Support site for LampCMS project


So it turned out that LinkedIn has updated their oauth based authentication/authorization API
It now requires to ask for specific permissions. I am already working on updating our LinkedIN integration script.

The one good news about this is that now LinkedIN shares user's email address with the API client. So basically the popup permission window tells user that the Applications wants to access their profile, get their email address and post to LinkedIN on their behalf. User can agree or decline.

Having email address provided by the API makes it easier to register new user - we no longer need to use the extra step that we used before to ask user for their email address right after the Join with LinkedIN was completed.

Also knowing the email address during the Sign In with Linked IN can help determine if the user with this email address already registered on our site, in which case we will just connect their existing account with their LinkedIN account.

I'm working on having the updates ready. Will probably take about a week to make changes and test them.

Friday, January 25, 2013

My answer to "LinkedIn posts do not work"

This is my answer to a Question on Support site for LampCMS project


Thank you for this update. I will test this fix and if it works will push changes to github

Sunday, January 13, 2013

My answer to "Can't login with ID/PWD and can't change password"

This is my answer to a Question on Support site for LampCMS project


The fixed version has been pushed to github