rwm
Advisor
Joined 12 years ago
User Profile
User Widgets
Contributions
settings.name.get confusion
This is more an FYI post than an issue. Many posts talk about using settings.name.get to fetch a value, and I was using it to get the same value in two components. One component on my home/category page worked great, but the same component failed on forum topic pages (null or missing value error). My thought was a scoping issue, but what threw me off is the second component that used the same call worked at both forum and forum topic pages no problem. Put another way, on my forum topic pages I had two components, both using settings.name.get to fetch the same value, but one worked and one failed. Huh? Many posts say it gets a 'user' setting (such as profile.language), but if so then I would have expected failure in all my cases. My setting has community/category/board scopes, but only the community level setting has data. I eventually fixed my problem by using "community.settings.name.get". I still do not know why one component worked and one failed but using settings.name.get alone is questionable to me, and the docs use different terms and are not totally clear. What is clear from all the posts I read is that other people have also experienced confusion with this. This article says that it's a community setting, but if so then why did one fail? So I would offer a suggestion for anybody using this (particulary across different scopes/pages) that you may want to consider a more explicit reference such as: community.settings.name.get coreNode.settings.name.get (not sure if there are others?) Of course, you can avoid this and use a REST API call with the specific path to the setting instead.234Views4likes0Commentslia-mark-empty class
Does anybody know why components get marked with the ‘lia-mark-empty’ class and contain no content? I wanted to add the ‘primary-post-button´ component to our home page (category) quilt, just like it is in the ForumPage quilt. Yet when I do this it does not display, and instead puts an empty DIV there with this class name. Works fine on the ForumPage, but not the CategoryPage. Why?130Views0likes1CommentRe: last_chance_html versus "Page Hitbox Content" in wrapper
Hi Claudius, They are both at the end of the page after 99.9% of the HTML before the ending body tag, but they are separated by some JavaScript. The Page Hitbox content comes first, right after the footer and closing lia-page DIV, and followed by a bunch of Lithium JavaScript code (100+ lines in our pages). The content in the last_chance_html is literally at the very end because it is placed immediately before the closing </body> tag. In our case, we put our script tags in the Page Hitbox so they load after the HTML as is usually recommended. As for last_chance_html, I also use it for the one hoverCard.js file for Lithium's Profile Hover Cards which recommended putting it there, but I'm sure you could use it for other things. So in our case the page looks like this: <html><head>[...typical header stuff...]</head> <body> <div class="lia-page"> <center> [...all page content including header and footer...] </center> </div> [...Page Hitbox content goes here...] [...Next, lots and lots of Lithium JavaScript code...] [...last_chance_html content goes here...] </body> </html> Hope that makes sense. Robert232Views2likes2CommentsRe: User macros data
I mean the user macros under My Settings/Macros tab. I would expect to find them in user settings rather that the profile, but the point is I don't see them anywhere - not in '/user/id/xxxx/settings' REST calls or related queries. Just wondering if they can be accessed via REST?342Views0likes2CommentsUser macros data
Is there a way to fetch a specific user macro title and body with REST or aother way? I've searched all around but cannot find any information about user macros in the API docs, user resource or profile descriptions, forums, or anywhere. Where is this data stored and how do I get to it?Solved373Views0likes4CommentsRe: 15.8 Release Notes
JohnD, we like the placeholder and although you are removing it I'm glad the text key will remain. We have found a good use for not only the body placeholder mentioned here, but also the subject placeholder key at 'searchBeforePostField.placeholder-text.title' using our own customized messaging. For me there is no harm in adding such features as long as they are optional and/or configurable.215Views0likes0CommentsRe: Custom component repository
I love this idea! I've been able to benefit from some code posts in the past and would be happy to share some of the customizations that I've done. Even if Studio alerts, forking, or other advanced features were not part of an initial repository just having a basic code library where you can put anything from the smallest snippets to full components (including endpoints and macros) would be very useful. For posting or updating it could help to require some meta info about the component such as the release it runs/written on, required settings or other dependencies, usage, description, some reasonable documentation....the usual stuff. Count me in!127Views2likes0CommentsRe: custom code only on 2 pages
Glad that helped. Any reason you don't like contains? You could do a string compare with "==" like many languages, but for the http.request.url method you would have to include the entre URL from 'http' to the end, for your compare. That's why contains is nice because it just valdates the part you need to check. If the URL happens to contain query parameters after the path then you have to know those too since everything after the '?' is also part of the http.request.url. Since those are often dynamic then that would not fly. Or you may want to read about starts_with and ends_with in case they can help.223Views1like1CommentRe: custom code only on 2 pages
The page object doesn't support that. Instead, use the http.request context object which does have a url method. Using that along with the Freemarker contains built-in can do what you want. For example: <#if http.request.url?contains("/t5/path/to/page1") || http.request.url?contains("/t5/path/to/page2")> <code for special pages here> </#if>256Views1like3Comments