portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-323) Portlet Entity Browser portlet broken when installed in a custom portal with a different context name
Date Thu, 04 Aug 2005 22:00:37 GMT
     [ http://issues.apache.org/jira/browse/JS2-323?page=all ]
     
Ate Douma resolved JS2-323:
---------------------------

    Resolution: Fixed
     Assign To: Scott Weaver

I tested it out on my JS2-319 branch (merged your changes locally) and it now works!
Although I haven't tested it out on trunk, I can't think why it wouldn't work there, except
I can't get trunk running with a different context.
Lets just assume its fixed  :-)

> Portlet Entity Browser portlet broken when installed in a custom portal with a different
context name
> -----------------------------------------------------------------------------------------------------
>
>          Key: JS2-323
>          URL: http://issues.apache.org/jira/browse/JS2-323
>      Project: Jetspeed 2
>         Type: Bug
>   Components: Ajax
>     Versions: 2.0-M4
>     Reporter: Ate Douma
>     Assignee: Scott Weaver
>      Fix For: 2.0-M4

>
> The current Ajax javascript in the PAM Portlet Application contains hardcoded references
to a /jetspeed context.
> Because of this, the Portlet Entity Browser is broken on a custom portal installation
with a different context name.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message