PacoVK

Building nightly will download the changed layers of course, containing the fixes. The same you would patch your systems you propably need to redeploy the new container or leave as...

I could use the code on the `fix-root-login` branch 👍 However, i now run into another issue when i try to update multiple account names, even with a wait of...

Also ran into this issue. Just for a reference: due to another small bug fixed in #1186 i was working on the `publishToConfluence` task and i started a bit of...

We could enforce the "old" editor adding the following metadata to the page creation requests ``` "metadata": { "properties": { "editor": { "value": "v1" } } } ``` additionally we...

You would run into an issue with older confluence instances then especially the self-hosted ones. Due to the fact that currently the fallback is always v1 i assume once they...

@arutscheidt @rdmueller concerning the hash the most elegant solution i found would probaply be using ``` hash xxxx ``` this way, the hash is only visible in edit mode and...

#1189 introduces a flag to enable editor v2. Default editor is still v1 and user will get a warning if she enables v2. As of now it seems not possible...

interessting for the table issue, Atlassian is actively working on that right now ([reference](https://jira.atlassian.com/browse/CONFCLOUD-67748))

#1189 merged, which enforces editor version v1. Hence, there is at least a workaround for this issue. We still need to wait for Atlassian to provide more features for v2,...

#1189 can close this since it will help you to stick to a certain editor version. Without enforcing a version Confluence will decide by the content of the page (whether...