Jenn Cole's dashboard

StrayCat marked one of Scott Fleckenstein's replies in Get Satisfaction as useful. Scott Fleckenstein replied to the question "How come our "Widget embed page" is always blank? Can I dictate what goes there?".

StrayCat marked one of Scott Fleckenstein's replies in Get Satisfaction as useful. Scott Fleckenstein replied to the question "Why won't our widget default to the question view?".

StrayCat replied on June 04, 2009 19:29 to the problem "Feedback widget causes security prompts on SSL secured site" in Get Satisfaction:

For what it's worth, we stopped seeing the IE non-secure message about 12 days ago when you deployed the fix. It has been working well for us over SSL since then.

StrayCat replied on May 27, 2009 12:55 to the idea "Filter the feedback widget based on URL" in Get Satisfaction:

I am interested in specifying a page identifier as one of the feedback widget properties. In my dream world, the widget options would include an origin property and I would stuff my page title into it. It would look something like this:
feedback_widget_options.origin = encodeURIComponent(document.title);

I'm not exactly sure if this question submitted by smnbss is what I'm looking for, but it sounds like it might be in the ballpark... Just checking to see if this is still in beta or is it commonly available yet?

StrayCat started following the idea "Filter the feedback widget based on URL" in Get Satisfaction.

StrayCat started following the idea "dont require customers to log in to post!!!!" in Get Satisfaction.

StrayCat started following the idea "Include Product Tags in Email Notification" in Get Satisfaction.

A comment on the question "How come our "Widget embed page" is always blank? Can I dictate what goes there?" in Get Satisfaction:

We have the widget embedded in our password protected Web app. I had to put the code in the head element (rather than the body element) of the pages. I read online about another dude who had to do that, too, and he claims it worked OK. If you need to see it, feel free to contact me off-line and I can get you a temporary password. jcoleATpkcDOTcom – StrayCat, on May 26, 2009 12:33

StrayCat asked a question in Get Satisfaction on May 22, 2009 20:10:

How come our "Widget embed page" is always blank? Can I dictate what goes there?

When somebody submits something using feedback widget, the e-mail message I receive contains this information:
Your Get Satisfaction feedback widget generated these additional details:
Widget embed page:
Browser: Internet Explorer 7.0
OS: Windows Vista

How come our "Widget embed page" field is always empty, and what do I need to do to get it to contain useful information? It would be awesome if I could get it to contain, say, the page title using document.title. (I use a similar trick in Google Analytics for tracking page views.)

StrayCat asked a question in Get Satisfaction on May 22, 2009 20:01:

Why won't our widget default to the question view?

We want our widget to default to the question view. I can even see it in our code snippet where that option is set: feedback_widget_options.style = "question";
But for some reason it is defaulting to the idea view instead. Any ideas of why this is happening?

StrayCat started following the question "Feedback widget leaving key fields blank when submitted from password-protected page" in Get Satisfaction.

StrayCat replied on May 22, 2009 19:45 to the problem "Feedback widget causes security prompts on SSL secured site" in Get Satisfaction:

We just implemented Get Satisfaction in our Web application. It looks like the SSL support is included in the javascript (which is awesome, by the way), but for some reason I am still getting a "some content is non-secure" message in IE.

On a potentially related note, I am also getting a javascript error when I click the feedback tab:
$("recaptcha_response_field") is null

The significant observation here is that this error is reported to be encountered in http://api.recaptcha.net/js/recaptcha..., note that it is http, not https. Could this be the non-secure resource that IE is whining about?