Hi Mike,
I have been looking into this issue more thoroughly and as it turns
out the reason I was able to reproduce your problem was because I had
the same file located in two different custom tags folders.
When I removed one of the Custom Tags Paths FusionDebug was able to
step into the custom tag successfully.
Would you just like to confirm that this is not the case for you?
Also make sure to check that the path specified on the breakpoint in
the breakpoint’s view of FusionDebug is actually pointing to the right
file on your server.
Kind Regards,
Anna
On Dec 13, 10:08 am, "Anna Ljungberg [FusionDebug Team]"