I have noticed that in Maestro Content Type Task absolute path used for handler. Handler appears in template configuration and can broke the workflow when configuration has been imported in another environment. There are any reason to use additional $base_url?

I have attached patch to fix this issue.

CommentFileSizeAuthor
maestro-fix-content-type-task-handler.patch1.26 KBugolek

Comments

lebster created an issue. See original summary.

  • _randy committed 309f0fd on 8.x-2.x authored by lebster 
    Issue #3043851 by lebster: Avoid using absolute handler path in content...
_randy’s picture

_randy commented
Status: Active » Fixed

Seems reasonable I think -- The task console tries to strip off the base url for both the detection of the handler AND the display of the link.

We'll see how this change goes longer-term and see if other issues arise from removing it (don't think there will be though)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.