Scott Fleckenstein's dashboard

Scott Fleckenstein set one of Scott Fleckenstein's replies as an official response to "How to abstract the Widget Js into an external .js file?" in Get Satisfaction

Scott Fleckenstein replied on October 15, 2009 23:06 to the question "How to abstract the Widget Js into an external .js file?" in Get Satisfaction:

Let me see if I can give a fully detailed response.

Personally, I wouldn't bother moving the invocation of the feedback widget (the second script block) into an external js file. You're only going to save 100 or so bytes with caching. If you GZip your responses, it will be even less. If you go down that path, you just need to cache feedback-v2.js in your common js file.

---

If, on the other hand, you still want to cache everything in your js, here's how you would do it.

You'd first need to copy feedback-v2.js into your common js file like above. Next you'll need to have some way to run JS after the DOM is reader. In jQuery that would be something like $(document).ready() or in prototype you'd use document.observe("dom:loaded", ...). In that code block you would include the invocation code where you create the feedback widget using new GSFN.feedback_widget().

The only thing you need to make sure about is that for your options you include a 'container' option. Normally, the feedback just uses document.write() to ouput it's HTML, but that won't work when you create the widget in an external file. So, instead you'll have to tell it where to render itself and that is where the 'container' option comes in. This option should be set to the id of an element you want to render the widget in. Preferably this element will be near the footer of the page, just like the script tags would be if you were following the preferred method. A sample call, using prototype would look like something below:


document.observe("dom:loaded", function() {
feedback_widget_options.display = "overlay";
feedback_widget_options.company = "getsatisfaction";

feedback_widget_options.container = "feedback_footer_container"

var feedback_widget = new GSFN.feedback_widget(feedback_widget_options);
});


That code assumes you have an empty html element with the id "feedback_footer_container" on every page.

-Scott

Scott Fleckenstein replied on October 14, 2009 20:46 to the question "Community Stats: where do they come from?" in Get Satisfaction:

When a logged in user visits your section, we record it on their user account. We don't currently expose that info, but we do plan on allowing users to opt in and make their information available to employees and admins in the future.

Scott Fleckenstein replied on October 13, 2009 17:15 to the problem "I'm sorry but an unexpected error occurred: NameError" in Get Satisfaction:

http://getsatisfaction.com/getsatisfa...

A fix will go out tonight.

Scott Fleckenstein replied on October 13, 2009 15:48 to the problem "Error message when viewing users private data" in Get Satisfaction:

A bug made it into last night's deploy. I've already put a fix into the code repository, and it will get deployed tonight.

Sorry for the inconvenience,
Scott

Scott Fleckenstein replied on October 12, 2009 15:41 to the problem "Feedback Button dims the page, but doesn't load" in Get Satisfaction:

Your welcome!

Glad it worked.

-Scott

Scott Fleckenstein replied on October 09, 2009 18:41 to the question "Logout FastPass" in Get Satisfaction:

Our login cookies themselves are just session cookies. When the user closes their browser, we log them out. We don't use time expiration. I can add it onto the feature requests.

---

It might be useful to note that the Fastpass cookie you set it just used as a one time communication mechanism. We delete it ourselves after we validate the url and store it in the user's session.

Scott Fleckenstein replied on October 09, 2009 18:16 to the question "Logout FastPass" in Get Satisfaction:

We will clear the necessary cookies and send users along to the url you specify If you send your users to http://commmunity.mixamo.com/logout?r...

The cookies we use to determine a user's login state are considered part of our internal API. We want to make sure that if we change our login system (as we have recently) we don't break other people's integrations.

Does that help?
-Scott

Scott Fleckenstein replied on October 09, 2009 17:26 to the problem "xmlns attributes are stripped from copy & pasted XML fragments" in Get Satisfaction:

Hi Sebastiaan,

Our input scrubber can be a little overzealous. It removes non-whitelisted attributes before it decides whether an element is whitelisted or not.

I'll add it into the bug tracker, but I also would recommend using something like gist.github.com in the meantime.

Thanks for the report,
Scott

Scott Fleckenstein replied on October 09, 2009 02:57 to the problem "406 Not Acceptable Error in Feedback Widget" in Get Satisfaction:

A fix will go out tonight. Sorry about that.

- Scott

Scott Fleckenstein replied on October 07, 2009 20:37 to the problem "FastPass + Safari + Tab widget doesn't work" in Get Satisfaction:

Thanks for reporting this. It's been added into our bug tracker.

Basically what we have to do is to modify how we open the tab to pass through the fastpass information as well.

Scott Fleckenstein replied on October 07, 2009 16:16 to the question "JSON object instead of RSS?" in Get Satisfaction:

If you look at our read-only widgets such as the List widget and the Search widget, they are driven behind the scenes by JSON. If you pull the URL it calls to on those widgets, you can see it takes a callback that gets called with the returned data.

You're free to change that callback to one of your own custom functions and do whatever you want with the data. It's not anything we support, so you'll be on your own in that regard, but it's a pretty good bet that that you can rely on those URLs being the same for a long time. We have too many people with the widgets installed to easily change those pages.

Long story short... yes.

-Scott

Scott Fleckenstein set one of Scott Fleckenstein's replies as an official response to "Lazy loading of feedback widget from javascript?" in Get Satisfaction

Scott Fleckenstein replied on October 05, 2009 15:56 to the question "Lazy loading of feedback widget from javascript?" in Get Satisfaction:

Hi Senad,

One of the options you can specify for your widget is a container, into which we will render the required html. By default, we just use document.write, that as you can see overwrites the whole page if it is called after the initial document load.

basically, you just need to specify the id of an element for your container options.

For example:

feedback_widget_options.container = "my_element_id";

Hope that helps,
Scott

Scott Fleckenstein replied on October 02, 2009 01:27 to the problem "Search and post functions returning IE errors...object undefined, ajax.." in Get Satisfaction:

Could you give it another try? I just made some more fixes.

-Scott

Scott Fleckenstein set one of Scott Fleckenstein's replies as an official response to "Search and post functions returning IE errors...object undefined, ajax.." in Get Satisfaction

Scott Fleckenstein replied on October 01, 2009 23:10 to the problem "Search and post functions returning IE errors...object undefined, ajax.." in Get Satisfaction:

Are you still seeing this? Could you try doing a full refresh of the page to get the new javascript?

There was a problem, but I deployed a fix to it roughly 2 hours ago. Also, I am no longer seeing this issue on my own browser.

Sorry for the troubles!

-Scott

Scott Fleckenstein set one of Scott Fleckenstein's replies as an official response to "CNAME forwarding" in Get Satisfaction

Scott Fleckenstein replied on September 25, 2009 23:48 to the question "CNAME forwarding" in Get Satisfaction:

Hi Darren,

We don't support using A records to enable the domain aliasing functionality. The reason for this is it adds a very big problem if we want to change hosting providers or add/change IP addresses in the future. We would have to notify and coordinate any changes with our IP addresses with all of our customers. We would run the risk of turning someone's community off unexpectedly, which we obviously want to avoid at all costs.

I'm sorry I can't offer you a better solution, but your only viable choice is really to migrate your own dns provider to one that will allow you to add cname records. Did they provide any reason why they allow A records but not CNAME records?

-Scott

Scott Fleckenstein replied on September 25, 2009 20:01 to the problem "Feedback Button dims the page, but doesn't load" in Get Satisfaction:

In your javascript, you run:

$('.loading').hide();

Our iframe has a loading class on it and so it gets improperly hidden by that statement. I would add:

$('#fdbk_container .loading').show()

after the previous statement to fix things.

Sorry about that!
-Scott Fleckenstein