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; } } }

"Content body cannot be converted to new editor format" error when updating page content

Leonid Sokolovskiy_0j51li

API call work when I send a request from Postman but not from c# code.

As an experiment I have just get content from a page, and then update page.

If I send request from Postman it works but not from code.

I checked requests in Fiddler and they are almost indentical. There are some Postman specific items in the header.

Any ideas how can I troubleshoot it?

Some addition - actually pages with simple content updated ok.

I would appreciate if somebody provide some hints.

Accepted answers

Leonid Sokolovskiy_0j51li

Ok, I found the problem. Probably I could have found it easier if your error message was actually correct.

The reason that some pages cannot be updated with the error :

Content body cannot be converted to new editor format

there is no User-Agent header!!!!

User-Agent should be set to something - otherwise looks like you have null reference exception during the conversion procedure. This looks like a bug to me.

All comments

Dario B

Hello @Leonid Sokolovskiy ,

If the same exact request works with Postman but it does not work from your code, the problem must be somewhere in your code.

One thing you can do is to modify your code so that it will print to the logs (or to the console) the full request body, the endpoint and method and headers before sending the request.

This way you can compare what is generated by your code with the working request in Postman.

However, since the error in the summary refers to converting the content body in your request to the new format, and since you say everything works fine when updating a simple page, there are chances the issue is related to the representation used in your request or with the body.value or similar (see the workaround of CONFCLOUD-68057 for details).

Now, in case nothing works, can you kindly provide:

The exact steps you follow when testing this with Postman
Endpoint called and method used (I believe it is PUT /wiki/rest/api/content/{id} but please confirm)
Complete request body (remove sensitive data, if any)
Authentication method

Please also confirm you are trying to update a page created with the new editor.

Finally, for the future, please notice that this might not the best place to get help on development related questions. You have much higher chances to get help on development related question using the links you can find in https://developer.atlassian.com/resources. Specifically:

Cheers,
Dario

Leonid Sokolovskiy_0j51li

1. just give you a bit more details of how I did the test

- it the debugger I have a copy and then pasted json content to Postman

- in the code, only 2 statements left

var data = new StringContent(json, Encoding.UTF8, "application/json");

response = await _client.PutAsync(url, data); - client is a standard HttpClient

not that many things could go wrong but I will appreciate your feedback

2. I compared 2 requests in Fiddler and could not find differences

3. And ... for some pages everything works OK. - the same code

I am new to the Confluence development so I will try the developers community.

thank you.

Leonid Sokolovskiy_0j51li

Here is the final json sent both in Postman and in the code (this is the most simple one which does not work)

{"version":{"number":21},"type":"page","title":"page13","status":null,"body":{"storage":{"value":"<table data-layout=\"default\"><tbody><tr><th>XXX</th><th>Location</th><th>Operated By</th><th>Handles Products</th><th>Outbound</th><th>Inbound</th></tr><tr><td>DC 1</td><td>XXX</td><td>XXX</td><td>APP</td><td>x</td><td>Q1 2020</td></tr><tr><td>DC 2</td><td>XXX</td><td>XXX</td><td>FTW</td><td>x</td><td>Q1 2020</td></tr><tr><td>DTC</td><td>XXX</td><td>XXX</td><td>APP, FTW, OMNI</td><td>x</td><td>x</td></tr><tr><td>XXX</td><td>XXX</td><td>XXX</td><td>APP, FTW, OMNI</td><td>x</td><td>Q3 2020</td></tr></tbody></table>Global - EPCIS (EPC Information Service)","representation":"storage"}}}

also tried it with "status" : "current" - result is the same.

Endpoint - PUT https://detego.atlassian.net/wiki/rest/api/content/144606710

I am using Basic authentication.

Do you need more details?

Dario B

Hi @Leonid Sokolovskiy ,

I can confirm that the provided body works fine against a page created with both, new and old editor.

I had to modify it to apply to my instance like below but everything worked fine:

{
"version": {
"number": 2
},
"type": "page",
"status": "current",
"title": "New Editor",
"body": {
"storage": {
"value": "<table data-layout=\"default\"><tbody><tr><th><p>XXX</p></th><th><p>Location</p></th><th><p>Operated By</p></th><th><p>Handles Products</p></th><th><p>Outbound</p></th><th><p>Inbound</p></th></tr><tr><td><p>DC 1</p></td><td><p>XXX</p></td><td><p>XXX</p></td><td><p>APP</p></td><td><p>x</p></td><td><p>Q1 2020</p></td></tr><tr><td><p>DC 2</p></td><td><p>XXX</p></td><td><p>XXX</p></td><td><p>FTW</p></td><td><p>x</p></td><td><p>Q1 2020</p></td></tr><tr><td><p>DTC</p></td><td><p>XXX</p></td><td><p>XXX</p></td><td><p>APP, FTW, OMNI</p></td><td><p>x</p></td><td><p>x</p></td></tr><tr><td><p>XXX</p></td><td><p>XXX</p></td><td><p>XXX</p></td><td><p>APP, FTW, OMNI</p></td><td><p>x</p></td><td><p>Q3 2020</p></td></tr></tbody></table><p><strong>Global</strong>&nbsp;- EPCIS (EPC Information Service)</p>",
"representation": "storage"
}
}
}

Now:

Can you confirm you use basic authentication with email address and API Token and not username and password?
Can you confirm that the REST request always work in Postman, also for those pages that fail from your code?
Also, I can see you have access to 3 instances, d*.atlassian.net, h*.atlassian.net and l*.atlassian.net. Can you let me know against which instance are you sending the request together with date, time and timezone of the last time you get the error so that I can see if I find anything in the logs (please also confirm the error message returned).

Cheers,
Dario

Leonid Sokolovskiy_0j51li

Honestly, I am not convinced.

You are getting null reference exception and I am just passing all required filed in PUT request.

I have made tests for different formats : editor, editor2, view and everything works - and the code is exactly the same except in body (json) formation representations are different.

"representation": "storage"

used different formats here. If we asume that the problem if the body value that we should expect it should not work with other formats.

Leonid Sokolovskiy_0j51li

Ok, I found the problem. Probably I could have found it easier if your error message was actually correct.

The reason that some pages cannot be updated with the error :

Content body cannot be converted to new editor format

there is no User-Agent header!!!!

User-Agent should be set to something - otherwise looks like you have null reference exception during the conversion procedure. This looks like a bug to me.

Bahador.Nosrat

i've been watching this as i'm experiencing the same problem. i'm going to try the user agent.

tangential: i've heard that chrome is going to phase out the use of user agent

Bahador.Nosrat

adding the user agent worked for us as well. thank you @Leonid Sokolovskiy

Leonid Sokolovskiy_0j51li

@Bahador.Nosrat you are welcome

Yurii Petrovskyi

In my case I changed tag to in "value".

Wouter Jonker

This worked for me!

Philip Colmer

In case someone finds this question, as I did, while trying to troubleshoot this problem, I have found another reason why you might get this error back.

If you are creating or updating a page that is set to use the v2 editor and your content is syntactically incorrect in some way, you don't get the syntax error message back, you get the "Content body cannot be converted..." error.

So, if you find yourself getting this error message, try creating a v1-editor page and send the content there and you might get the correct syntax error message back, thus helping to diagnose the problem.

Ayush Ujjwal

I was facing the same issue. I was using python for the requests and was unable to find why it was happening and finally after a lot of debugging and coffee I found the issue might also occur if you have a & in your body.storage.value. Do check it and replace the & with something else.

Kommaraju Ajay Kumar

Hi @Ayush Ujjwal ,
I need & in my url .did you find any workaround for this.
Quick link to my problem : https://community.atlassian.com/t5/Confluence-questions/Content-body-cannot-be-converted-to-new-editor-format-if-my-html/qaq-p/1790375#M216349

Ayush Ujjwal

I haven't found any workaround yet on the problem you are facing. Since & is mandatory in your case there will need some modifications to send the params without the error causing trouble. Will let you know in case I find something. If you get any solution do post here as well. Cheers.

Ayush Ujjwal

I found a solution if it works for you. Replace & in your link with & and check if it works fine. I was able to push the & after replacing.

Stephen Costa

I've only recently stumbled across this error. We have an automation that uses the confluence API to update a page. This process was working correctly until Oct 5 when we started getting the `Content body cannot be converted to new editor format` error.

Same issue in Postman and in our original python code
The user-agent header is supplied
There aren't any `ri:` elements so I don't think there's anywhere to add the `ri:space` key. Maybe I'm wrong?
I don't see anywhere to select Editor v1 when creating/editing a page so I can't try sending the same page content there as suggested.

None of these solutions seem to work for me. Is there any other suggestion? This feels like either a bug on Confluence side or a bad error message I can't get around.

Dario B

Hello @Stephen Costa ,

Can you check if this is the same issue discussed in:

https://community.developer.atlassian.com/t/unable-to-post-content-body-cannot-be-converted-to-new-editor-format/52897/4

Vinci Wu

@Leonid Sokolovskiy

I've only recently stumbled across this error. I updated a table records to wiki page. When I limitd table records to 100, it can work. But I select all records(1000 row), it failed.

update wiki {"statusCode":400,"data":{"authorized":true,"valid":true,"errors":[],"successful":true},"message":"com.atlassian.confluence.api.service.exceptions.BadRequestException: Content body cannot be converted to new editor format"}

payload = {
"type":"page",
"title": f'{wiki_title_name}',
"space":{
"key":"DataScience"
},
"body":
{
"storage":{
"value":html,
"representation":"storage"
}
}
}

"html" is strings include table records with html code.

I don't know if there is long limit in "value" string.

Vinci Wu

It is python code.

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

atl-gruland

atl-adm

atl-dev