Orbeon Forms community mailing list

Migrating from 3.8.0.201005270113; All dialogs inline

classic Classic list List threaded Threaded
♦
♦
 3 messages Options
Bill Parod
Reply | Threaded
Open this post in threaded view
♦
♦
|

Migrating from 3.8.0.201005270113; All dialogs inline

Bill Parod
We're migrating a VRA Core editor developed mostly over a year ago to the current Orbeon release. We've been running it on 3.8.0.201005270113. We have run into some problems with it on 3.9.0.201105152046.

I wonder if others with knowledge of release changes have general advice in such an upgrade or specific advice for the symptoms below. Here is what we're seeing in 3.9.0.201105152046:

The main form page is empty (white). On closer inspection with Firebug, I notice that <form id="xforms-form".../> has CSS:

html body form.xforms-initially-hidden, html body .xforms-form .xforms-initially-hidden {
    display: none;
}

By removing "display:none;" with FireBug, an error page is visible, however "Show Details" is empty.

The form appears below the error page, but all the form's fr:tabview/fr:tab elements, dialogs in the main form and in custom XBLs are laid out inline in the form on the error page.

We're just starting to dig into this. I thought I'd pass this to the list in case anyone recognizes these symptoms and has advice.

Thanks,
Bill Parod
Northwestern University
Erik Bruchez
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Migrating from 3.8.0.201005270113; All dialogs inline

Erik Bruchez
Administrator
Bill,

The fact that xforms-initially-hidden hasn't been removes indicates an
issue with the Orbeon Forms JavaScript during initialization.

I would try to configure JavaScript in dev mode:

http://wiki.orbeon.com/forms/doc/contributor-guide/development-environment/javascript-development

And then use Firebug, the Chrome dev tools, or similar, to see
if/where the JavaScript is crashing.

-Erik

On Mon, Mar 5, 2012 at 11:27 AM, Bill Parod <[hidden email]> wrote:

> We're migrating a VRA Core editor developed mostly over a year ago to the
> current Orbeon release. We've been running it on 3.8.0.201005270113. We have
> run into some problems with it on 3.9.0.201105152046.
>
> I wonder if others with knowledge of release changes have general advice in
> such an upgrade or specific advice for the symptoms below. Here is what
> we're seeing in 3.9.0.201105152046:
>
> The main form page is empty (white). On closer inspection with Firebug, I
> notice that <form id="xforms-form".../> has CSS:
>
> html body form.xforms-initially-hidden, html body .xforms-form
> .xforms-initially-hidden {
>     display: none;
> }
>
> By removing "display:none;" with FireBug, an error page is visible, however
> "Show Details" is empty.
>
> The form appears below the error page, but all the form's fr:tabview/fr:tab
> elements, dialogs in the main form and in custom XBLs are laid out inline in
> the form on the error page.
>
> We're just starting to dig into this. I thought I'd pass this to the list in
> case anyone recognizes these symptoms and has advice.
>
> Thanks,
> Bill Parod
> Northwestern University
>
>
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Migrating-from-3-8-0-201005270113-All-dialogs-inline-tp4447316p4447316.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.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
>


--
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
Bill Parod
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Re: Migrating from 3.8.0.201005270113; All dialogs inline

Bill Parod
Erik,

Thanks very much for this tip. I found the main problem was a jQuery jQuery ui version mismatch. After updating that in my code, the application comes up and mostly works now.

I am still generating an error in xforms.js

            getElementByTagName: function(root, tagNameOrArray) {
                var result = _.isArray(tagNameOrArray)
                    ? _(tagNameOrArray).chain()
                        .map(_.bind(arguments.callee, null, root))
                        .compact()
                        .first()
                        .value()
                    : root.tagName.toLowerCase() == tagNameOrArray
                        ? root
                        : root.getElementsByTagName(tagNameOrArray)[0];
                return _.isUndefined(result) ? null : result;
            },

because root is null. I'm still exploring that but traced it to a tabview dispatch in a custom XBL:

<xforms:dispatch targetid="preferred_tab" name="fr-toggle"/> 


I'm not sure why that's a problem but am still looking at it. Aside from that I'm mainly working on css changes.

Thanks again for your help.

Best,
Bill Parod



On Mar 5, 2012, at 11:12 PM, Erik Bruchez wrote:

Bill,

The fact that xforms-initially-hidden hasn't been removes indicates an
issue with the Orbeon Forms JavaScript during initialization.

I would try to configure JavaScript in dev mode:

http://wiki.orbeon.com/forms/doc/contributor-guide/development-environment/javascript-development

And then use Firebug, the Chrome dev tools, or similar, to see
if/where the JavaScript is crashing.

-Erik

On Mon, Mar 5, 2012 at 11:27 AM, Bill Parod <[hidden email]> wrote:
We're migrating a VRA Core editor developed mostly over a year ago to the
current Orbeon release. We've been running it on 3.8.0.201005270113. We have
run into some problems with it on 3.9.0.201105152046.

I wonder if others with knowledge of release changes have general advice in
such an upgrade or specific advice for the symptoms below. Here is what
we're seeing in 3.9.0.201105152046:

The main form page is empty (white). On closer inspection with Firebug, I
notice that <form id="xforms-form".../> has CSS:

html body form.xforms-initially-hidden, html body .xforms-form
.xforms-initially-hidden {
    display: none;
}

By removing "display:none;" with FireBug, an error page is visible, however
"Show Details" is empty.

The form appears below the error page, but all the form's fr:tabview/fr:tab
elements, dialogs in the main form and in custom XBLs are laid out inline in
the form on the error page.

We're just starting to dig into this. I thought I'd pass this to the list in
case anyone recognizes these symptoms and has advice.

Thanks,
Bill Parod
Northwestern University


--
View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Migrating-from-3-8-0-201005270113-All-dialogs-inline-tp4447316p4447316.html
Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.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


--
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



--
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
Free forum by Nabble Edit this page