Jens Rehsack comments

Results 25 comments of


                                            Jens Rehsack

publishToConfluence FAILED: Content body cannot be converted to new editor format

After deleting the page and run from developer machine with: ``` sno@beaker:docToolchain$ git branch * ng ``` following happened With ``` sno@beaker:docToolchain$ git diff diff --git a/scripts/AsciiDocBasics.gradle b/scripts/AsciiDocBasics.gradle index 7801e995..77ac4915...

publishToConfluence FAILED: Content body cannot be converted to new editor format

As far as I can see, it results in a newer feature of plantUML, which is included in `asciidoctorj-diagram:2.2.x`. I updated that locally and was successful and when rebuild the...

publishToConfluence FAILED: Content body cannot be converted to new editor format

The _About_-Link is hidden behind the _?_ button in top menu - seems that depends on used style. But I found it thanks to the hint ;) `Confluence 1000.0.0-bc53697e6f14 `...

publishToConfluence FAILED: Content body cannot be converted to new editor format

https://github.com/docToolchain/docToolchain/pull/889 created

publishToConfluence FAILED: Content body cannot be converted to new editor format

Of the confluence version page?

publishToConfluence FAILED: Content body cannot be converted to new editor format

@rdmueller here it is ;)

publishToConfluence FAILED: Content body cannot be converted to new editor format

The PR solved my issue, a colleague run into a similar. I think, the error message hides several errors behind the scenes. I did into it beginning next work week...

to_json is double encoding UTF8?

I run into the same problem (hidden by fuzzed encoding issues solved thanks to @tux) and correct flagged and encoded utf8 strings fed to Dancer2 were double encoded. As a...

to_json is double encoding UTF8?

We use ``serializer => "JSON"`` and always return utf8 encoded strings (octet can also be some kind of opaque snmp representation, what we don't use). And yes, those strings contain...

DBD::Sponge corrected and lazy default PRECISION

Hi @pilcrow would you please be so kind and re-submit a rebased PR with tests and commented changes? For me it's difficult to guess where the patch stands as I'm...