Hi,
this is a bug that cannot be solved easily. Object tool filtering for displaying in context menu is done on client side. If client application does not have access to templates it cannot check if node is in that template or not. This can be solved by sending filtering request to the server, but that will require round trip to server on each right click on object (possibly combined with some sort of caching and push notifications from server when template membership changes) - this can significantly slow down UI.
Alternative approach for such filtering could be by using custom attributes - you can use configuration poll hook to set custom attribute for each parent template and then in object tool check for those custom attributes.
Best regards,
Victor
this is a bug that cannot be solved easily. Object tool filtering for displaying in context menu is done on client side. If client application does not have access to templates it cannot check if node is in that template or not. This can be solved by sending filtering request to the server, but that will require round trip to server on each right click on object (possibly combined with some sort of caching and push notifications from server when template membership changes) - this can significantly slow down UI.
Alternative approach for such filtering could be by using custom attributes - you can use configuration poll hook to set custom attribute for each parent template and then in object tool check for those custom attributes.
Best regards,
Victor