Cannot access public blog posts on the mobile version on Confluence when not logged in.

[Lauren Hanyok]

Some of our team do not have Confluence accounts but must still have access to our blog posts.  They can see the overview page just fine, but when they click on a blog post, they get the following error:

"That page ID is invalid.  Page IDs can only contain numbers.  Double-check the URL and give it another shot."

The URL contains the name of the blog post as opposed to a pageID.  They can still see the blog posts in desktop mode on their home computers, but we really need the mobile access (we can't afford the more expensive package for more accounts).

Is there a way to force the pageID version of the URL in mobile, do we need to enable something in our settings?  I have found no guidance on this, as everything says we should be able to access the blog posts publicly (the permissions are set for public).

Thanks!

[Sloan]

Hi Lauren,

this is odd. Can you show us an URL for example (only if it doesn't hurt your companies privacy or compliance), the bit after the base-URL. Is every blogpost affected?

If you want to force pageID in the URL just add one of these characters to the title of a blog post or page: ! * ' ( ) ; : @ & = + $ , / ? # [ ]

To learn why this happens look here: https://confluence.atlassian.com/confkb/confluence-page-urls-contain-pageid-instead-of-the-page-title-278692715.html

Cheers
Nick

[Lauren Hanyok]

Hi Niklas!  Thanks for such a speedy response!  Unfortunately I can't share one of the blog posts, but this does affect every blog post.  We used to put ",", ":", and "()" in our post names but they still came up with the same error.  We actually thought it was the problem :/

[Sloan]

And this happens only on the mobile view of Confluence, right? 

Can you tell me on what version of Confluence you are?

[Lauren Hanyok]

Correct, only the mobile view.  The team can see the blog posts on the desktop view no problem.

Confluence Cloud 1000.0.0

[Sloan]

Hi Lauren, if you can, try reaching out to the Atlassian Support.

I think this could be a Cloud Specific problem.

[Lauren Hanyok]

will do, thanks!