ancestorId is not taken into account

[Simon-at-work]

We have the docker container running and want to publish to confluence.

When I use the container to publish the pages they will always be created in the root hierarchy of the confluence space instead of under the ancestorId.

If I use doctoolchain directly after cloning the repository the publishToConfluence works fine and the pages will be created at the desired ancestor.

This is even logged by doctoolchain itself (notice the missing /pages/....)

[rdmueller]

I think we once had a bug where you have to specify the ancestor ID as string in the config, not as number. Could you please give this a try?

[Simon-at-work]

It is already a string but I will try with a number instead and see what happens

edit: tried ancestorID as number with same result as with string

[rdmueller]

we now have a new docker image and we plan to updated it on a regular basis so that it matches the current doctoolchain version.

could you please try see if this is fixed now?

[CruCo]

I noticed that it does only work if the ancestorId is specified as a string.

I tried it with ancestorId=12345 in my docToolchainConfig.groovy file and it failed with the following error message:

If I use ancestorId='12345' everthing works as expected.