Customize the page of a Space Overview? (confluence/wiki/spaces/xxx/overview)?

[Thomas Schittli]

Good afternoon

I'm very sorry to ask the honorary working community for help
while Atlassian makes a lot of money and raise prices every year.
But the Atlassian Support usually needs years to solve Problems (there are very many multi-year open issues), so here I am:

Is there a way to customize the Space Overview Page? 

For example, we would like to remove:

• The Dropdown list with the other spaces
• Space settings
• … if possible, we would like to remove the whole left column

Thanks a lot for any help & light,
kind regards,
Thomas

[JP _AC Bielefeld Leader_]

Hi Thomas,

in my case specific problems to my installation have been solved by the Atlassian support team in a couple of hours or days.

Try customize the viewspacesummary.vm file located in

CONFINST/confluence/spaces

There are some more space related files where you can modify the decorators.

Best

JP

[Thomas Schittli]

Hello Jan-Peter

Thank you very much for your answer!,
it's true, we also have successful Atlassian Support requests, but 8 of 10 are not successful, they just send us links to well known and long time open issues. :-(

It looks like Cloud-Customers cannot modify viewspacesummary.vm

I've found this Doc: https://confluence.atlassian.com/doc/customize-space-layouts-139512.html

But although Atlassian does not declare any restriction to cloud-customers, the Layout settings are missing in Look and Feel in the Space tools.

Therefore it looks like it's not possible to change the annoying default site summary layout.

Thanks a lot,
kind regards,
Thomas

[Nic Brough -Adaptavist-]

To be fair, they do explicitly state that you have no access to hacking the code behind a Cloud install, and that space layouts are not editable.  It's on the "cloud restricted functions" mentioned when you sign up.

[Thomas Schittli]

... yes, we can ask google to answer Atlassians issues, if we pay some 1000$ per year, we expect to get information like this limitation where it must be: in the product Docs. it couldn't be that hard to assign the three Tags - one for each product type.

Additionally, modifying the layout is not related to hacking "code behind". We're pretty sure there is an open ticket about this issue ... and we bet it is ignored since many years :-(