ContributionsMost RecentMost LikesSolutionsRe: GDPR ComplianceGreat GDPR info - we can never have enough. I have been batching the .JSON files for community data for a few test users. I don't see any reference to Private Messages. Can you tell if if they are included and I missed them or they are on a future release to be included in the batch .JSON file. Thank you JasonRe: Override Master CSS visited link on Category Pages Peter, thanks for the info. Cheers ~jm Re: Override Master CSS visited link on Category Pages Thank you - the exact work around I was looking for. Cheers ~jm Override Master CSS visited link on Category Pages All, I'm attempting to create four microsite pages on the community for separatevendors. The tabs on the page are reading the main visited link causing them to be red, how can I override the CSS for these four separateCategory pages? In one case the OEM background for the active tab is red rendering it invisible. I'm attempting to create four microsite pages on the community for separatevendors. The tabs on the page are reading the main visited link causing them to be red, how can I override the CSS for these four separateCategory pages? In one case the OEM background for the active tab is red rendering it invisible. I've got some one page CSS and JS running the tabs for the main component but haven't figured our to over-ride the master template. 1. https://community.brocade.com/t5/OEM-Lenovo-Brocade-Resource-Page/ct-p/OEM-Lenovo-Brocade-Resource-Page - temporarily turned off the active red tab so the site is usable. 2. https://community.brocade.com/t5/OEM-HPE-Brocade-Resource-Page/ct-p/OEM-HPE-Brocade-Resource-Page It's probably obvious, but I'm having a tough time. SolvedHelp with Endpoint - escaping errors in description field I've got an endpoint that is being consumed by our parent domain to power portlets on AEM. Recently, errors started popping up surrounding the description field. The errors are cryptic so I've been modifying usernames and posts which seemed to fix that error only for one more to popup. I do not have any developer support from my agency nor do I have funds to engage Lithium professional services. Has anyone run into issues with content causing errors in your endpoints? If so how did you solve the issue? Any help would be appreciated. Below is the custom endpoint created to power a portlet with blog and forum content. Thank you Jason http://community.brocade.com/dtscp75322/plugins/custom/brocade/dtscp75322/forums_blogs_desc_for_search <#include "test_macro.ftl" /> <?xml version="1.0" encoding="utf-8"?> <channel> <#assign posttime= http.request.parameters.name.get("posttime","1388563200000")?js_string/> <#assign limit= http.request.parameters.name.get("limit","5000")?js_string/> <#assign x = rest("2.0","/search?q=" + "SELECT * FROM messages WHERE depth = 0 AND conversation.style in ('forum', 'blog') and post_time > ${posttime} LIMIT ${limit} OFFSET 0"?url) /> <#list x.data.items as message> <item> <title>${message.subject?xml}</title> <link>${baseUrl}${message.view_href}</link> <pubDate>${message.post_time?date}</pubDate> <last_reply_time>${message.conversation.last_post_time?date}</last_reply_time> <last_edit_time>${message.current_revision.last_edit_time?date}</last_edit_time> <type>${message.conversation.style}</type> <author>${message.author.login}</author> <labels> <#assign pre_lbl = restadmin("/messages/id/${message.id}/labels/").labels> <#list pre_lbl.label as lbl> "${lbl.text?xml}" </#list> </labels> <tags> <#assign pre_tags = restadmin("/messages/id/${message.id}/tagging/tags/all").tags> <#list pre_tags.tag as tags> "${tags.text?xml}" </#list> </tags> <views> <#assign viewcount = restadmin("/messages/id/${message.id}/views/count").value> "${viewcount}" </views> <kudos> <#assign kudoscount = restadmin("/messages/id/${message.id}/kudos/count").value> "${kudoscount}" </kudos> <#assign blurb = utils.html.stripper.from.gdata.strip(message.teaser)> <description><#if blurb?has_content> ${blurb?xml} <#else> <#assign body = utils.html.stripper.from.gdata.strip(message.body)> <#if body?length gt 250> ${body?substring(0, 250)?xml}... <#else>${body?xml}</#if> </#if> </description> </item> </#list> </channel> Endpoint Question: Description Breaking into Multiple lines I'm having an issue with an endpoint that I am publishing which is being picked up by an AEM service. The description is broken up into multiple lines. The developer on the AEM side is asking me to publish on one line. Has anyone run across this problem? Using appplication/rss+xml as the format. This is what it looks like published. Thank you Jason