-
Suggestion
-
Resolution: Unresolved
Summary
Feature request made in developer support: https://ecosystem.atlassian.net/browse/DEVHELP-3321
In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation:
"You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1]While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user.
I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained.
My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set.
[1] https://developer.atlassian.com/cloud/confluence/modules/custom-content/
- relates to
-
DEVHELP-3321 Loading...
[AI-896] Don't index/display a raw body when "ac:custom-content:search-body" is set
Component/s | Original: XP - Content Search [ 61005 ] | |
Component/s | New: XP - Content Search [ 75299 ] | |
Key | Original: CONFCLOUD-67909 | New: AI-896 |
QA Demo Status | Original: Not Done [ 14330 ] | |
QA Kickoff Status | Original: Not Done [ 14234 ] | |
Project | Original: Confluence Cloud [ 18513 ] | New: Atlassian Intelligence [ 23110 ] |
Component/s | Original: Search - Indexing [ 46493 ] | |
Component/s | New: XPC - Content Search [ 61005 ] |
Component/s | New: Search - Indexing [ 46493 ] | |
Component/s | Original: Ecosystem [ 49196 ] | |
Component/s | Original: Macros - 3rd Party [ 46352 ] |
Rank | New: Ranked lower |
Rank | New: Ranked lower |
Rank | New: Ranked lower |
Workflow | Original: JAC Suggestion Workflow [ 3559421 ] | New: JAC Suggestion Workflow 3 [ 3630709 ] |
Labels | Original: cc-integration cc-integrations devhelp ecosystem | New: cc-integration cc-integrations devhelp ecosystem grooming-ready |
Description |
Original:
h3. Summary
Feature request made in developer support: https://ecosystem.atlassian.net/browse/DEVHELP-3321 {quote} In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation: "You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1] While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user. I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained. !Screenshot 2019-08-16 at 11.22.54.png, height=300! My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set. [1] https://developer.atlassian.com/cloud/confluence/modules/custom-content/ {quote} |
New:
h3. Summary
Feature request made in developer support: [https://ecosystem.atlassian.net/browse/DEVHELP-3321] {quote}In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation: "You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1] While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user. I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained. !Screenshot 2019-08-16 at 11.22.54.png|width=745,height=419! My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set. [1] [https://developer.atlassian.com/cloud/confluence/modules/custom-content/] {quote} |
Description |
Original:
h3. Summary
Feature request made in developer support: https://ecosystem.atlassian.net/browse/DEVHELP-3321 {quote} In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation: "You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1] While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user. I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained. !Screenshot 2019-08-16 at 11.22.54.png|thumbnail! My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set. [1] https://developer.atlassian.com/cloud/confluence/modules/custom-content/ {quote} |
New:
h3. Summary
Feature request made in developer support: https://ecosystem.atlassian.net/browse/DEVHELP-3321 {quote} In my Mind Map App, I store the mind map data in XML format in the raw body of a custom content type as proposed by the documentation: "You can define custom content to support a content body with a type of raw. This is useful when you want to store, for example, stringified JSON to the content." [1] While this works well, the raw body still gets indexed and displayed in the confluence search results. And seeing a bunch of XML code in the search results is probably confusing for the user. I tried using the "ac:custom-content:search-body" property which states: "The content of this property will also be used in displaying the excerpt text for search result." [1] but the content of that property was only added to the excerpt text and the XML code still remained. !Screenshot 2019-08-16 at 11.22.54.png, height=300! My proposal is not to index/display a raw body - at least when "ac:custom-content:search-body" is set. [1] https://developer.atlassian.com/cloud/confluence/modules/custom-content/ {quote} |