It’s not intended that you would use a full URL there, just a segment path like you would a path variable or a Pages URI. I can see that it might be beneficial though, for instance if you run the CP or that channel from a separate subdomain, will look into supporting full URLs there, including the {base_url} variable.
Hey Kurt, so I looked into this further today and I don’t think that it needs to support {base_url}, since we aren’t making HTTP requests to your front end anyway. We just spin up the renderer using the template path / route from the current site—which would be the same site as the Channel, since you can only edit an entry for a Channel while in that Channel’s site. The URL you are at shouldn’t matter, in other words. So this preference setting only needs the template group / name plus the URL title / entry ID, or the Template Route that you use to display single entries. Make sense?
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.