Natkinson
Genius
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Requesting feedback on our Dev Lab!
A big +1 to everythingallensmith81mentioned in his comment. I think it was nice to see the roadmap and ideas behind building Aurora the way it's built, but having more of an actual "lab" would have been nice. I'm still a bit of a n00b so some of this is intimidating. I'd love to have labs similar to what Allen and others have suggested, a bit of theory/best practices on Aurora and then some demonstration and working together or sharing ideas and code snippets. I did appreciate getting a high level overview of how Aurora works and how to navigate the dev docs. I also enjoyed the breakouts to see how things are built. Another suggestion is providing some pre-built open source components built using best practices that we can then use as a starting point in the labs and "hackathons". This would also provide some easy references for documentation and best practices. Overall, this was an awesome event to attend and I hope to see more similar gatherings and an evolution of these types of events. Some people may prefer just the "product marketing style"/overview style meetings while others would prefer the hands-on build it together style meetings. I did notice a pretty big drop-off in attendance when we broke into smaller groups, so breaking these into two different webinars may be helpful.401Views2likes0CommentsRe: Custom pagination numbers aren't lining up
Akenefickyeah in testing more I'm sure the if statements aren't the problem either. There just seems to be something overriding either the total items or total pages fed to the pagination component but I can't seem to find what is overriding it. If I click anything beyond page 8 it just refreshes the page back to page 8, despite the pagination component showing pages beyond page 8. Incidentally, the first if statement section in my first code example above (where tabParam = "latest"), that content ends at page 8 and works correctly. It's almost like the pagination for the second, longer section is retaining some data from the first section, but I can't figure out if that's the case or why that would be happening268Views0likes0CommentsRe: Custom pagination numbers aren't lining up
AkenefickI've never had an issue using this either and I've used it in dozens of custom components. However, this is the first time I've used it to display different feeds using an if statement and the first time I've used it on a ForumPage quilt, so I wonder if one of those is causing the issue here. "rest_20" is just a variable pulling in from a macro I'm using to build out the message feeds. It just declares the api version, in this case "2.0".269Views0likes0CommentsRe: Custom pagination numbers aren't lining up
Tried a modified version of this changing the parameter and the pagination is still sending me to page 7, but now the pagination component isn't updating (it's stuck on displaying page 1) and it never progresses to further pages even though the URL changes <#elseif tabParam = "activity"> <#assign pageSize=5 /> <#assign pageNum=webuisupport.path.rawParameters.name.get("items", "1") /> <#assign paginationOffset=(pageNum?number - 1) * 5 /> <#include "forum_feed_macro" /> <#assign msgCountQryAll=rest("2.0","/search?q=" + "SELECT count(*) FROM messages WHERE board.id='${currentBoard}'"?url).data.count /> <#assign res = liql(rest_20, "SELECT ${querySelect} FROM messages where board.id = '${currentBoard}' ORDER BY post_time desc LIMIT ${pageSize} OFFSET ${paginationOffset}") /> <@renderListResponse type="message" response=res render=messageRenderFullMessage /> <#assign pageable_item=webuisupport.paging.pageableItem.setCurrentPageNumber(pageNum?number).setItemsPerPage(5).setTotalItems(msgCountQryAll?number).setPagingMode("enumerated").build /> <@component id="common.widget.pager" pageableItem=pageable_item /> </#if> I don't understand how to make this work correctly. I understand why "page" as a parameter doesn't work, but don't understand how to implement an alternative293Views1like0CommentsCustom pagination numbers aren't lining up
I'm getting a weird issue with a custom pagination component I'm trying to build. I have two tab items that I'm using a URL parameter to switch between. For each tab I'm using Freemarker to determine which tab is displaying and then build a feed of messages based on that. With the pagination, here's my code: <#if tabParam = "latest"> <#assign pageSize=settings.name.get("layout.messages_per_page_linear")?number /> <#assign pageNum=webuisupport.path.parameters.name.get("page", 1 ) /> <#assign paginationOffset=(pageNum - 1) * pageSize /> <#include "forum_feed_macro" /> <#assign msgCountQry=rest("2.0","/search?q=" + "SELECT count(*) FROM messages WHERE board.id='${currentBoard}' AND depth=0"?url).data.count /> <#assign res = liql(rest_20, "SELECT ${querySelect} FROM messages where board.id = '${currentBoard}' AND depth=0 ORDER BY post_time desc LIMIT ${pageSize} OFFSET ${paginationOffset}") /> <@renderListResponse type="message" response=res render=messageRenderFullMessage /> <#assign pageable_item=webuisupport.paging.pageableItem.setCurrentPageNumber(pageNum).setItemsPerPage(pageSize).setTotalItems(msgCountQry?number).setPagingMode("enumerated").build /> <@component id="common.widget.pager" pageableItem=pageable_item /> </#if> <#if tabParam = "activity"> <#assign pageSize=settings.name.get("layout.messages_per_page_linear")?number /> <#assign pageNum=webuisupport.path.parameters.name.get("page", 1 ) /> <#assign paginationOffset=(pageNum - 1) * pageSize /> <#include "forum_feed_macro" /> <#assign msgCountQryAll=rest("2.0","/search?q=" + "SELECT count(*) FROM messages WHERE board.id='${currentBoard}'"?url).data.count /> <#assign res = liql(rest_20, "SELECT ${querySelect} FROM messages where board.id = '${currentBoard}' ORDER BY post_time desc LIMIT ${pageSize} OFFSET ${paginationOffset}") /> <@renderListResponse type="message" response=res render=messageRenderFullMessage /> <#assign pageable_item=webuisupport.paging.pageableItem.setCurrentPageNumber(pageNum).setItemsPerPage(pageSize).setTotalItems(msgCountQryAll?number).setPagingMode("enumerated").build /> <@component id="common.widget.pager" pageableItem=pageable_item /> </#if> My problem here is that the feed created within the second "if" statement, the pagination stops at page 8, even though it's displaying up to 25 pages available. The first section, however, does stop at page 8. I'm wondering if somehow something is getting crossed between the first and second sections. For reference, the variables in the second feed are as follows: "pageSize" = 4 msgCountQryAll = 98 I just don't understand what's going on with my code that's causing the pagination in the second section to get stuck at page 8 even though it's showing up to 25 pages in the pagination component.308Views0likes9CommentsRe: Get Announcement Text from Group Hub
Never mind, I'm just dopey today. I dug a little further and found a very obscure reference to groups being treated like boards somewhere, so it turns out if you need announcement text for a grouphub you need to use a query like SELECT announcements FROM boards WHERE id = 'your_group_hub_id'74Views0likes0CommentsGet Announcement Text from Group Hub
Is there no way to get the announcement info for a group hub via the API? We have queries to get announcement info for communities, categories, and boards, but no group hubs? Is that right or am I just completely missing something here? Is this an oversight on Khoros' part?SolvedRe: Has anyone purchased/implemented FontAwesome Pro?
keithkellyI think if you're swapping icons there's probably a couple ways to go about it. There may be a better way, but what I did was identify the icon used in the default CSS and then adding custom CSS to override the Khoros default. So for the notification bell, we replaced ours with something like this: .lia-header-nav-component-widget .lia-notification-feed-page-link:before { content: "\f0f3"; font: var(--fa-font-light); } for more details:https://fontawesome.com/docs/web/add-icons/pseudo-elements I haven't found another way yet to easily replace built-in default icons.142Views1like1Comment