TysonN
Khoros Alumni (Retired)
Joined 11 years ago
User Profile
User Widgets
Contributions
Re: Default bio widget doen't work for plain Users and can't parse it from DB for plain Users
him_varma is correct. Your code is probably throwing a freemarker error for a non-admin user because one of your freemarker objects doesn't exist for a non-admin user. And of course the error message for a non-admin user won't include any useful debugging info. The component might fail more gracefully if you add an additional check like so: <#if (res.data.items[0].biography)?has_content>...</#if> This will check for both not null and not empty. However, it won't address the issue of some profile fields not being retrievable for non-admin users via a rest() call. This may be an acceptable use case for restadmin().567ViewsSign in to react to this post0Comments- ViewsSign in to react to this postComment
Re: API for "Hide messages in this board from lists"
You're correct that this is not currently available as a constraint via the APIv2 messages collection, and I agree it'd be pretty handy if it were. Khoros PS has made an internal request for this, though I couldn't tell you if and when it will happen at this point. Might be worth checking with your CSM if you have one.ViewsSign in to react to this postCommentsRe: Requires dependency to upgrade Base Theme skin
There's a known bug in Studio which prevents upgrading Themes versions. If you have an open engagement with Professional Services, please ask us to upgrade the version for you. If not, please open a Support ticket for the same.ViewsSign in to react to this postCommentsRe: How to download all skins in Studio into SDK
You couldn't call the child "theme_support" in Studio, but I believe that's what Parshant is suggesting, yes.ViewsSign in to react to this postCommentsRe: How to download all skins in Studio into SDK
Then you already started with a copy of the theme_support files. If you're trying to do local Sass compilation, that's not (yet) supported via the Community SDK, and as you've discovered, it's not straightforward to obtain all of the core Sass files. You can, however, find read-only copies in Studio.ViewsSign in to react to this postCommentsRe: How to download all skins in Studio into SDK
Ah, sorry, I mis-spoke. Of course we do support local Sass compilation via li serve-sass. But the Community SDK code does not currently handle core theme code. Back to SuzieH 's original response, this could be considered a bug, and is worth reporting to Support. In the meantime, you could use Parshant 's workaround, which I believe is to create a new custom skin derived from "theme_support". This is effectively a copy of theme_support, and since it's custom, Community SDK should allow you to export it. You could then rename your local copy to "theme_support" and see if that allows you to compile locally via li serve-sass. Not sure if Parshant has actually done this exact thing. I have not. Another option is to manually copy files out of Studio. You're right that that doesn't sound like much fun.ViewsSign in to react to this postCommentsRe: How to download all skins in Studio into SDK
If you derive a custom skin from the theme_support skin, all of the theme_support Sass files will be copied there.ViewsSign in to react to this postCommentsRe: How to download all skins in Studio into SDK
Themes skins (both base and support) are core skins which wouldn't normally be included in your SDK export. Parshant 's suggestion is also what I'd recommend, as Themes skins do contain directives to copy Sass partials to skins which inherit from them. Themes skin partials are also viewable, read-only, in Studio.ViewsSign in to react to this postComments
567Views
0CommentsYou’ve seen all recent content