Databases
StackOverflow2013
Postsdbo
POConfluence API: How to find out which css/js resources a pages uses?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConfluence API: How to find out which css/js resources a pages uses?
    text
    copied!<p>We have an in-house plugin that exports a Confluence space. The space css file is already included, but this is far from complete. I've browsed through the Confluence API, but I can't find anything that will tell me which resources a page (including macros) needs to be rendered properly. Basically I need something that allows me to reproduce the following for css and js:</p> <pre><code>&lt;!-- include system css resources --&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/34/_/download/superbatch/css/batch.css" media="all"&gt; &lt;!--[if lt IE 9]&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/34/_/download/superbatch/css/batch.css?conditionalComment=lt+IE+9" media="all"&gt; &lt;![endif]--&gt; &lt;!--[if IE 9]&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/34/_/download/superbatch/css/batch.css?conditionalComment=IE+9" media="all"&gt; &lt;![endif]--&gt; &lt;!--[if lte IE 9]&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/34/_/download/superbatch/css/batch.css?conditionalComment=lte+IE+9" media="all"&gt; &lt;![endif]--&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/34/_/download/superbatch/css/batch.css?media=print" media="print"&gt; &lt;!--[if lt IE 9]&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/4e59e07231dd67576ce6f003b6a8095e/_/download/contextbatch/css/page/batch.css?conditionalComment=lt+IE+9" media="all"&gt; &lt;![endif]--&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/4e59e07231dd67576ce6f003b6a8095e/_/download/contextbatch/css/page/batch.css" media="all"&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/75877fb710740f0fb2358dd832691580/_/download/contextbatch/css/plugin.quick.comment.pre/batch.css" media="all"&gt; &lt;!--[if lt IE 9]&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/767f156fe1e9f3d7a21cf551551d1dd8/_/download/contextbatch/css/viewcontent,main/batch.css?conditionalComment=lt+IE+9" media="all"&gt; &lt;![endif]--&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/767f156fe1e9f3d7a21cf551551d1dd8/_/download/contextbatch/css/viewcontent,main/batch.css" media="all"&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/62d979954d4d69b0a4870d806bfe4e43/_/download/contextbatch/css/atl.general/batch.css" media="all"&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/1.3.4-SNAPSHOT/_/download/batch/com.jfb.confluence.plugins.latex:styles/com.jfb.confluence.plugins.latex:styles.css" media="all"&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/1.0-SNAPSHOT/_/download/batch/com.jfb.confluence.plugins.numcapt:styles/com.jfb.confluence.plugins.numcapt:styles.css" media="all"&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/2.0.2/_/download/batch/com.atlassian.confluence.plugins.pagetree:pagetree-resources/com.atlassian.confluence.plugins.pagetree:pagetree-resources.css" media="all"&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/5/_/styles/colors.css?spaceKey=HELP" media="all"&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/4.2.1/_/download/resources/com.atlassian.confluence.plugins.doctheme:documentation/default-theme.css" media="all"&gt; &lt;link type="text/css" rel="stylesheet" href="/s/en_GB/3277/32/4.2.1/_/download/resources/com.atlassian.confluence.plugins.doctheme:documentation/splitter.css" media="all"&gt; &lt;!-- end system css resources --&gt; </code></pre> <p>Any ideas? This must be possible!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload