I'm still experienceing this issue. I realize that this modification states that it works with 3.5 and that I'm running 3.6
Is there a chance that this could be ported over to work with 3.6 by chance?
I'm thinking that the new thread template might be the issue and I'm not savy enough to figure out what's going on.
Is anyone else experiencing this issue? This is cripling our bug reporting process and it's driving me nuts!
|