ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Assistly Widget Integration?

September 28, 2011 8:38pm

Subscribe [1]
  • #1 / Sep 28, 2011 8:38pm

    Hitch

    105 posts

    Gang:

    Has anyone out there successfully integrated an Assistly contact form Widget (which uses jquery and fancybox) into an EE template?

    My entire site is essentially Boyink’s toots, with a different template.  I have his contact form (http://www.ebookconversion.biz/coffee/contact) as mine; I’d like to substitute the widget.  The widget is essentially simply javascript, but I get whingy about it…if anyone here has successfully done this and has any pointers, I’d appreciate same.

    EDITED TO ADD:  Well, since, as usual, here in the Questions Graveyard, where questions go to die, no one had any thoughts or experience, here’s the code (script tags removed) and here’s my question:

    // ********************************************************************************                                // This needs to be placed in the document body where you want the widget to render                                // ********************************************************************************                                                                new ASSISTLY.Widget({
                                             version: 1,
                                             site: 'sitename.assistly.com',
                                             port: '80',
                                             type: 'email',
                                             displayMode: 1,  //0 for popup, 1 for lightbox                                        features: {
                                              },
                                              fields: { 
                                                    ticket: {
                                                             // desc: '',
                                    // labels_new: '',
                                    // priority: '',
                                    // subject: '',
                                    // custom_book_title: ''
                                                    },
                                                     interaction: {
                                                             // email: '',
                                    // name: ''
                                                    },
                                                     email: {
                                                             //subject: '',
                                                             //body: ''
                                                     },
                                                     customer: {
                                                             // company: '',
                                    // desc: '',
                                    // first_name: '',
                                    // last_name: '',
                                    // title: ''
                                                    }
                                             }
                                     }).render();

    I’ve already put the script calls in the header, which is an embedded template; at least they’ve not done any harm, as near as I can tell. 

    BUT, I either get a blank section of the template whither the widget should be (if I set the type as a webpage), OR a big white Screen O’Death with all the code sitting on it like a text file rendered in a browser if I take a flier and set it as JS.  Obviously, I don’t know what I’m doing, and my EE guy is tied up until mid-November. I’m trying to put the js declarations in the head in ONE template and the actual script in another and kluge them together.  Can anyone—anyone at ALL—provide some pointers?

    Hitch

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases