Board Thread:Support Requests - Getting Technical/@comment-28398720-20160915104153/@comment-188432-20160922145237

I've done some exploration around this issue recently. I can't reproduce this issue simply by using a construction like: ... infobox content ... In itself, that's fine and works without issue.

However, if you have, say, Template:Happy infobox -- which is already using PI markup -- and you also have Template:Happy infobox/Draft, then the includeonly tags that are in Template:Happy infobox trigger the "Migrate this infobox" module.

So, it's not really a bug, so much as an unexpected edge case: it's not really anticipated that a new /Draft would be created (or left in place) when the parent template was already using PI code. Nevertheless, we have an internal ticket for this issue. While it's being worked on, the simple solution is just to remove the /Draft or move it to a different parent name.

If, Bugthe, you're experiencing this issue in some other circumstance than I've just laid out, please gimme a shout back! Thanks for bringing this up!