September 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3151) Twitter OAuth integration doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3151?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3151: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 982249|https://bugzilla.redhat.com/show_bug.cgi?id=982249] from NEW to MODIFIED > Twitter OAuth integration doesn't work > -------------------------------------- > > Key: GTNPORTAL-3151 > URL: https://issues.jboss.org/browse/GTNPORTAL-3151 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Final > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.1.Final, 3.7.0.Final > > > Twitter OAuth integration actually doesn't work, because Twitter stopped to support it's 1.0 API and we used old version of twitter4j-core library, which supported just Twitter 1.0. > We need to upgrade to twitter4j-core 3.0.3, which supports newest Twitter API 1.1 -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3151) Twitter OAuth integration doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3151?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3151: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> made a comment on [bug 982249|https://bugzilla.redhat.com/show_bug.cgi?id=982249] This was fixed in upstream some time ago and appeared in JPP 6.1.0 ER03, so it might have been verified already. > Twitter OAuth integration doesn't work > -------------------------------------- > > Key: GTNPORTAL-3151 > URL: https://issues.jboss.org/browse/GTNPORTAL-3151 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Final > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.1.Final, 3.7.0.Final > > > Twitter OAuth integration actually doesn't work, because Twitter stopped to support it's 1.0 API and we used old version of twitter4j-core library, which supported just Twitter 1.0. > We need to upgrade to twitter4j-core 3.0.3, which supports newest Twitter API 1.1 -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3151) Twitter OAuth integration doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3151?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3151: ---------------------------------------------------- Thomas Heute <theute(a)redhat.com> made a comment on [bug 982249|https://bugzilla.redhat.com/show_bug.cgi?id=982249] > Twitter OAuth integration doesn't work > -------------------------------------- > > Key: GTNPORTAL-3151 > URL: https://issues.jboss.org/browse/GTNPORTAL-3151 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Final > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.1.Final, 3.7.0.Final > > > Twitter OAuth integration actually doesn't work, because Twitter stopped to support it's 1.0 API and we used old version of twitter4j-core library, which supported just Twitter 1.0. > We need to upgrade to twitter4j-core 3.0.3, which supports newest Twitter API 1.1 -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3151) Twitter OAuth integration doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3151?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3151: ---------------------------------------------------- Thomas Heute <theute(a)redhat.com> changed the Status of [bug 982248|https://bugzilla.redhat.com/show_bug.cgi?id=982248] from NEW to CLOSED > Twitter OAuth integration doesn't work > -------------------------------------- > > Key: GTNPORTAL-3151 > URL: https://issues.jboss.org/browse/GTNPORTAL-3151 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Final > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.1.Final, 3.7.0.Final > > > Twitter OAuth integration actually doesn't work, because Twitter stopped to support it's 1.0 API and we used old version of twitter4j-core library, which supported just Twitter 1.0. > We need to upgrade to twitter4j-core 3.0.3, which supports newest Twitter API 1.1 -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3151) Twitter OAuth integration doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3151?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3151: ---------------------------------------------------- Thomas Heute <theute(a)redhat.com> made a comment on [bug 982248|https://bugzilla.redhat.com/show_bug.cgi?id=982248] > Twitter OAuth integration doesn't work > -------------------------------------- > > Key: GTNPORTAL-3151 > URL: https://issues.jboss.org/browse/GTNPORTAL-3151 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Final > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.1.Final, 3.7.0.Final > > > Twitter OAuth integration actually doesn't work, because Twitter stopped to support it's 1.0 API and we used old version of twitter4j-core library, which supported just Twitter 1.0. > We need to upgrade to twitter4j-core 3.0.3, which supports newest Twitter API 1.1 -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3253) [IE] Ajax requests are broken if the node name containing accent characters

by Hai Nguyen (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3253?page=com.atlassian.jira.pl... ] Hai Nguyen commented on GTNPORTAL-3253: --------------------------------------- PR for 3.5.x: https://github.com/gatein/gatein-portal/pull/656 > [IE] Ajax requests are broken if the node name containing accent characters > --------------------------------------------------------------------------- > > Key: GTNPORTAL-3253 > URL: https://issues.jboss.org/browse/GTNPORTAL-3253 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Internet Explorer browser > Reporter: Trong Tran > Assignee: Hai Nguyen > Priority: Critical > Labels: backlogs > Fix For: 3.7.0.Final > > > h3. Problem > Let's say we have a page with node name is "tét". Go to Edit Page, then click on the close/save button ==> it doesn't work. > h3. Cause > The encoded URI in the href attribute of <a> tag is automatically decoded in wrong ISO-8859-1 before the javascript function is executed > h3. Proposal to fix the problem > We should use *onclick* to perform the javascript ajax update execution instead of href attribute. > Moreover, putting javascript code into href is kind of bad practice that we could avoid in use -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3253) [IE] Ajax requests are broken if the node name containing accent characters

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3253?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3253: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: (was: 3.5.7.Final) Resolution: Done > [IE] Ajax requests are broken if the node name containing accent characters > --------------------------------------------------------------------------- > > Key: GTNPORTAL-3253 > URL: https://issues.jboss.org/browse/GTNPORTAL-3253 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Internet Explorer browser > Reporter: Trong Tran > Assignee: Hai Nguyen > Priority: Critical > Labels: backlogs > Fix For: 3.7.0.Final > > > h3. Problem > Let's say we have a page with node name is "tét". Go to Edit Page, then click on the close/save button ==> it doesn't work. > h3. Cause > The encoded URI in the href attribute of <a> tag is automatically decoded in wrong ISO-8859-1 before the javascript function is executed > h3. Proposal to fix the problem > We should use *onclick* to perform the javascript ajax update execution instead of href attribute. > Moreover, putting javascript code into href is kind of bad practice that we could avoid in use -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2394) The GadgetDeployer should unregister itself as WebAppListener in the stop method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2394?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-2394: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=987708 > The GadgetDeployer should unregister itself as WebAppListener in the stop method > -------------------------------------------------------------------------------- > > Key: GTNPORTAL-2394 > URL: https://issues.jboss.org/browse/GTNPORTAL-2394 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.1.0-GA > Reporter: Nicolas Filotto > Labels: gadget > Attachments: GTNPORTAL-2394.patch > > > Up to now, when the application tries to stop the component instead of unregistering itself it registers itself another time. Indeed the current code is: > {code} > public void stop() > { > DefaultServletContainerFactory.getInstance().getServletContainer().addWebAppListener(this); > } > {code} > But should be: > {code} > public void stop() > { > DefaultServletContainerFactory.getInstance().getServletContainer().removeWebAppListener(this); > } > {code} -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3250) The portlets cannot be displayed after a portal reload

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3250?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3250: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=987708 > The portlets cannot be displayed after a portal reload > ------------------------------------------------------ > > Key: GTNPORTAL-3250 > URL: https://issues.jboss.org/browse/GTNPORTAL-3250 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PC integration > Affects Versions: 3.6.1.Final > Reporter: Nicolas Filotto > Assignee: Marko Strukelj > Attachments: GTNPORTAL-3250.patch > > > If you launch Gatein in developing mode, it is possible to reload only a given portal container either automatically by redeploying a webapp that has been defined as a PortalContainerConfigOwner (in other words you have the listener org.exoplatform.container.web.PortalContainerConfigOwner in your web.xml) or manually using the JMX console. And when you do so, no portlet can be displayed properly anymore (we have the message "This portlet encountered an error and could not be displayed" for all portlets), this issue is due to https://issues.jboss.org/browse/GTNPORTAL-2406. > Here are the steps to reproduce: > * Start GateIn with ./standalone.sh -Dexo.product.developing=true > * launch the JMX Console and call _reload_ with the argument _portal_ on the MBean {{exo:container=root}} > * Once the command is over, go to http://localhost:8080/portal/ -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3253) [IE] Ajax requests are broken if the node name containing accent characters

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3253?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3253: ---------------------------------- Fix Version/s: 3.5.7.Final 3.7.0.Final > [IE] Ajax requests are broken if the node name containing accent characters > --------------------------------------------------------------------------- > > Key: GTNPORTAL-3253 > URL: https://issues.jboss.org/browse/GTNPORTAL-3253 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Internet Explorer browser > Reporter: Trong Tran > Assignee: Hai Nguyen > Priority: Critical > Labels: backlogs > Fix For: 3.5.7.Final, 3.7.0.Final > > > h3. Problem > Let's say we have a page with node name is "tét". Go to Edit Page, then click on the close/save button ==> it doesn't work. > h3. Cause > The encoded URI in the href attribute of <a> tag is automatically decoded in wrong ISO-8859-1 before the javascript function is executed > h3. Proposal to fix the problem > We should use *onclick* to perform the javascript ajax update execution instead of href attribute. > Moreover, putting javascript code into href is kind of bad practice that we could avoid in use -- 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

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues September 2013