Hardcoded Publish Template Path

Development
1

Hi Community,

is there a reason why the publish template path is hardcoded to “default” in many places of ayon_core and other plugins?
Like for example here:

Shouldn’t something like ayon_core.pipeline.publish.get_publish_template_name() be used to solve the path templates based on user settings?

Thanks for sharing your insights!

2

I believe you’re right - yes. @iLLiCiT can likely confirm best what the intended behavior should be.

3

It’s really everywhere. I’m just surprised that this seems to work for everyone else. It also causes the pipeline to store a file at the intended place and then trying to load it from the default path.

4

I guess you’re touching areas which others may not have customized thus far. I haven’t seen the issue reported but it does look iffy looking at the code.

Please do report all the places you find them, create an issue (likely on ayon-core repository?) and if you’re able to PRs are welcome.

5

I can’t, not done by me, it is logic added in avalon/pype 1 that (somehow) stayed in the codebase.

6

Pretty sure we’ve been fixing most of these since under the assumption that they are indeed incorrectly hardcoded. Quite a few of these should have since been fixed.

7

We have +40 addon repos, I’ve only searched core, houdini, maya and nuke.

Core Addon:

Maya Addon:

Nuke Addon

8

Also in TrayPublisher, and in Resolve :