Home Forums Weaver Xtreme Theme Formidable Forms calculated fields don’t work on Xtreme

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #17978
    businessnaples
    Participant

    I use Formidable Forms (2.0.10) on all my sites as well as Weaver Theme. Ones on Weaver Pro II all work OK. On Xtreme, they all seem to work OK except when using a form with a simple calculated field. The calculated field will not work on Xtreme but functions fine on Weaver Pro II. I created a simple test form with a simple calculated field (Qty * Price) on Weaver II Pro. Works fine. Exported form and imported into an Xtreme theme. Calculated field doesn’t calculate. Can you help with this? I even deactivated all plugins except Formidable on the Xtreme site and it will still not function.

    #23107
    scrambler
    Moderator

    Can you also ask the plugin developer to check it out, because they know how their plugin works, and are probably better placed to detect where the interaction problem comes from.

    Once that is clarified, it will be easier for weaver to figure out if it is an issue that needs fixing on the plugin side or on weaver’s side

    #23108
    Weaver
    Keymaster

    It is no doubt a JavaScript issue, and it is unlikely we can track that down with some other plugin. They might be able to do that.

    #23109
    businessnaples
    Participant

    Thanks. I will do that

    #23110
    businessnaples
    Participant

    I have further discovered that the issue is only a problem when “Previewing” the form. Once I place it on a page it works! Still just in the Xtreme theme though – works OK in Weaver II Pro. 

    Preview link where calculated field does not work:

    http://www.maintainwp4u.com/wp-admin/admin-ajax.php?action=frm_forms_preview&form=c8l6om

    Page link where the same form shortcode is placed and it works:

    http://www.maintainwp4u.com/test/

    Gave this to Formidable and they did some checking and provided this information:

    It looks like the theme is
    expecting something on the page that isn’t

    included on the preview page.

    Error: ReferenceError: wvrxEndOpts is not defined

    Source File:

    http://www.maintainwp4u.com/wp-content/themes/weaver-xtreme/assets/js/weaverxjslib-end.min.js?ver=1.2.4

    Line: 8

    Anything you can do with this?

    #23111
    scrambler
    Moderator

    @weaver is away until middle of next week, so be patient 🙂

    #23112
    businessnaples
    Participant

    Thanks – patiebce I have!

    #23113
    Weaver
    Keymaster

    @businessnaples

    What exactly do you mean by “preview page”, and exactly how do you open it from the admin side?

    You links show a difference, but the preview link has all kinds of missing statements normally included when the Weaver Xtreme page is displayed normally – almost as if the main “functions.php” file is not being loaded properly.

    Weaver II and Weaver Xtreme have quite different JavaScripts files, and it is not surprising there is a difference.

    But I would really need to know how exactly you get the the preview page.

    #23114
    businessnaples
    Participant

    Thanks for looking at this. In the Formidable form creation page there is a “Preview” link that is used to “Preview” what the form will look like. It apparently uses a “Blank” page to display the form and that is where the calculated fields do not function. I have discovered that in a recent update version of the Formidable Plugin they have added the ability to define a specific page for previewing and if I define it and use it to display the previewsit works OK. So, of course I will use that now to preview my forms. Sorry to be a bother but I think all is OK now

    #23115
    Weaver
    Keymaster

    Whatever mechanism the plugin used to build a preview page must not be quite “standard”, and thus the difference. As long as you can see the final results on a standard site view, that should seem to “solve” the issue. Glad you figured out that part.

Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.