RobertT
Boss
Joined 14 years ago
User Profile
User Widgets
Contributions
Re: How to Install the Lithium Community SDK on Windows
There are ways to get the SDK to run on windows, it's a bit long-winded but I have the steps documented somewhere that I can share. it does involve installing a few missing dependencies manually to get it to run and I've not tested WSL as an option which might simplify the process somewhat. We've used the SDK on windows without any issues here. If you're interested in the steps let me know and I'll pull together a guide to share.Re: Is community impacted by Log4J vulnerability?
Reviewing the latest from the ISC, it would appear some initial mitigations for Log4J may not be enough and further mitigations may be required. https://isc.sans.edu/forums/diary/Log4j+2150+and+previously+suggested+mitigations+may+not+be+enough/28134/has more details. Can we confirm that Khoros infrastructure has adopted this revised guidance?Re: Lithium SDK and Apple Silicon Support
Testing with an Apple Silicon Mac, I can confirm that out of the box you'll not be able to install the required versions of NodeJS that the Community SDK currently supports. There is however a workaround to get the SDK running on an Apple Silicon Mac that I'd like to share. In order to install and run NodeJS version 8.3.0 you'll need to switch terminal over to the X86_64 architecture, there are 2 options for this. Option 1: Change Terminal in Finder to always open using Rosetta. Note: All terminal sessions will then default to the x86_64 emulation, this is fine if you don't use the terminal for other items in your workflow, however if you use the Terminal for anything else this might cause problems for you. To do this in Finder navigate to your Applications Folder > Utilities and open the Properties for Terminal (Command + I) then check the box to Open using Rosetta as shown below: Option 2 Selectively tell the Terminal session you have open to run in the X86_64 instruction set. This requires you to run the following command before interacting with the SDK every time you run a terminal session. arch -x86_64 zsh This second option is less disruptive for people who may use the terminal for other workflows, however does come with the caveat that you need to run this command every time you open a new terminal window and want to interact with the SDK. Using either of the options above you should be able to install the SDK and use it as per the instructions on the community in the same way that Intel Macs are currently supported.Lithium SDK and Apple Silicon Support
Any news on updating the Lithium SDK to support newer versions of NodeJS? It's stuck at version 8.3.x currently and Apple Silicon Macs are only supported by NodeJS 16.x and newer. Couple that with the SDK not officially being supported on Windows and it's looking bleak for the current SDK workflow going forwards. I know Aurora is in the works but that's not likely to address this issue before it becomes a problem for people, our company is looking to transition the Mac estate over to Apple Silicon machines in the next 12 months and we don't have confirmed plans to shift to Aurora in that timeframe for our community.Increase line-spacing for badge description text
Hi there, The descriptive text that appears when you hover over a badge on the community looks a little cramped. I'd recommend increasing the line-spacing (CSS line-height) slightly just to make this a little more legible as it looks a bit squashed. I played around here and set the following CSS: line-height: 120%; The before and after results are shown below: and with the change...Re: How to Install the Lithium Community SDK on Windows
Hi Allen, Looking at the error it seems it's not happy with Visual Studio when it comes to the node-gyp dependency part of the build. Visual Studio 2017 and later cause some issues unfortunately. I think I've seen this before, if I remember correctly there is a workaround. Can you try running the following command: npm install --global --production windows-build-tools --vs2015 following this re-run the command to install the Lithium-SDK npm install -g lithium-sdk Hopefully that should work.Re: How to Install the Lithium Community SDK on Windows
charan have you used NodeJS on your machine prior to attempting to install the SDK and if so what version of NodeJS is currently installed alongside npm? You can check this by running the following commands in powershell node -v npm -v If you're using NodeJS 8.3.0 and are not relying on it for anything else other than the SDK you might be able to get the SDK to install by running it with the --force flag. npm install -g lithium-sdk --forceRe: Custom Search Components
This is possible with some CSS, we've done it on our community, an example of this can be found at https://helpforum.sky.com/t5/What-s-On/bd-p/sky_programmingchannels You need to ensure if you're displaying any text over the image that there's suitable contrast between the background image and the text, also to have an image which will work with the overlaying elements. We're using the out of the box search component with some JS and CSS to alter its display.Re: Adding Components Visible Prior to Login Only
Hi lindseyrheapool You can do this by wrapping the component code in studio using the following freemarker logic: <#if user.anonymous> -- component code here -- </#if> In the above scenario, the component will only be displayed to anonymous users, once signed in the condition is no longer true so the code is not loaded.
