• Nathan Long
  • NEWBIE
  • 0 Points
  • Member since 2015

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 0
    Replies
I have a Salesforce community using tabs that functions as a partner portal, as well as a community site using the community builder with a custom theme, that functions as a community/QA forum.  

-With the "Community User Visibility" box unchecked, the partner portal functions as expected, but the users on the community site cannot see posts outside of ones made by themselves/their accounts.  

-With the "Community User Visibility" checked, the community site functions as expected.  All questions and comments are visible.  However, every single user lookup on a page layout (specifically everything relating to tasks/activities) allows users to every user in the org, which is a usability concern, but more importantly, a security concern.  

At this point, it appears that every single related list on Opportunity/Account/etc and all pages that have a "user" lookup will have to be completely rewritten with visualforce.  I'm hoping that someone here has some advice on how this can work without rewriting a ton of basic pages just to remove a edit/del link or user lookup.
I've been tasked with adding a twitter feed to a page. The twitter TOS for embedding tweets requires some controls on the tweet that are provided by widgets.js. Since Lightning doesn't allow loading libraries from external sources, and Twitter doesn't allow local hosting of their library, this seems like a no-go. It does seem possible to load external libraries on community sites by modifying the header, which I'm not 100% opposed to doing if it gets the job done, but in this case, i believe the locker service will interfere with the functionality in widgets.js. Any advice here? There doesn't seem to be an obvious solution, short of pulling in tweet data via the twitter api, and then recreating the controls inside lightning, which would be a maintenance headache, and my fall outside Twitter's TOS.