Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-35359

Social Bookmarks hook; social links need an update


    • Type: Regression Bug
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: 6.1.20 EE GA2, 6.1.30 EE GA3, 6.2.0 CE M6
    • Fix Version/s: 6.2.0 CE RC1
    • Labels:
    • Environment:
      Tomcat 7.0.34 + MySQL 5.5. Portal 6.1.x EE GIT ID: f32b5998dd74e93516bb14614ac6646db5e5d42d.
      Tomcat 7.0.21 + MySQL 5.5. Portal 6.1.20 EE GA2
      Tomcat 7.0.34 + MySQL 5.5. Portal 6.2.x GIT ID: 665737d65ad65dff93ac8ef5435e11c9bd738248.
    • Fix Priority:


      When the social bookmark hook is applied, some of the links don't work and need to be updated.

      Steps to reproduce:

      1. Deploy the social bookmarks hook
      2. Start Liferay
      3. Add a blogs portlet and Blogs entry
      4. Click each of the social bookmark links and sign in and post "Blogs Entry" including the links: twitter, facebook, google plus, blink, delicious, digg, evernote, newsvine, reddit, slashdot, stumbleupon, technorati, and tuenti.
      5. Assert that the following social links fail: google plus, delicious, digg, evernote, newsvine, and tuenti

      Expected result:
      The links should take the user to the correct login page and the user should be able to post.

      Actual result:
      For the failing links, the user is unable to sign on and/or cannot post. Details below:

      1. google plus fails = able to sign in but button doesn't work, error = https://support.google.com/plus/answer/1199142?p=plusone_button_error&rd=1
      2. delicious fails = once the user is signed on the page is blank
      3. digg fails = and "invalid url" message displays
      4. evernote fails = invalid pw/login -probably just needs to be updated
      5. newsvine fails = doesn't take the user to the right login screen, but it is possible to workaround and sign in
      6. tuenti fails= login doesn't work and says "The URL you are trying to share is incorrect or does not exist." But a workaround works if you go to the actual site and login and post from there.




            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created:
                Days since last comment:
                6 years, 41 weeks, 4 days ago


                Version Package
                6.2.0 CE RC1