Could you report his particular issue to Jira?
If you still think that embedded elements suck (apart form the fact
that this one thing doesn't work as you want), can you please post a
proposal for how you would design it? Maybe give your thoughts on the
other post that talks about widget co
Exactly, I can't use EXIT:QUERY on flowlinks which point to url-less
elements. The generated link should be to the current page.
On Sep 11, 2005, at 4:33 PM, Geert Bevin wrote:
What is the exact exception you get, and when?
There should be nothing that prevents you from defining flowlinks
a
What is the exact exception you get, and when?
There should be nothing that prevents you from defining flowlinks and
datalinks to url-less elements. Only generating URLs to activate the
exits should trigger an exception.
Submissions don't have that limitation and any submission will always
p
No, I don't think so. I can't define flowlinks from embedded element
to itself because it says element has no url.
On Sep 11, 2005, at 3:24 PM, Geert Bevin wrote:
As long as the embedded element has no url of its own in the site
definition, the entire embedding page will be reloaded and
ev
As long as the embedded element has no url of its own in the site
definition, the entire embedding page will be reloaded and everything
will be passed on to the embedded element. It functions then exactly
as a portlet.
On 11-sep-05, at 21:20, Keith Lea wrote:
I have lots of problems with r
I have lots of problems with rife's implementation of embedded
elements. I think it sucks that I can't specify exits and flowlinks
for embedded elements which point to itself, so the embedded element
can generate EXIT:QUERY links, and form submissions, to the current
page, which reloads the
