Hidden code on every page

Still trying to understand why my submissions don't work (I would really appreciate if someone could help me), I thought that maybe trying the lastest version would help out. Now, on my home page, I have the following code:

<div class="hd">An error has occurred</div>
<div class="bd">

<p>An error has occurred in Orbeon Forms. You may want to try one of the following: </p>

<ul>
<li>Close this dialog and continue to use this page.</li>
<li>Reload this page. Note that you will lose any unsaved changes.</li>
<li>

<p>If the above does not work, try reloading the page yourself. Note that you will lose any unsaved changes:</p>

<ul>
<li>With Firefox and Safari: hold down the <code>shift</code> key and click the Reload button in your browser toolbar.</li>
<li>With Internet Explorer: hold down the <code>control</code> key and click the Reload button in your browser toolbar.</li>
</ul>

</li>
<li>Return home.</li>
</ul>

<div class="xforms-error-panel-details-hidden">

<p>


Show details


</p>

</div>

<div class="xforms-error-panel-details-shown xforms-disabled">

<p>



Hide details


</p>

<div class="xforms-error-panel-details"></div>

</div>

</div>

</div>
<div class="xforms-help-panel xforms-initially-hidden" xml:base="oxf:/config/help-panel.xml">

<div class="hd">Help</div>

<div class="bd">

<div class="xforms-help-panel-message"></div>

<div class="xforms-help-panel-close">
<button>Close</button>

</div>

</div>

</div>

I just wanted to know if it was really normal?

What you are seeing is Form's new error page. If you hit the details
button, it should show you the cause of the error in a format similar to
what you're used to seeing.

This is normal if you are getting or expecting an error. It is not
normal if you are expecting a normal page. :)

You would have to look at the details of your error to find out why you
are seeing this.

Daniel E. Renfer
http://kronkltd.net/

StephR wrote:
> Still trying to understand why my submissions don't work (I would really
> appreciate if someone could help me), I thought that maybe trying the
> lastest version would help out. Now, on my home page, I have the following
> code:
>  
[snip error page]
> I just wanted to know if it was really normal



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

That's what I thought... there shouldn't be any errors so I don't really understand :)!

I changed the epilogue-servlet.xpl to have a plain template... if I come back to the initial file (and thus initial template) I don't see this error.

Is this right what I'm doing, epilogue-servlet.xpl :

<!-- The container is a servlet -->
    <p:choose href="#xformed-data">
        <!-- XHTML detection. Apply the theme, rewrite URLs, and serialize to HTML or XHTML. -->
        <p:when test="/xhtml:html">
            <!-- Apply theme -->
            <p:choose href="#request">
                <p:when test="starts-with(/request/request-path, '/doc/') or /request/parameters/parameter[name = 'orbeon-theme']/value = 'plain'">
                    <!-- Case of doc: use plain theme -->
                    <p:processor name="oxf:unsafe-xslt">
                        <p:input name="data" href="#xformed-data"/>
                        <p:input name="request" href="#request"/>
                        <p:input name="config" href="theme-doc.xsl"/>
                        <p:output name="data" id="themed-data"/>
                    </p:processor>
                    <!-- Rewrite all URLs in HTML and XHTML documents -->
                    <p:processor name="oxf:xhtml-rewrite">
                        <p:input name="rewrite-in" href="#themed-data"/>
                        <p:output name="rewrite-out" id="rewritten-data"/>
                    </p:processor>
                </p:when>
                <p:when test="starts-with(/request/request-path, '/xforms-renderer')">
                    <!-- Case of XForms Renderer mode: use plain theme and don't rewrite -->
                    <p:processor name="oxf:unsafe-xslt">
                        <p:input name="data" href="#xformed-data"/>
                        <p:input name="request" href="#request"/>
                        <p:input name="config" href="theme-plain.xsl"/>
                        <p:output name="data" id="rewritten-data"/>
                    </p:processor>
                </p:when>
                <p:otherwise>
                    <!-- Default case: show portal theme and rewrite data -->
                    <p:processor name="oxf:unsafe-xslt">
                        <p:input name="data" href="#xformed-data"/>
                        <p:input name="request" href="#request"/>
                        <p:input name="config" href="theme-plain.xsl"/>
                        <p:output name="data" id="themed-data"/>
                    </p:processor>
                    <!-- Rewrite all URLs in HTML and XHTML documents -->
                    <p:processor name="oxf:xhtml-rewrite">
                        <p:input name="rewrite-in" href="#themed-data"/>
                        <p:output name="rewrite-out" id="rewritten-data"/>
                    </p:processor>
                </p:otherwise>
            </p:choose>

[...]

Does it come from this ? I have attached the file that I call... but it's the same file where the submission doesn't work and I'm desperately waiting for help... ;)!

Thanks !

Steph



Daniel E. Renfer a écrit :

What you are seeing is Form's new error page. If you hit the details
button, it should show you the cause of the error in a format similar to
what you're used to seeing.

This is normal if you are getting or expecting an error. It is not
normal if you are expecting a normal page. :)

You would have to look at the details of your error to find out why you
are seeing this.

Daniel E. Renfer
http://kronkltd.net/

StephR wrote:
  

Still trying to understand why my submissions don't work (I would really
appreciate if someone could help me), I thought that maybe trying the
lastest version would help out. Now, on my home page, I have the following
code:
  
    

[snip error page]
  

I just wanted to know if it was really normal
    

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

At first glance, your epilogue looks right, but I haven't checked it
against mine.

Looking at your login form, I see that you have a trigger that does
nothing. Odd, but shouldn't be causing an error. You have your instance
hard-coded into your form, with no way to load a new one. That would
make your form not work very well, but shouldn't cause an error. You are
submitting the instance to the same URL as your login page, but I assume
you are aware of that. Again, shouldn't be causing an error.

It looks like you want to be putting your xforms:action element inside
inside your xforms:trigger so that when you click on the trigger, it
executes the action, but I may be just getting tripped up by some of the
obscure syntaxes of xforms.

When you click on the details of the error page, what is it saying the
error is? That'll tell you right there.

Daniel E. Renfer
http://kronkltd.net/

Stephane Ruchet wrote:
> That's what I thought... there shouldn't be any errors so I don't
> really understand :)!
>
> I changed the epilogue-servlet.xpl to have a plain template... if I
> come back to the initial file (and thus initial template) I don't see
> this error.
>
> Is this right what I'm doing, epilogue-servlet.xpl :
>
[snip epilogue-servlet.xpl]

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Hi Daniel,

Thanks for your quick feedback.

I see that you have a trigger that does nothing.

Why do you say that ? I have followed the example here : http://www.orbeon.com/ops/source-viewer/pfc-atm/ . Check the enter-pin-view.xhtml file. The trigger is used to launch the submission when the user clicks on "enter". Why would it be wrong ?

You have your instance hard-coded into your form, with no way to load a new one. That would make your form not work very well, but shouldn't cause an error.

Again, I would like to understand ? The example shows that I can do this... and why would it make my form not work very well (it does not work at all :) )

You are submitting the instance to the same URL as your login page,

But now the action element is set to submit, and in my page-flow, i have to following :

<page id="login" path-info="/" view="/is/login/login.xhtml">
    <action when="/form/action='submit'" action="/is/login/login-model.xpl">
         <result id="success" page="homeCoordinator"/>
    </action>
</page>

Again, I believe that I followed correctly an example on orbeon's website. Could you tell me why you think this is strange ?

When you click on the details of the error page, what is it saying the
error is? That'll tell you right there.

I don't have the possibility to see the details of the error page. The code is there, but my login page is presented the exact same way that it was under orbeon 3.5. It's only because I looked at the source of the page that I saw all this extra code.

Thanks for your help !



Daniel E. Renfer a écrit :

At first glance, your epilogue looks right, but I haven't checked it
against mine.

Looking at your login form, I see that you have a trigger that does
nothing. Odd, but shouldn't be causing an error. You have your instance
hard-coded into your form, with no way to load a new one. That would
make your form not work very well, but shouldn't cause an error. You are
submitting the instance to the same URL as your login page, but I assume
you are aware of that. Again, shouldn't be causing an error.

It looks like you want to be putting your xforms:action element inside
inside your xforms:trigger so that when you click on the trigger, it
executes the action, but I may be just getting tripped up by some of the
obscure syntaxes of xforms.

When you click on the details of the error page, what is it saying the
error is? That'll tell you right there.

Daniel E. Renfer
http://kronkltd.net/

Stephane Ruchet wrote:
  

That's what I thought... there shouldn't be any errors so I don't
really understand :)!

I changed the epilogue-servlet.xpl to have a plain template... if I
come back to the initial file (and thus initial template) I don't see
this error.

Is this right what I'm doing, epilogue-servlet.xpl :

    

[snip epilogue-servlet.xpl]
  

Does it come from this ? I have attached the file that I call... but
it's the same file where the submission doesn't work and I'm
desperately waiting for help... ;)!

Thanks !

Steph



Daniel E. Renfer a écrit :
    

What you are seeing is Form's new error page. If you hit the details
button, it should show you the cause of the error in a format similar to
what you're used to seeing.

This is normal if you are getting or expecting an error. It is not
normal if you are expecting a normal page. :)

You would have to look at the details of your error to find out why you
are seeing this.

Daniel E. Renfer
http://kronkltd.net/
    
      

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

It is normal to see this in the source code for the page, but do you see
it when you look at the page in your browser?

-Erik

StephR wrote:
--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Okay so it is normal. I did think so and I suppose you hide it with css and show it when there is really an error.

Well that's one thing... but still my submission will not work under firefox... and it will under IE even though this morning it wouldn't either :(



Erik Bruchez a écrit :

It is normal to see this in the source code for the page, but do you see it when you look at the page in your browser?

-Erik

StephR wrote:

Still trying to understand why my submissions don't work (I would really
appreciate if someone could help me), I thought that maybe trying the
lastest version would help out. Now, on my home page, I have the following
code:

<div class="hd">An error has occurred</div>
<div class="bd">

<p>An error has occurred in Orbeon Forms. You may want to try one of the
following: </p>

<ul>
<li> Close this dialog  and continue to use this page.</li>
<li> Reload this page . Note that you will lose any unsaved changes.</li>
<li>

<p>If the above does not work, try reloading the page yourself. Note that
you will lose any unsaved changes:</p>

<ul>
<li>With Firefox and Safari: hold down the <code>shift</code> key and click
the Reload button in your browser toolbar.</li>
<li>With Internet Explorer: hold down the <code>control</code> key and click
the Reload button in your browser toolbar.</li>
</ul>

</li>
<li>Return  /mepia2/ home .</li>
</ul>

<div class="xforms-error-panel-details-hidden">

<p>

/mepia2/ops/images/xforms/section-closed.png Show details


</p>

</div>

<div class="xforms-error-panel-details-shown xforms-disabled">

<p>


/mepia2/ops/images/xforms/section-opened.png Hide details


</p>

<div class="xforms-error-panel-details"></div>

</div>

</div>

</div>
<div class="xforms-help-panel xforms-initially-hidden"
<a class="moz-txt-link-freetext" href="xml:base=">xml:base="oxf:/config/help-panel.xml">

<div class="hd">Help</div>

<div class="bd">

<div class="xforms-help-panel-message"></div>

<div class="xforms-help-panel-close">
<button>Close</button>

</div>

</div>

</div>

I just wanted to know if it was really normal?

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Stephane Ruchet wrote: different than how I'm used to seeing triggers used. It's always struck
me as odd that all of the examples on the Orbeon site were done that
way. Erik, could you please explain why that is? And how that works? It
may just be my limited understanding of how events work in XForms, but
it seems to me that that would trigger whenever the group receives a
DOMActivate and not just the trigger. disregard my comments in that matter. I was more or less grasping at
straws to find out what your problem may be having only a portion of the
code. I said it wouldn't work very well because that particular page
wouldn't be able to respond to anything done in the model. Since you do
that processing elsewhere, it isn't an issue. see the reason for the error on the line before the stack trace. Try
looking in ops.log or stdout.log and see if you can find any errors.

Sorry for confusing you when I was only trying to help. :)

Daniel E. Renfer
http://kronkltd.net/


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Daniel & all,

 > Okay, I now see why you're doing that. Obviously, it works, but it's
 > different than how I'm used to seeing triggers used. It's always
 > struck me as odd that all of the examples on the Orbeon site were
 > done that way. Erik, could you please explain why that is? And how
 > that works? It may just be my limited understanding of how events
 > work in XForms, but it seems to me that that would trigger whenever
 > the group receives a DOMActivate and not just the trigger.

Events in XForms follow the XML Events specification, which itself is
based on DOM 2 events. This means that:

* An event is dispatched to a target (here the xforms:secret or the
   xforms:trigger controls).

* The event first follows a capture phase (which usually nobody cares
   about).

* It then follows a bubbling phase, i.e. goes up the XML elements from
   the target towards the root element. This is usually more
   interesting.

* Finally, there may be default action taking place.

There is a drawing here illustrating this:

   http://www.w3.org/TR/2003/REC-xml-events-20031014/

What you see in this example is this:

     <xforms:group>
         <xforms:secret ref="pin">
             <xforms:alert>Invalid PIN</xforms:alert>
         </xforms:secret>
         <xforms:trigger>
             <xforms:label>Access Account</xforms:label>
         </xforms:trigger>
         <xforms:action ev:event="DOMActivate">
             <xforms:setvalue ref="action">submit</xforms:setvalue>
             <xforms:send submission="main-submission"/>
         </xforms:action>
     </xforms:group>

Here, the xforms:action event handler will be activated whether a
DOMActivate event is dispatched to xforms:secret or xforms:trigger,
because the event in both cases will bubble up towards the
xforms:group. By placing the event handler within xforms:group, we
implicitly attach it as an observer on the xforms:group element. When
the event reaches xforms:group, the event handler will therefore run.

This allows us to write only one handler to handle an event reaching
two controls.

Of course, this is interesting in this case only because xforms:secret
is able to dispatch a DOMActivate event when pressing the return /
enter key.

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Erik Bruchez wrote: xforms:secret, click == DOMActivate. Right before I posted that, I tried
that. When it didn't work, I got confused.



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws