Include+ macro and cache-macro

Hi,

we are using an include library witth Scroll Versions an ST (both 3.7.6; Con: 5.10.8). The drawback of the include library is the search. So we tested the approach of Sarah Maddox (https://ffeathers.wordpress.com/2011/05/15/making-the-include-macros-content-appear-the-confluence-search-results/ ). The search itself runs perfectly. But unfortunately the Cache-Macro of Bob Swift doesn't work together with the include+ macro properly. Usually all inlcude+ macros are converted to "normal" include page macros after publishing the pages to a new/existing space. But if the include+ macro is enclosed by the Cache-macro it stays an include+ macro with several side effects. a) On some pages the included content is highlighted even if you have disabled the setting "highlight included content". b) When you edit the published page (in target space) and choose "go to included page" you are directed to the include library page of the private master space. The weird things is, that the normal user, who has no rights on this space, can see the content. And if the user follows the link (which he can see and follow because of the hightlighting), he is directed to the include library of the target space.

c) The k15t-exando doesn't work either included by the Cache-Macro.

Our questions are:

Why is the include+ macro not converted to an include page macro after publishing? Do you know further problems using the Cache-Macro together with Scroll Versions? What could be a workaround?

Greetings,

Volker

Roman Serazhiev August 28, 2018 14:01

Hi Volker.

This is a known issue with Cache macro and our apps: https://k15t.jira.com/browse/VSN-2178. There is no workaround we are aware of. There could be further problems when using this macro in translated or versioned spaces.

There is no workaround unfortunately.

What is the end goal in this situation for you? To show pages from the Include Library space in search results?

Cheers,
Roman.

Volker Weinreich August 29, 2018 06:52

Hi Roman,

thanks for your reply. I haven't been aware of this ticket.

I'm not quite sure how we handle these problems. We are still in the test phase. There are three problems:

1. Highlighting of included content -> With CSS we can hide the highlighting -> solved

2. k15t-exando seems to work now (If not, we can replace it by expand macro) -> solved

3. Not transforming the include+ -> not solved.
What is the actual consequence of this behavior? I mean: Does it matter as long as the restricted user sees the right content?

Do you know specific problems with translated pages?

If we will not use the cache macro, we will go on with creating a lot of labels on the displayed pages and still not showing the included pages.

Include+ macro and cache-macro

Comments

Didn't find what you were looking for?