When I use a include page macro in a section, the page shows a horizontal scrollbar to the section.
This does not happen to include page macro when not using sections.
Is there a way to get rid of the scrollbar? Because I need sections for page layouy
the horizontal scrollbar is there because the width of the included page is bigger than the width of the section.
You can't disable that. If you would, you will lose content from the original page.
Have a look at your original page. Add line breaks and use smaller images, so that your page is smaller. If it is small enough to fit into your column, the scrollbar should go away.
Thank you for your reply.
I understand what you are saying, but the problem is a little more complicated.
A section takes up a little space, even when it is an single column section, for that reason all my pages that are included are using sections (or else they do not align).
So if I include them in my main page without a section in the main page all goes well.
Now the difficult part starts, if I now use an section in the main page use some column, in a different part, the single column section that contains the page-include now automatically adds a horizontal scrollbar, this because the extra (unnecessary) room needed for the section.
I understand what causes the problem (although I’m not too happy about it) but I do not like the work around that I’m using (not using sections in the main page). It provides my editors with overhead that is unnecessary.
So I was hoping there was a more straightforward solution. Or maybe I'm understanding the problem completely wrong (I really hope so)
Indeed, I have the same problem. I'm trying to build a page made-up of smaller pages, for re-use.
Each of the micro-page is like a single item, made-up of a single section of two columns (description on the left, code example on the right).
But in the main page, i have to use sections to correctly format and align various sections, and then list a few of the micro-pages.
I think the quick solution (as a new feature request) would be for the included page to replace the single column section it is declared into, thus eliminating the need for the scroll bar in the containing section.
I created a feature request for this.
It is not strictly true that the scrollbar only appears if the included page is wider than the section.
If the included page has sections of any kind, the scrollbar appears.
The screenshots I've attached demonstrate that the amount of content on the source page is irrelevant...if it has sections.
Scenario 1 - source page has multiple sections
My source page with very little content.
The page that has the include page macro gets a scrollbar in the section containing my source page.
Scenario 2 - source page has only one section
Here my source page has the exact same content, but only in one section.
Now, the section of the page with the "include page" macro does not get a scrollbar.
Same Problem Here..
I am setting up a Wiki, where on each page i put in the top of the page some infos for the users and a further pagetree macro.
I try to create a "Masterpage" whith those content an i want to reuse it on all the following pages with the page includ macro.. This would be handy, because the information at the Beginning is not complete and maybe in the future has to be updated..
This would mean i have to go through all 200 pages of my Space and replace the infos by hand..
but with the page include macro i could do this i a secound.. and all pages would change simultaniously..
But now with the scrollbar. this aproach doesnt work..
so please improve it.
Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs