• 97
    • 55
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      It can be very usefull to have an abillity to switch confluence in read-only mode. During our last problems with database, which is hosted several application including Confluence and Jira, all mentioned services was unavailable. It is desirable to be able to run some kind of backup instance of Confluence in read-only mode: data can be searched and viewed, but not modified. This could decrease downtime during upgrade, too.

      Several members of our team really suffer, if they havn't loved wiki online.

      Atlassian Update - June 2018

      Read-only mode is now available in our Data Center deployment option from version 6.10 (release notes), to help admins perform routine maintenance, recover from unexpected problems, or prepare to migrate content to a new site. Admins can temporarily put their site in "read-only mode" to limit the actions that end users can do. Users will be able to view pages and their history, but not create, edit, comment, copy or move content.
      If you own an add-on/app for Confluence, check out the How to make your add-on compatible with read-only mode.

      If you are a Server customer interested in this feature, please vote on CONFSERVER-55071: Allow non-Data Center customers to switch Confluence to read-only mode. It would be great if you could also articulate how you would intend to use this feature.

      Cheers,

      Adam Barnes - Confluence PM

            [CONFSERVER-6390] Allow to switch Confluence to read-only mode

            Syed Ali added a comment -

            Syed Ali added a comment - How does this relate to https://jira.atlassian.com/browse/CONFSERVER-52686  ?  

            (sigh) - now +ing the new issue.

            Rick Carini added a comment - (sigh) - now +ing the new issue.

            nowayride added a comment -

            @sbrannen this issue was opened before datacented existed. All feedback in this issue was explicitly for non datacenter. Why do we have to vote again and wait another 12 years?

            nowayride added a comment - @sbrannen this issue was opened before datacented existed. All feedback in this issue was explicitly for non datacenter. Why do we have to vote again and wait another 12 years?

            rs1,

            We're tracking interest for read only mode in non-DC Confluence installs at CONFSERVER-55071. Please vote for and comment on that ticket so that the development team can see how valuable this would be for non-DC customers.

            Regards,
            Stephen Brannen | Atlassian Support

            Branno (Inactive) added a comment - rs1 , We're tracking interest for read only mode in non-DC Confluence installs at CONFSERVER-55071 . Please vote for and comment on that ticket so that the development team can see how valuable this would be for non-DC customers. Regards, Stephen Brannen | Atlassian Support

            Hi @abarnes 

            the issue was filed for CONFSERVER. As I appreciate a solution for Confluence Data Center, this issue is NOT RESOLVED for server. Opening a new issue for the same topic again is, lets face it, not a solution.

            Be honest, don't f#%&% with the customer and clearly state that this feature will only be available for data center customers for the next years. Then we would know where we're up to & might considering switch to data center or, maybe, another solution.

            Just my 2c

            Jan-Peter

            Jan-Peter Rusch added a comment - Hi @abarnes  the issue was filed for CONFSERVER. As I appreciate a solution for Confluence Data Center, this issue is NOT RESOLVED for server. Opening a new issue for the same topic again is, lets face it, not a solution. Be honest, don't f#%&% with the customer and clearly state that this feature will only be available for data center customers for the next years. Then we would know where we're up to & might considering switch to data center or, maybe, another solution. Just my 2c Jan-Peter

            Well some of you probably know this but Server version and Data Center version is basically the same application, you download the same binaries and libraries. The only difference is some configuration files and the license. So when such a "feature" is implemented, then its available for both of them in the meaning that the code is there. Analyzing the "maintenanace" feature source code you get this:

            if (!licenseService.isLicensedForDataCenterOrExempt()) {
                throw new ServiceException("The instance is not a Data Center");
            }
            

            So implementing it for the Server version should be simple enough as removing those lines (in a very crude simplification).
            Now Atlassian is a big corporate family right now, so it's not a surprise that they make decision based mostly on profit. Well it's their product and they have the right to do so. And their policy against server customers is known since several years ago when they announced that, with a growing cloud customer base.

            Of course I also think that with such policies they should stop the PR marketing and remove one of their values from the list (You all know which I'm referring to) and replace it with "We care mostly about profit now". But still they do have the right to implement all the policies they wan't to. And we as customers can do only one thing: find a better product.

            Ireneusz Lepel added a comment - Well some of you probably know this but Server version and Data Center version is basically the same application, you download the same binaries and libraries. The only difference is some configuration files and the license. So when such a "feature" is implemented, then its available for both of them in the meaning that the code is there. Analyzing the "maintenanace" feature source code you get this: if (!licenseService.isLicensedForDataCenterOrExempt()) { throw new ServiceException( "The instance is not a Data Center" ); } So implementing it for the Server version should be simple enough as removing those lines (in a very crude simplification). Now Atlassian is a big corporate family right now, so it's not a surprise that they make decision based mostly on profit. Well it's their product and they have the right to do so. And their policy against server customers is known since several years ago when they announced that, with a growing cloud customer base. Of course I also think that with such policies they should stop the PR marketing and remove one of their values from the list (You all know which I'm referring to) and replace it with "We care mostly about profit now". But still they do have the right to implement all the policies they wan't to. And we as customers can do only one thing: find a better product.

            This issue has NOT been resolved! This is just marketing bull$ and you know it!

            Where is that Atlassian from 10y a go, trying to build best product available? Well, after this I guess forever gone...

            Patrik Cevela added a comment - This issue has NOT been resolved! This is just marketing bull$ and you know it! Where is that Atlassian from 10y a go, trying to build best product available? Well, after this I guess forever gone...

            Sad indeed. I think this may be the moment Atlassian finally, definitively jumped the shark.

            Carter Snowden added a comment - Sad indeed. I think this may be the moment Atlassian finally, definitively jumped the shark.

            Vlad added a comment -

            Hi,

            I know this issue is closed - but, seeing all of this happening:

            • This feature being requested 12 years ago.
            • This feature (very basic in its nature) gets implemented only for Data Center version.
            • Atlassian makes a marketing splash with this feature and closes this ticket.
            • And paying Confluence Server customers are left with nothing, this issue is closed, and they are asked to make a separate request.

            ... all of this together makes me said.

            I've been a Confluence admin (with non-zero input into purchase decisions) for about 10 years.  I may use my non-zero input next time.

            Vlad added a comment - Hi, I know this issue is closed - but, seeing all of this happening: This feature being requested 12 years ago. This feature (very basic in its nature) gets implemented only for Data Center version. Atlassian makes a marketing splash with this feature and closes this ticket. And paying Confluence Server customers are left with nothing, this issue is closed, and they are asked to make a separate request. ... all of this together makes me said. I've been a Confluence admin (with non-zero input into purchase decisions) for about 10 years.  I may use my non-zero input next time.

            nowayride added a comment -

            This issue was hijacked and now used for marketing to upsell people to datacenter. We just got a marketing email for https://www.atlassian.com/webinars/software/introducing-read-only-mode-for-confluence-data-center

            To help teams minimize planned downtime in Confluence Data Center, we're introducing read-only mode, a top-voted feature request. 

            This was top voted for non-datacenter

            nowayride added a comment - This issue was hijacked and now used for marketing to upsell people to datacenter. We just got a marketing email for https://www.atlassian.com/webinars/software/introducing-read-only-mode-for-confluence-data-center To help teams minimize planned downtime in Confluence Data Center, we're introducing read-only mode, a top-voted feature request.  This was top voted for non-datacenter

              Unassigned Unassigned
              4d1419c1def8 Jozef Babjak
              Votes:
              348 Vote for this issue
              Watchers:
              186 Start watching this issue

                Created:
                Updated:
                Resolved: