[JBoss JIRA] (GTNPORTAL-3085) Responsive Community Portlet doesn't work after ajax refresh
by Matt Wringe (JIRA)
Matt Wringe created GTNPORTAL-3085:
--------------------------------------
Summary: Responsive Community Portlet doesn't work after ajax refresh
Key: GTNPORTAL-3085
URL: https://issues.jboss.org/browse/GTNPORTAL-3085
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Mobile
Reporter: Matt Wringe
Assignee: Viliam Rockai
The responsive community portlet doesn't work after an ajax page refresh. Same issue as we have had with the header/footer and nav portlets :( Really wish a more universal approach could be used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (GTNPORTAL-3082) OAuth buggy when facebook users don't have 'username'
by Tomas Kyjovsky (JIRA)
Tomas Kyjovsky created GTNPORTAL-3082:
-----------------------------------------
Summary: OAuth buggy when facebook users don't have 'username'
Key: GTNPORTAL-3082
URL: https://issues.jboss.org/browse/GTNPORTAL-3082
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.6.0.Beta02
Reporter: Tomas Kyjovsky
OAuth integration is buggy when facebook users don't have 'username' attribute set (test users, unactivated/unverified accounts).
1. follow instructions for facebook oauth integration https://docs.jboss.org/author/display/GTNPORTAL36/Facebook
2. additionally create 2+ test users for the created app: Settings --> Developer Roles --> Test users
Facebook generates a "Switch to" link for each test user, like: https://www.facebook.com/platform/test_account_login.php?user_id=10000601...
3. login to FB as test user A
4. login to gatein via fb and register new user
Expected: Newly registered gatein account should be linked to FB account of user A.
Actual: Gatein account isn't linked to FB account. After attempting to link again manually portal indicates success:
"Social network "Facebook" connected for user "A"."
But the accounts still aren't linked.
5. logout user A from FB, logout from gatein
6. login to FB as test user B
7. login to gatein via FB
Expected: A registration dialog should be displayed with values pre-filled for user B.
Actual: Gatein automatically logs in previously created user A - even if user B is currently logged in FB (user A is not).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (GTNPORTAL-3080) Change PicketLinkIDMOrganizationServiceImpl.recoverFromIDMError method to include Exception
by Martin Weiler (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3080?page=com.atlassian.jira.pl... ]
Martin Weiler updated GTNPORTAL-3080:
-------------------------------------
Git Pull Request: https://github.com/gatein/gatein-portal/pull/501
> Change PicketLinkIDMOrganizationServiceImpl.recoverFromIDMError method to include Exception
> -------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3080
> URL: https://issues.jboss.org/browse/GTNPORTAL-3080
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Identity integration
> Affects Versions: 3.6.0.Beta02
> Reporter: Martin Weiler
> Assignee: Marek Posolda
> Fix For: 3.6.0.Final
>
>
> PicketlinkIDMOrganizationServiceImpl.recoverFromIDMError() method was added with GTNPORTAL-2928 changes to have a single place to handle exceptions at the IDM layer.
> As the code in the upper layer (WebUI classes) is not prepared to handle the exception, the current implementation does a rollback of the failed transaction, and starts a new one afterwards.
> In a custom implementation using the IDM layer, it could be desirable to let the exception bubble up the stack instead. For this, users can create subclass of PicketlinkIDMOrganizationServiceImpl and
> override method recoverFromIDMError() with their own code for recovery
> error and rollback of their own transaction abstraction.
> To access the original exception for some reason, the signature of recoverFromIDMError() should be changed to include the exception, so the
> signature will be "recoverFromIDMError(Exception e)" .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (GTNPORTAL-3080) Change PicketLinkIDMOrganizationServiceImpl.recoverFromIDMError method to include Exception
by Martin Weiler (JIRA)
Martin Weiler created GTNPORTAL-3080:
----------------------------------------
Summary: Change PicketLinkIDMOrganizationServiceImpl.recoverFromIDMError method to include Exception
Key: GTNPORTAL-3080
URL: https://issues.jboss.org/browse/GTNPORTAL-3080
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Identity integration
Affects Versions: 3.6.0.Beta02
Reporter: Martin Weiler
Assignee: Marek Posolda
Fix For: 3.6.0.Final
PicketlinkIDMOrganizationServiceImpl.recoverFromIDMError() method was added with GTNPORTAL-2928 changes to have a single place to handle exceptions at the IDM layer.
As the code in the upper layer (WebUI classes) is not prepared to handle the exception, the current implementation does a rollback of the failed transaction, and starts a new one afterwards.
In a custom implementation using the IDM layer, it could be desirable to let the exception bubble up the stack instead. For this, users can create subclass of PicketlinkIDMOrganizationServiceImpl and
override method recoverFromIDMError() with their own code for recovery
error and rollback of their own transaction abstraction.
To access the original exception for some reason, the signature of recoverFromIDMError() should be changed to include the exception, so the
signature will be "recoverFromIDMError(Exception e)" .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (GTNPORTAL-3079) Fix modals/popups on the classic site when visiting from a mobile device
by Matt Wringe (JIRA)
Matt Wringe created GTNPORTAL-3079:
--------------------------------------
Summary: Fix modals/popups on the classic site when visiting from a mobile device
Key: GTNPORTAL-3079
URL: https://issues.jboss.org/browse/GTNPORTAL-3079
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Mobile, WebUI
Reporter: Matt Wringe
Assignee: Matt Wringe
When viewing the classic site on a mobile device, the modals with text input (like the login modal) don't work properly. This is due to the mobile device trying to handle scrolling for the on-screen keyboard, while the portal also tries to always center the content using javascript.
The portal should not be handling the page in this manner, we should be using a more purely css based mechanism to center the content on the page.
Notes:
- this does not affect the mobile site.
- this may or may not affect tablets, depending on if they are zoomed in or not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months