Eelco Hillenius wrote:
>> Unfortunately, this was just one little nice-to-have enhancement I
>> thought I'd throw in while I was making changes. It works fine until I
>> put the code into it's production environment, which means it's being
>> called as part of a Plumtree portal. And there something falls apart
>> when I do this. It's not Wicket's fault, of course, but some strange
>> interaction with Plumtree's Javascript. In Firefox the fragment
>> identifier is gone; in IE I get an "Internal Error." Although the fault
>> is clearly with Plumtree that doesn't help me. I think "nice-to-have"
>> is going to turn into "yes-it-would-have-been-nice". :-)
>
> Could you tell us more about what doesn't work/ what kind of problems
> you are experiencing en what your environment looks like? I'd say
> there not much that can go wrong with anchors?
I probably won't have time to look into it until next week. There's a
major client demo, and things are basically frozen. But briefly, there
is something that runs in the portal server and combines pieces of
otherwise independent application. To do this, it must adjust all
links, hrefs, hrefs, etc to point through the portal server, converting
a link like this:
<a
href="/myContext/?path=0:forums:0:topics:1:topicLink&interface=I
LinkListener" title="...">
into something more like this:
<a
href="javascript:void(pt_8362.refresh('https://portal.server.com/por
tal/server.pt/gateway/PTARGS_0_0_8362_2263_0_43/https%3B/my.server.c
om/myContext/?path=0:forums:0:topics:1:topicLink&interface=ILink
Listener'));" title="...">
Something in that process is causing issues for us with the fragment
identifiers included. But I wont' be able to check on this too soon.
Thanks for your help and your insight,
-- Scott
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
