skylinegtr if you want to import data from a RSS feed in a component, have a look at this thread, it should work.

darrenSP - You can easily update the confirmation message from a text editor. 

Below is the text key used for show Thanks for your feedback message. 

page.RatingEnumerationDisplay.feedback.success.title

Studio -> Text Editor -> Community Text 

Lithium uses the text key for each string appearing in the community.  You can search for the string you want to update from there. 

https://community.lithium.com/t5/FAQs-email-templates-and-text/About-text-keys/ta-p/109029

https://community.lithium.com/t5/FAQs-email-templates-and-text/Find-text-keys/ta-p/109027

Regarding the custom component for this, there is no POST API call available for helpfulness, you can only perform GET action. 

https://community.lithium.com/t5/Developer-Documentation/bd-p/dev-doc-portal?section=commv2&collection=tkb_helpfulness_ratings#constraints-message.id

Hi,

I guess you could build something custom to use the rest API to inject new content but I wouldn't suggest that's the best way or even suggested to be honest. My best advice and to make sure you get the job done, I would use li professional services and get them to migrate the content, normally done as part of the launch service but I am sure they could do this for you Post live.  

Obviously at a cost but for peace of mind and to ensure you get all content moved in the best and quickest way I would suggest ts method. 

My apologies.

You'll need to reference the results as so:

<#if activity.results.name.UserUpdated??>
  ...
</#if>

 Sorry for the confusion!

When an SSO cookie is processed, Lithium tries to delete the cookie and replace it with a cookie that starts with an exclamation point (!lithiumSSO:).  This is to prevent the app from trying to process the same cookie it's already processed more than 1 time, which we don't allow (for security reasons).  We also put time limits on how long an SSO token is good for, so it's best practice to only set an SSO cookie right befor sending a browser to the community.  

It shouldn't matter how you generate the cookie (server-side or ajax call), as long as the request is secure and cannot be used to get an sso token that lets you log in as another user.  

If you are making an ajax call to another domain to get an sso cookie, make sure you have CORS configured correctly for that community and are sending the correct headers.  

If an sso cookie is set by an ajax call, you should always reload the page (or make another ajax request with the sso cookie) since the sso processing happens on the server-side.

I googled "ajax can't set cookie firefox" and found this stackoverflow article:

Jquery Ajax Firefox not sending cookie (Chrome works)

Maybe what you're trying is related?

-Doug