0

Bug of register_publish?

Hi there,

We find there is something wrong with the register_publish function. If there are two Local File Storages with the same configurations which defined on the Preferences page, the register_publish function will not register the right local file storage to the path field of published file. For example, there are two local storages(Storage01, Storage02) defined like below:

Storage01:

Windows Path: I:\projectFiles

Storage02:

Windows Path: I:\projectFiles

The Storage02 will be used as a root of the project , i publish a file by the register_publish function: 'I:\projectFiles\proj001\file.v003.mb'.
When you view the result of the path field of the published file, you will find that local_storage in the field is Storage01, but not Storage02 which used as a root of the project. And this also effort the result of util.find_publish function.
Thanks,

Zhy

댓글 2개

  • 0
    Avatar
    Manne Öhrström

    Hello!

    Toolkit sometimes needs to figure out which storage a certain path belongs to. If you have two different storages both pointing at the same path, toolkit doesn't know which storage you refer to, so it will choose the first one it finds. The easiest way to solve this would be to rationalize the storage setup, so that there is only one storage which points at I:\projectFiles. Would this be an option at all? How come you ended up with two storages pointing to the same location in the first place? Curious to hear more about this use case!

    Many thanks!

    Manne

  • 0
    Avatar
    Zhy

    Hi Manne,

    We just mount two network locations to I disk,  And we use the name of storages as environment variables which will be used in project tools developments. If that is not a bug of toolkit, we will find other ways to avoid this.

    Many thanks,

    Zhy

댓글을 남기려면 로그인하세요.