Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Please reopen CONFSERVER-22874 and make page version history use immutable versions of images

As of Confluence 7.13.0, you can upload a new and completely different version of an image, and it will not change the page history: if you are working on a page named Foo and it is currently at version 2, and you upload a newer version of an image, 

This is a serious bug. It means that the items in the page history are not immutable, and they can change image content, without any way to go back and audit and see exactly what the page looked like as of a particular point in time.

Please reopen CONFSERVER-22874, which was identified in 2011 but dismissed as "Not a bug".

1 comment

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 06, 2022

The Community is not a place to ask for this, it's not where Atlassian looks for getting features or ideas, and it's definitely not anything they look at as a source for "please reopen".

The behaviour you describe is not what Confluence is designed for, hence the "close, not a bug" response.  I don't think you're going to get any traction on this one here.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events