nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Creating page public link does not work after first use

David Washbrook

I am able to create a public link for one page but when I try to do it for additional pages setting the public link does not work.

I found that the workaround is to open the next page in edit mode and then close the page. The public link can then be set. I have to repeat this for each additional page that I want to make public.

Accepted answers

All comments

Tomislav Tobijas

Hi @David Washbrook ,

Can you maybe share what happens when you turn on public link for this second page? Also, I'm guessing both of these pages have been published?

I've checked JAC bug tracked but couldn't find any open bugs related behavior you've mentioned.

Also, I've tested generating public links on our test instance (for multiple pages) but I couldn't replicate this.

Cheers,
Tobi

David Washbrook

Hi @Tomislav Tobijas ,

When I try to turn on the public link for the second page nothing happens at all. There is no response to my clicks. The pages I have tried this on are all published.

Tomislav Tobijas

@David Washbrook have you maybe tried using different browsers to see if this happens there as well? Also, are other users experiencing this too?

Potentially, you can check what's going on when you open browser DevTools/console (e.g. Chrome), but I would suggest reaching out to Atlassian Support as they can provide better assistance when it comes to these backend issues.

Cheers,
Tobi

Jessica_j1vjtw

Hi @David Washbrook

I'm sorry to hear you are having issues creating public links currently.
We'll try to find out what could be causing it, and depending on the case, if we cannot find why here, we can continue on a support ticket, so we can analyze the possible issues through the logs and a har file generated by you, okay?

At our side, we weren't able to reproduce this issue, so it seems the public links feature is working as expected for now.

Depending on the page that the public link is trying to be enabled, the public link might not be possible to turn it on (page is restricted, you dont have the permission/restriction to edit the page) or even if the page is on the legacy editor (public links are only available for the current editor).

However, if the public is available after applying the workaround mentioned and is not under one of the motives above that could block you from enabling it (considering the space and site is allowing public links), we would suggest the tests that Tobi shared, as well trying to disable all of your browser extensions and in incognito mode to see if this still happens.

As another test, we would ask if this happens when using another device and if in the same device, if using a different network (another wifi or even the mobile connection 4G or 5G) if this is still something blocking from creating other public links in the same space.

We ask for those tests as sometimes, some of our services could be blocked by a configuration in the network, software/ service provider or even by the browser extension.

Let me know if any of those tests works, David.

Cheers,
Jessica

David Washbrook

Hi @Jessica , I did all of the above and nothing made any difference.

I checked the console for errors and there are no errors initiated upon clicking the Public Link toggle with the first or subsequent pages. However, there are many errors and warnings on loading the pages. The warnings are "No value associated with the flagkey:". The errors are either 404 or 409 all relating to failed to load resources including:

409 - https://xxxxx.atlassian.net/gateway/api/engage-targeting/api/v2/user/messages/confluence_page_ownership_changeboarding/start

404 - https://cc-fe-bifrost.prod-east.frontend.public.atl-paas.net/assets/master/force-update.json

409 - https://xxxxx.atlassian.net/gateway/api/engage-targeting/api/v2/user/messages/shareButton-shareToSlack-spotlight/start

409 - https://xxxxx.atlassian.net/gateway/api/engage-targeting/api/v2/user/messages/cc-watch-page-spotlight-nudge/start

Also this error message:
Refused to evaluate a string evalLegacyConnectInlineScripts.ts as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'report-sample' 'nonce-98ba46b2b3de41a7929ea0c8f4aeedd2' 'unsafe-inline' 'strict-dynamic' https:".

There are numerous other messages.

Jessica_j1vjtw

Thanks, @David Washbrook

At this point, I believe we would need to investigate further on your site and try to replicate the issue and gather more information.

That said, I created a ticket on your behalf to request data access to your site, if that is okay, and we will continue the investigation from there.

Please feel free to add any additional comments here and check updates from our team: https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-1085390

Cheers,
Jessica

David Washbrook

@Jessica thank you for your assistance. The support team have contacted me.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud